Hi Josef, Is this Vista thing Window's Vista? In that case, can you just use the standard oracle JDK 1.6? I don't know about your HP environment, whether you need to add a separate saaj impl or its JDK comes with some default impl. But I don't know why you want to add saaj.jar when you are using the standard oracle JDK 1.6 on windows.
regards, aki 2012/11/22 Stadelmann Josef <[email protected]>: > Aki > Unfortunally a NO GO > just seek in Google with > cxf+builds+"com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnectionFactory" > and receive 3 entries; 1 from me and two from others having similar to same > problems. > in general it is a big mess which SAAJ is to be used and when. That my > impression. > we have axis2 installed on our PC as well as OpenVMS. Maybe that makes a > difference. > We have no Glassfish installed. If that matters i.e.. > So we have not yet a cxf installed, we are just about to build one; if that > makes a difference. > > My last cfx/trunk build failed at exact the same position as delivered with a > previous mail: > But this time I had as explained in my previous mail jar files endorsed. > > maybe I have to endorse as well a jar file containing an IMPLEMENTATION for > the saaj-api.jar? > what do you think about that? > > Guess I have to take the debugger and find why it can't create this > HttpSOAPConnectionFactory > > Just to have it build on a Vista / JDK1.6.0_30 with some jars endorsed. > Josef - BTW take time to answer - I am in again next Monday > > > > > > -----Ursprüngliche Nachricht----- > Von: Stadelmann Josef [mailto:[email protected]] > Gesendet: Donnerstag, 22. November 2012 16:55 > An: [email protected] > Betreff: AW: [cxf] trunk and tags/2.7.0 > > good point Aki > > I just forgot that my original installation of JDK1.6.0_30 on VISTA has no > endorsed directories. > > Now I will redo the build but this time with a JDK1.6.0_30 installation which > has the files as shown below endorsed. (will let you know) > > Because in order to work with certain java code annotations and JDK 1.6.0_30 > and axis2-1.6.2 JAX-WS routines i.e. for @Resources, you will find > axis2-1.6.2 failing at runtime because it's implementation used a new > jdk1.7.0 interface to an old JDK1.6.0 implementation (in a JAR) of some > jax-ws stuff. > > To cure this, we have endorse and run since months on Vista and OpenVMS this > files from JDK1.7.0_03 at > > E:\Users\C770817\SW-UMGEBUNG\Java\jdk1.6.0_30\jre\lib\endorsed > jaxws-api.jar > jsr181-api.jar > jsr250-api.jar > saaj-api.jar > > since, our JAX-WS based web service works on tomcat on OpenVMS as well as on > VISTA we endorsed the same files to Tomcat to and gave him a hint about to > use endorsed files. > > that is all we changed. > > That is why we wait so eagerly for HP to deliver after all an OpenJDK 1.7 and > an OpenJDK 1.8 for OpenVMS but may wait forever; > > Will keep you informed > > Josef > > -----Ursprüngliche Nachricht----- > Von: Aki Yoshida [mailto:[email protected]] > Gesendet: Donnerstag, 22. November 2012 14:29 > An: [email protected] > Betreff: Re: [cxf] trunk and tags/2.7.0 > > Hi, > I was wondering if there is some specific setup in your environment or there > is some inconsistency with the jdk version and your environmen that is > interfering with the normal behavior (i.e., of finding that default factory). > > I have win7 and the standard x64 jdk version 1.6.0_37 does not have any issue > with the trunk's cxf-systests-jaxws. > > regards, aki > > 2012/11/21 Stadelmann Josef <[email protected]>: >> Hi Colm, >> hi developers; >> >> After cxf/trunk built OK with JDK1.7.0_03 on a Vista system, (as >> reported), so I tried the same build from trunk sources with Vista / >> JDK1.6.0_30 / maven-3.0.5 (I just changed from JDK1.7.0_03 to JDK >> 1.6.0_30 (including strong encryption files for wss4j in place)) >> >> Unfortunately that build fails to produce project cxf-systests-jaxws; >> see attached text file. Maybe you have a clue what I can do? >> >> Guess I am missing a jar file which comes from JDK1.7.0 to be placed into >> jre/lib/endorsed directory. But which one? >> >> As endorsements are to overcome few shortcomings of an older JDK, can we >> still say that cxf builds with JDK 1.6 if more and more jar files are taken >> from JDK 1.7 to be endorsed to JDK 1.6? >> >> The reason I am still trying to build on JDK1.6.0_30 is: >> 1. http://cxf.apache.org/building.html states that I can build with JDK >> 1.5.0 or better. >> 2. We have only a JDK 1.6.0 on OpenVMS, and when the build on VISTA/JDK >> 1.6.0 is OK I will move cxf/trunk to OpenVMS and do it there, that would >> give us a true alternative to Tomcat/Axis2-1.6.2 running since it was >> released on OpenVMS. >> 3. That is because it is very uncertain that HP is ever willing or >> able to come out with a Open JDK1.7.0 for OpenVMS (not talking about >> Open JDK 1.8.0 which is far in development at Oracle/Sun) >> >> So any hint, why it should build but does not build on JDK1.6.0_30 is very >> welcome. >> Josef >> >> Also the build on Vista / JDK1.6.0_30 / maven-3.0.5 "$ mvn -Pnochecks >> -T 2" progresses very good but later fails and leaves i.e. the api >> projects target-dir in a condition that the following "$ mvn cleanup" >> fails. But this not my issue now. YFI >> >> >> >> >> -----Ursprüngliche Nachricht----- >> Von: Stadelmann Josef [mailto:[email protected]] >> Gesendet: Montag, 19. November 2012 19:49 >> An: [email protected]; [email protected] >> Betreff: AW: [cxf] trunk and tags/2.7.0 >> >> Colm, >> >> just updated the cxf/trunk and rerun the cxf/trunk build. >> this time with a fresh built wss4j-1.6.7 in .m2\repository (including >> surefire testing) and strong encryption policy files on-site (under >> Vista / JDK1.7.0_03 / maven 3.0.5 ) >> >> The build of cxf just completed successfully after 2 restarts due to "out of >> memory" >> >> it takes time on my little machine, and I need a bigger one, or a better >> tuning of the memory parameters for the JVM running maven. >> >> (BTW: what are your recommendations for a 4 GB Vista machine ?) >> >> BUT most important: >> >> cxf/trunk build has passed to successful completion. >> >> so your cxf/trunk commitments show effect. >> >> Josef >> >> >> >> >> >> -----Ursprüngliche Nachricht----- >> Von: Colm O hEigeartaigh [mailto:[email protected]] >> Gesendet: Montag, 19. November 2012 17:39 >> An: [email protected] >> Betreff: Re: [cxf] trunk and tags/2.7.0 >> >> I've just committed a potential fix. Could you try building trunk again? >> >> Colm. >> >> On Mon, Nov 19, 2012 at 1:51 PM, Stadelmann Josef < >> [email protected]> wrote: >> >>> Sorry my fault, I was looking somehow skew to the version output. >>> in fact what I described below was attempted with mvn 3.0.5 on Vista, >>> (would be 2.2.1 on OpenVMS but that is not the point yet). >>> So the version of maven might not be the problem. I would also update >>> to maven-3.1 but that bootstrap-build of maven fails at my site. >>> >>> So I hope that the version of maven given below should make it? >>> >>> E:\asf\cxf\tags\cxf-2.7.0>mvn -version Apache Maven 3.0.5-SNAPSHOT >>> (r1297401; 2012-03-06 12:23:19+0100) Maven home: >>> E:\Users\C770817\SW-UMGEBUNG\apache-maven-3.0.5 >>> Java version: 1.6.0_30, vendor: Sun Microsystems Inc. >>> Java home: E:\Users\C770817\SW-UMGEBUNG\Java\jdk1.6.0_30\jre >>> Default locale: de_CH, platform encoding: Cp1252 OS name: "windows >>> vista", version: "6.0", arch: "x86", family: "windows" >>> 'cmd' is not recognized as an internal or external command, operable >>> program or batch file. >>> E:\asf\cxf\tags\cxf-2.7.0> >>> >>> >>> -----Ursprüngliche Nachricht----- >>> Von: Colm O hEigeartaigh [mailto:[email protected]] >>> Gesendet: Montag, 19. November 2012 14:43 >>> An: [email protected] >>> Betreff: Re: [cxf] trunk and tags/2.7.0 >>> >>> You must build with at least Maven 3.0. >>> >>> Colm. >>> >>> On Mon, Nov 19, 2012 at 1:25 PM, Stadelmann Josef < >>> [email protected]> wrote: >>> >>> > Hy developers >>> > >>> > I just tried to build cxf from the trunk and as it failed from the >>> > tags/cxf-2.7.0 using maven-2.2.1 && JDK_1.6.0_30 and it failed >>> > twice at the same place on a Windows Vista System. >>> > >>> > Running org.apache.cxf.ws.security.wss4j.WSS4JFaultCodeTest >>> > Tests run: 3, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: >>> > 1.035 sec <<< FAILURE! >>> > testInvalidTimestamp(org.apache.cxf.ws.security.wss4j.WSS4JFaultCod >>> > e >>> > Te >>> > st >>> > ) Time elapsed: 1.02 sec <<< FAILURE! >>> > java.lang.AssertionError: Expected failure on an invalid Timestamp >>> > at org.junit.Assert.fail(Assert.java:93) >>> > at >>> > org.apache.cxf.ws.security.wss4j.WSS4JFaultCodeTest.testInvalidTime >>> > s >>> > ta >>> > mp >>> > (WSS4JFaultCodeTest.java:171) >>> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >>> > at >>> > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImp >>> > l >>> > .j >>> > av >>> > a:39) >>> > at >>> > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcc >>> > e >>> > ss >>> > or >>> > Impl.java:25) >>> > at java.lang.reflect.Method.invoke(Method.java:597) >>> > at >>> > org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(Framewo >>> > r >>> > kM >>> > et >>> > hod.java:45) >>> > at >>> > org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveC >>> > a >>> > ll >>> > ab >>> > le.java:15) >>> > at >>> > org.junit.runners.model.FrameworkMethod.invokeExplosively(Framework >>> > M >>> > et >>> > ho >>> > d.java:42) >>> > at >>> > org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeM >>> > e >>> > th >>> > od >>> > .java:20) >>> > at >>> > org.junit.internal.runners.statements.RunBefores.evaluate(RunBefore >>> > s >>> > .j >>> > av >>> > a:28) >>> > at >>> > org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java: >>> > 30) >>> > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263) >>> > at >>> > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassR >>> > u >>> > nn >>> > er >>> > .java:68) >>> > at >>> > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassR >>> > u >>> > nn >>> > er >>> > .java:47) >>> > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231) >>> > at >>> > org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60) >>> > at >>> > org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229) >>> > at >>> > org.junit.runners.ParentRunner.access$000(ParentRunner.java:50) >>> > at >>> > org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222) >>> > at >>> > org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java: >>> > 30) >>> > at org.junit.runners.ParentRunner.run(ParentRunner.java:300) >>> > at >>> > org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provi >>> > d >>> > er >>> > .j >>> > ava:252) >>> > at >>> > org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUni >>> > t >>> > 4P >>> > ro >>> > vider.java:141) >>> > at >>> > org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider. >>> > ja >>> > va:112) >>> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >>> > at >>> > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImp >>> > l >>> > .j >>> > av >>> > a:39) >>> > at >>> > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcc >>> > e >>> > ss >>> > or >>> > Impl.java:25) >>> > at java.lang.reflect.Method.invoke(Method.java:597) >>> > at >>> > org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArra >>> > y >>> > (R >>> > ef >>> > lectionUtils.java:189) >>> > at >>> > org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invo >>> > k >>> > e( >>> > Pr >>> > oviderFactory.java:165) >>> > at >>> > org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(Pro >>> > v >>> > id >>> > er >>> > Factory.java:85) >>> > at >>> > org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(Fo >>> > r >>> > ke >>> > dB >>> > ooter.java:113) >>> > at >>> > org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.jav >>> > a >>> > :7 >>> > 5) Running org.apache.cxf.ws.security.wss4j.WSS4JInOutTest >>> > Tests run: 10, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: >>> > 0.297 sec >>> > >>> > >>> > [INFO] Apache CXF Runtime UDP Transport .................. SUCCESS >>> > [5.819s] [INFO] Apache CXF Runtime WS Reliable Messaging .......... >>> > SUCCESS [52.329s] [INFO] Apache CXF Runtime WS MetadataExchange >>> > ............ SUCCESS [5.772s] [INFO] Apache CXF Runtime WS Security >>> > .................... FAILURE [57.194s] [INFO] Apache CXF JAX-RS >>> > Extensions: Providers ........... SKIPPED [INFO] Apache CXF JAX-RS >>> > Extensions: Search .............. SKIPPED [INFO] Apache CXF RS XML >>> > Security ........................ SKIPPED >>> > >>> > Any special attentions preparations key-stores required or to be >>> > consider/setup for WSS4J before it can be used in a cxf/trunk build. >>> > >>> > Josef - thanks full for any hint >>> > >>> > >>> > >>> > >>> > >>> > >>> >>> >>> -- >>> Colm O hEigeartaigh >>> >>> Talend Community Coder >>> http://coders.talend.com >>> >> >> >> >> -- >> Colm O hEigeartaigh >> >> Talend Community Coder >> http://coders.talend.com
