Update 11/6/06:
- I updated javaee5 this morning and hit some problems due to changes
with dependencies on activecluster from
\configs-jee5\jetty6-clustering-builder-wadi\pom.xml
I added the following to the root pom to get around this problem:
<dependency>
<groupId>org.apache.activemq</groupId>
<artifactId>activecluster</artifactId>
<version>4.0.1</version>
</dependency>
- Next I hit the same problem with the security tests that I hit earlier
(and still haven't resolved). To make some further progress I decided
to skip the tests to see how far I could get.
- Next I hit errors because I didn't have the 1.0.1 version of the
geronimo-servlet_2.5_spec in my local repo and couldn't download it. I
checkout out specs and built them using the 1.5 JDK thinking that it
would resolve the problem and get me the latest specs for Java EE 5 that
we had checked in.
- However, I hit the same problem with the geronimo-servlet_2.5_spec
again because the version built from specs\trunk was 1.1-SNAPSHOT while
the dependency management in the root pom.xml was looking for version
1.0.1. To get past this I updated the root pom dependency management to
1.1-SHAPSNOT.
- I hit a similar problem with the geronimo-ws-metadata_2.0_spec which
was declared in the root pom.xml dependency management as needing
version 1.0 while my local build produced 1.1-SNAPSHOT. I updated the
pom to reference 1.1-SNAPSHOT.
- After that I started hitting these errors for more missing specs:
Missing:
----------
1) javax.annotation:jsr250-api:jar:2.0-JAXWS-2.0-EA3
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=javax.annotation
-DartifactId=jsr250-api \
-Dversion=2.0-JAXWS-2.0-EA3 -Dpackaging=jar -Dfile=/path/to/file
Path to dependency:
1) org.apache.geronimo.modules:geronimo-cxf:jar:1.2-SNAPSHOT
2)
org.apache.cxf:cxf-rt-transports-http:jar:2.0-incubator-M1-SNAPSHOT
3) org.apache.cxf:cxf-api:jar:2.0-incubator-M1-SNAPSHOT
4)
org.apache.cxf:cxf-common-utilities:jar:2.0-incubator-M1-SNAPSHOT
5) javax.annotation:jsr250-api:jar:2.0-JAXWS-2.0-EA3
2) javax.jws:jsr181-api:jar:2.0-JAXWS-2.0-EA3
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=javax.jws
-DartifactId=jsr181-api \
-Dversion=2.0-JAXWS-2.0-EA3 -Dpackaging=jar -Dfile=/path/to/file
Path to dependency:
1) org.apache.geronimo.modules:geronimo-cxf:jar:1.2-SNAPSHOT
2)
org.apache.cxf:cxf-rt-transports-http:jar:2.0-incubator-M1-SNAPSHOT
3) org.apache.cxf:cxf-api:jar:2.0-incubator-M1-SNAPSHOT
4)
org.apache.cxf:cxf-common-utilities:jar:2.0-incubator-M1-SNAPSHOT
5) javax.jws:jsr181-api:jar:2.0-JAXWS-2.0-EA3
The first one is kinda ironic since I had checked the only missing
common annotations spec item into trunk last week. However it appears
that cxf is not using our specs. I have to dig into these errors some
more.
As an aside ... I suspected that I would eventually get to a point where
I needed to also build openjpa locally. So I checked this out and gave
it a go. This is fails due to a missing dependency from sourceforge ...
net.sourceforge.serp:serp:jar:1.12.0
I'll keep posting my results/progress. If anybody else is having
problems or getting further please post as well.
Thanks,
Joe
Joe Bohn wrote:
Thanks for the responses David (and the fix for the new Jetty constructor).
Some more info:
For those building on windows:
- When building Jetty the WebAppTest fails on windows because it reads a
files and the asserts that the file ends with a "blah,blah,blah\n".
However, on windows the file actually ends with CRLF. One way around
this is to change the line (line 119) to assert that the line ends with
"blah,blah,blah\r\n" (adding the \r).
Test failure building javaee5:
- Building javaee5 is currently failing in a different test that I'm
looking into at the moment.
<testcase time="0.469" name="testExplicitMapping">
<error type="java.io.IOException" message="Server returned HTTP
response code: 403 for URL:
http://localhost:5678/test/protected/hello.txt";>java.io.IOException:
Server returned HTTP response code: 403 for URL:
http://localhost:5678/test/protected/hello.txt
at
sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1149)
at
org.apache.geronimo.jetty6.SecurityTest.testExplicitMapping(SecurityTest.java:119)
</error>
Still trying to figure this last one.
Joe
David Jencks wrote:
On Nov 2, 2006, at 9:18 AM, Joe Bohn wrote:
It appears that sandbox/javaee5 is the location that we should be
using to integrate various EE 5 items until 1.2 is released.
Therefore, I thought I would post some information that I've learned
(and problems that I've encountered) here since I supposed others
are or soon will be doing the same thing. Perhaps somebody has some
information that might help get around some of problems listed below
(such as when Jetty snapshots might be published?).
First, this is a feature branch. To use it you must first build
trunk to populate your local repository. Next you must checkout
https://svn.apache.org/repos/asf/geronimo/sandbox/javaee5 and build it.
However, in doing the last step you'll hit some problems:
- The Jetty 6.1 snapshots are not published anywhere yet (at least
not anywhere I've been able to find them). Therefore, you will need
to build Jetty 6.1 locally. Can somebody related to both Geronimo
and Jetty help us to get the Jetty 6.1 snapshots published?
They are currently available at
http://jetty.mortbay.org/maven2/snapshot
however I am encouraging jan to publish them to the codehaus snapshot
repo. I think we can wait a day or two for this rather than adding
another repo to the list.
Building Jetty:
- You can check out Jetty from http://svn.codehaus.org/jetty/jetty/
trunk Jetty requires cvs to build (in case you don't already have
it). For me the build failed because of test failures but it
appeared to create the jetty jars that we need.
After building Jetty you should be ready to build the javaee5
branch. Of course, this build requires JDK 1.5
- Next I hit a problem building javaee5. Apparently there have
been some changes in Jetty since the original integration in the
branch. It appears that the Jetty Session object may have changed.
Here is the error I received:
----------------------------------------------------------------------
--
[ERROR] BUILD FAILURE
[INFO]
----------------------------------------------------------------------
--
[INFO] Compilation failure
C:\javaee5\modules-jee5\geronimo-jetty6\src\main\java\org\apache
\geronimo\jetty6\cluster\ClusteredSessionManager.java:[94,12] cannot
find symbol
symbol : constructor Session(<nulltype>,java.lang.String)
location: class
org.mortbay.jetty.servlet.AbstractSessionManager.Session
I committed a change to this class to work with current jetty 6.1
I then spoke with David Jencks and he told me the revision of Jetty
that he used when he first created the branch. That was revision
1064. So, I checked out this Jetty revision but with this one the
build fails earlier with this error ....
2006-11-02 11:48:40.687::WARN: failed
[EMAIL PROTECTED]
java.io.IOException: Cannot write log directory C:\tmp
at org.mortbay.util.RolloverFileOutputStream.setFile
(RolloverFileOutputStream.java:131)
at org.mortbay.util.RolloverFileOutputStream.<init>
(RolloverFileOutputStream.java:88)
at org.mortbay.jetty.NCSARequestLog.doStart
(NCSARequestLog.java:363)
at org.mortbay.component.AbstractLifeCycle.start
(AbstractLifeCycle.java:39)
at org.mortbay.jetty.handler.RequestLogHandler.doStart
(RequestLogHandler.java:116)
.....
I haven't seen this.
I'll let you know as I resolve these issues in case you too need to
work on the JavaEE5 branch.
thanks
david "it works on my machine" jencks
Thanks,
Joe
