[ https://jira.jboss.org/browse/JBIDE-7279?page=com.atlassian.jira.plugin.s... ] Brian Fitzpatrick commented on JBIDE-7279: ------------------------------------------ So we just need to verify the JBossWS 3.3.x libraries are there? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBIDE-7279?page=com.atlassian.jira.plugin.s... ] Brian Fitzpatrick updated JBIDE-7279: ------------------------------------- Original Estimate: 0 minutes Remaining Estimate: 0 minutes Fix Version/s: 3.2.x -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-7279?page=com.atlassian.jira.plugin... ] Stuart Smith commented on JBIDE-7279: ------------------------------------- This issue really has nothing to do with the JBossWS web services tools specifically. This has to do with the fact that the Server definition that is added to the build path of the project is not aware of the lib/endorsed directory. This directory is used pretty heavily by the various JBossWS stacks to supply different JARs than the default Java SE 6 JARs. Right now the project compilation fails because it only picks up the Java SE 6 JAX-WS API version. I am using JBossWS CXF stack and originally I thought I was getting an error because I had defined the server runtime before upgrading the JBossWS stack. I look back at the original JBoss AS 5.1.GA distribution and even some of the JARs from that in the lib/endorsed directory are not on the server runtime build path. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-7279?page=com.atlassian.jira.plugin... ] Stuart Smith edited comment on JBIDE-7279 at 8/15/11 2:20 PM: -------------------------------------------------------------- I did some more digging and was going through each entry in the build path contributed by the server. It turns out the JAX-WS 2.2 JARs were also present in the 'common/lib' directory and were present on the project classpath. If issues come up it has more to do with the fact that by default a project is setup to have Java SE first on the classpath (after EAR libraries) and the server and any other entries after this. There does not appear to be an easy way to get the behavior we get at runtime where the 'endorsed' directory is checked first before any Java SE Jars. There are probably many ways to approach this. Moving the entire server classpath before the Java SE entry is probably not entirely correct as we only want the 'endorsed' directory to supercede Java SE. Another way would be to add a classpath variable that points to the JBoss 'endorsed' directory and add this separately. was (Author: stuart_wildcat): I did some more digging and was going through each entry in the build path contributed by the server. It turns out the JAX-WS 2.2 JARs were also present in the 'common/lib' directory. If issues come up it has more to do with the fact that by default a project is setup to have Java SE first on the classpath (after EAR libraries) and the server and any other entries after this. There does not appear to be an easy way to get the behavior we get at runtime where the 'endorsed' directory is checked first before any Java SE Jars. There are probably many ways to approach this. Moving the entire server classpath before the Java SE entry is probably not entirely correct as we only want the 'endorsed' directory to supercede Java SE. Another way would be to add a classpath variable that points to the JBoss 'endorsed' directory and add this separately. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira