-
1. Re: JDK 1.6.0_10/JBoss4.2.0.GA/JBossWS 2.0.0 - setProperty m
pallas_athena Nov 10, 2008 5:55 AM (in response to lcompton)I have the same issues with the following config:
Windows XP
JDK 1.6.0_10
JBoss AS 5.0.0 CR2
JBossWS 3.0.4
I, too, have followed the steps described in https://jira.jboss.org/jira/browse/SOA-984
and https://jira.jboss.org/jira/browse/JBWS-1439.
So upgrading to newer versions might not be a guarantee for success, either :-/ -
2. Re: JDK 1.6.0_10/JBoss4.2.0.GA/JBossWS 2.0.0 - setProperty m
asoldano Nov 11, 2008 5:02 AM (in response to lcompton)"pallas_athena" wrote:
I have the same issues with the following config:
Windows XP
JDK 1.6.0_10
JBoss AS 5.0.0 CR2
JBossWS 3.0.4
I, too, have followed the steps described in https://jira.jboss.org/jira/browse/SOA-984
and https://jira.jboss.org/jira/browse/JBWS-1439.
So upgrading to newer versions might not be a guarantee for success, either :-/
Did you try using the jdk6 distribution of the AS? Otherwise, could you please double-check again which jars (where they come from) are you using at runtime on client side (you get exceptions on client side, don't you?) ?
We run the whole testsuite with JDK 6 every night (and of course before every release), so this should really work http://jbossws.jboss.org:8180/hudson/job/Native-Core-AS-5.0.0-JDK6/ (<-- this is with AS 5.0.0.CR2 and the current jbossws trunk) -
3. Re: JDK 1.6.0_10/JBoss4.2.0.GA/JBossWS 2.0.0 - setProperty m
juergen.zimmermann Nov 11, 2008 6:30 AM (in response to lcompton)Don't forget to use the endorsed mechanism for jaxb-api.jar, jbossws-native-*.jar
-
4. Re: JDK 1.6.0_10/JBoss4.2.0.GA/JBossWS 2.0.0 - setProperty m
lcompton Nov 12, 2008 3:40 PM (in response to lcompton)I solved my problem. Here's a synopsis of the winning configuration:
1. Configured JBoss via the ant script in "jbossws-native-2.0.0". Ended up with the following in "$JBOSS_HOME/lib/endorsed":
- jaxb-api.jar
- jboss-jaxrpc.jar
- jboss-jaxws.jar
- jboss-saaj.jar
- serializer.jar
- xalan.jar
- xercesImpl.jar
2. Added the same files to "$JAVA_HOME/jre/lib/endorsed", which allowed my standalone web service client to work.
Note that I tried every permutation of "endorsed" directories and "java.endorsed.dirs" settings and this is the ONLY configuration that worked.
Larry -
5. Re: JDK 1.6.0_10/JBoss4.2.0.GA/JBossWS 2.0.0 - setProperty m
pallas_athena Nov 13, 2008 4:05 AM (in response to lcompton)Thank you Alessio and Juergen for the suggestions, you put me on the right track! :)
Yes, I was using the jdk6 distribution of the application server and the endorsed mechanism, but the client was using jars from the %JBOSS_HOME%/client folder. As soon as the client used the jars from the /lib/endorsed folder, the error disappeared.
Just out of curiosity, what is the difference between the /client and the /lib/endorsed jars? The files seem to have exactly the same size, which is why I assumed they were identical. -
6. Re: JDK 1.6.0_10/JBoss4.2.0.GA/JBossWS 2.0.0 - setProperty m
juergen.zimmermann Nov 13, 2008 6:40 PM (in response to lcompton)"Endorsed" is described at http://java.sun.com/javase/6/docs/technotes/guides/standards.
JDK 6 ships with an (internal) implementation of JAXB, and JBoss ships its own implementation of JAXB which should be used instead of the one of JDK. -
7. Re: JDK 1.6.0_10/JBoss4.2.0.GA/JBossWS 2.0.0 - setProperty m
zemagik Feb 13, 2009 9:00 AM (in response to lcompton)Hi,
My conf :
Windows XP
JDK 1.5.0_14
JBoss AS 5.0.0 GA
I get this "java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage" with my junit tests runned from ant.
I checked that :
- JBoss is the jdk5-compiled version
- I compile Junit tests with the JDK5 and I launched Junit with all the JBoss libraries in the classpath : lib/endorsed, common and client.
- To be sure, I removed all occurence of JDK and JRE 6.0 from my computer.
If you have any clue... Thanks for your help.
Eric -
8. Re: JDK 1.6.0_10/JBoss4.2.0.GA/JBossWS 2.0.0 - setProperty m
peterj Feb 13, 2009 11:33 AM (in response to lcompton)Do you have CLASSPATH set globally?
Or you can try this. Add "-verbose:class" to the JAVA_OPTS in run.conf. This option prints each class loaded and the JAR it was loaded from. This should help you locate the stray JAXB JAR file that is being picked up.