How to build org.mortbay.jetty.j2se6

[Axel Rose]

(repeated from user@...)

Hello all,

I wanted to test the org.mortbay.jetty.j2se6 classes but couldn't succeed
to build them on my own using maven.

This is what I did:

 svn co http://svn.codehaus.org/jetty/jetty/trunk jetty
 cd jetty
 mvn -Pall-modules install

This works well. Now

 svn co http://svn.codehaus.org/jetty-contrib/trunk jetty-contrib
 cd jetty-contrib
 mvn install

gives this error:
---
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Error building POM (may not be this project's POM).


Project ID: org.mortbay.jetty:jetty-contrib-parent:pom:7.0.0.1-SNAPSHOT

Reason: Cannot find parent: org.mortbay.jetty:jetty-project for
project: org.mortbay.jetty:jetty-contrib-parent:pom:7.0.0.1-SNAPSHOT
for project org.mortbay.jetty:jetty-contrib-parent:pom:7.0.0.1-SNAPSHOT


[INFO] ------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.reactor.MavenExecutionException: Cannot find parent:
org.mortbay.jetty:jetty-project for project:
org.mortbay.jetty:jetty-contrib-parent:pom:7.0.0.1-SNAPSHOT for
project org.mortbay.jetty:jetty-contrib-parent:pom:7.0.0.1-SNAPSHOT
    at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:378)
    at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:292)
    at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
    at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
    at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
    at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
    at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.project.ProjectBuildingException: Cannot
find parent: org.mortbay.jetty:jetty-project for project:
org.mortbay.jetty:jetty-contrib-parent:pom:7.0.0.1-SNAPSHOT for
project org.mortbay.jetty:jetty-contrib-parent:pom:7.0.0.1-SNAPSHOT
    at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1370)
---

How could I continue?

What is the state of the contrib code anyway?
It looks to me as if this is not yet ported to Jetty 7 org.eclipse


Thanks
 Axel

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[janb]

Axel,

The jetty j2se6 module has not been ported to jetty-7 yet.
It is only available in jetty-6. Note you only need to check
out and build https://svn.codehaus.org/jetty/jetty/branches/jetty-6.1
and it will also build most modules from contrib.

cheers
Jan

Axel Rose wrote:

> (repeated from user@...)
>
> Hello all,
>
> I wanted to test the org.mortbay.jetty.j2se6 classes but couldn't succeed
> to build them on my own using maven.
>
> This is what I did:
>
>  svn co http://svn.codehaus.org/jetty/jetty/trunk jetty
>  cd jetty
>  mvn -Pall-modules install
>
> This works well. Now
>
>  svn co http://svn.codehaus.org/jetty-contrib/trunk jetty-contrib
>  cd jetty-contrib
>  mvn install
>
> gives this error:
> ---
> [INFO] Scanning for projects...
> [INFO] ------------------------------------------------------------------------
> [ERROR] FATAL ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] Error building POM (may not be this project's POM).
>
>
> Project ID: org.mortbay.jetty:jetty-contrib-parent:pom:7.0.0.1-SNAPSHOT
>
> Reason: Cannot find parent: org.mortbay.jetty:jetty-project for
> project: org.mortbay.jetty:jetty-contrib-parent:pom:7.0.0.1-SNAPSHOT
> for project org.mortbay.jetty:jetty-contrib-parent:pom:7.0.0.1-SNAPSHOT
>
>
> [INFO] ------------------------------------------------------------------------
> [INFO] Trace
> org.apache.maven.reactor.MavenExecutionException: Cannot find parent:
> org.mortbay.jetty:jetty-project for project:
> org.mortbay.jetty:jetty-contrib-parent:pom:7.0.0.1-SNAPSHOT for
> project org.mortbay.jetty:jetty-contrib-parent:pom:7.0.0.1-SNAPSHOT
>     at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:378)
>     at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:292)
>     at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
>     at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
>     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>     at java.lang.reflect.Method.invoke(Method.java:597)
>     at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>     at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>     at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>     at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.project.ProjectBuildingException: Cannot
> find parent: org.mortbay.jetty:jetty-project for project:
> org.mortbay.jetty:jetty-contrib-parent:pom:7.0.0.1-SNAPSHOT for
> project org.mortbay.jetty:jetty-contrib-parent:pom:7.0.0.1-SNAPSHOT
>     at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1370)
> ---
>
> How could I continue?
>
> What is the state of the contrib code anyway?
> It looks to me as if this is not yet ported to Jetty 7 org.eclipse
>
>
> Thanks
>  Axel
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>     http://xircles.codehaus.org/manage_email
>
>
>

--
Jan Bartel, Webtide LLC | janb@... | http://www.webtide.com

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Axel Rose]

> The jetty j2se6 module has not been ported to jetty-7 yet.

Thanks for the information.

Perhaps I try this on my own.


Regards
  Axel

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Axel Rose]

Well, it was easy to make the code compilable but ...

I have no success at runtime because the code relies somehow on
org.eclipse.jetty.server.handler._handlers being non volatile. This
has been changed in Jetty 7.

Now it would be probably best to ask the original author lorban. Is he
(are you) still actively
working on this package?

Otherwise -- has somebody else time to help on this?

It would be a real benefit for Jetty 7 to serve SOAP request IMO.


Regards,
  Axel

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[jmcconnell]

i will try and look at this tonight or this weekend, I don't think I
really ever paid attention to this module, but I agree if its serving
soap goop its probably good to get going

jesse

--
jesse mcconnell
jesse.mcconnell@...



On Fri, Nov 6, 2009 at 04:28, Axel Rose <axel.roeslein@...> wrote:

> Well, it was easy to make the code compilable but ...
>
> I have no success at runtime because the code relies somehow on
> org.eclipse.jetty.server.handler._handlers being non volatile. This
> has been changed in Jetty 7.
>
> Now it would be probably best to ask the original author lorban. Is he
> (are you) still actively
> working on this package?
>
> Otherwise -- has somebody else time to help on this?
>
> It would be a real benefit for Jetty 7 to serve SOAP request IMO.
>
>
> Regards,
>  Axel
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Ludovic Orban]

Jesse,

This Jetty module is the only way I know to get scalable JAX-WS2 web services on J2SE.

I've attached to JETTY-1143 a slightly cleaned up version which compiles and works with Jetty 7. I'd appreciate if that module could be reviewed and eventually committed back to the SVN repository.

Thanks,
Ludovic

[jmcconnell]

great! I'll take a look, if it is working then we'll probably be able
to get it into the next release cycle of 7.0.1, otherwise would be the
one right after that

cheers,
jesse

--
jesse mcconnell
jesse.mcconnell@...



On Sun, Nov 8, 2009 at 07:20, Ludovic Orban <ludovic.orban@...> wrote:

>
> Jesse,
>
> This Jetty module is the only way I know to get scalable JAX-WS2 web
> services on J2SE.
>
> I've attached to JETTY-1143 a slightly cleaned up version which compiles and
> works with Jetty 7. I'd appreciate if that module could be reviewed and
> eventually committed back to the SVN repository.
>
> Thanks,
> Ludovic
> --
> View this message in context: http://old.nabble.com/How-to-build-org.mortbay.jetty.j2se6-tp26204777p26253711.html
> Sent from the Jetty Discuss mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Axel Rose]

It's working for me.

Phantastic!!

Many thanks for spending time during the weekend Ludovic


Cheers,
  Axel.

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[jmcconnell]

I have reviewed and committed this into the codehaus trunk and wired
it into the build...

A couple of things I would like to see here:

1) Ludovic: as the sole contributor of this and while we have your
attention, should this be a candidate for migrating to the eclipse
side of the jetty project would you also attach to the jira issue your
agreement that this contribution would also be acceptable to you for
being dual licensed EPL 1.0 and ASL 2.0?  That way it will be easier
to get that contribution through should this be something the project
decides to do down the road.

2) Axel and Ludovic: a little bit of documentation as to how you guys
use this module would be great, if you just replied to this mail with
the info I'll get a wiki page going for it.

3) Axel and Ludovic: What is your general usage scenario for making
use of this context...is this something that you guys do standalone
just for a particular server or do you wire this into the default
jetty server on startup?  Once I have a good idea on the usage and
configuration of this thing I'll go ahead and wire it into the
jetty-hightide distribution.

cheers and thanks for the contribution guys

jesse

--
jesse mcconnell
jesse.mcconnell@...



On Sun, Nov 8, 2009 at 07:20, Ludovic Orban <ludovic.orban@...> wrote:

>
> Jesse,
>
> This Jetty module is the only way I know to get scalable JAX-WS2 web
> services on J2SE.
>
> I've attached to JETTY-1143 a slightly cleaned up version which compiles and
> works with Jetty 7. I'd appreciate if that module could be reviewed and
> eventually committed back to the SVN repository.
>
> Thanks,
> Ludovic
> --
> View this message in context: http://old.nabble.com/How-to-build-org.mortbay.jetty.j2se6-tp26204777p26253711.html
> Sent from the Jetty Discuss mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Axel Rose]

Hi all,

my usage scenario is this:

I have some kind of server using a propriatory protocol. To make the
server usable for 3rd party developers there is a web service interface
using SOAP messages over http.

Up til now I use JAX-WS, build a war file and deploy that to a servlet
container.

With embedded Jetty I can now provide the SOAP interface directly from
my main server, short, simple and effective by just setting a property

System.setProperty(
  "com.sun.net.httpserver.HttpServerProvider",
  "org.eclipse.jetty.jaxws2spi.JettyHttpServerProvider");

The SOAP endpoint for a sample Calculator service is published thusly:

Calculator calculator = new Calculator();
Endpoint endpoint = Endpoint.create(calculator);
endpoint.publish(calcContext);


Regards,
  Axel

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Ludovic Orban]

Setting the system property is useless, just having the module on the classpath should be sufficient to have Jetty replace the Sun HTTP server.

[Ludovic Orban]

Jesse,

1) Could you please point me to instructions about how to get the agreement? I remember I had to fill & sign via PGP some contributor agreement file when I got contributor SVN access for Jetty 6 but I can't remember the details nor find the old agreement back.

2) There a two ways to make use of this module:
  * J2SE mode: just drop the Jetty binaries and this module's jar in your classpath and any call to javax.xml.ws.Endpoint.publish() will actually publish the web service on Jetty instead of on Sun's embedded web server.
  * J2EE/mixed mode: use this mode when you write a web application which needs to expose some web services (again with javax.xml.ws.Endpoint.publish()) but you want the web services to re-use the Jetty server and just create a new context per published web service. This requires the JettyHttpServerProvider.setServer() method to be called before any web service is published to tell the code to which server to add contexts.

3) I use both modes, the J2SE mode mostly for quick'n'dirty development and mixed mode mostly for production-quality code. The explanation at point (2) should gibe you a clear overview of the only possible use cases. If not shoot me as I wasn't clear enough describing them.