[jbosstools-issues] [JBoss JIRA] Issue Comment Edited: (JBIDE-7279) Provide support for JAX-WS 2.2 APIs

[Stuart Smith (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-7279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12621166#comment-12621166 ] 

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.
  
> Provide support for JAX-WS 2.2 APIs
> -----------------------------------
>
>                 Key: JBIDE-7279
>                 URL: https://issues.jboss.org/browse/JBIDE-7279
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: Webservices
>    Affects Versions: 3.2.0.Beta1
>            Reporter: Lukas Jungmann
>            Assignee: Feng Qian
>             Fix For: 3.3.x
>
>   Original Estimate: 0 minutes
>  Remaining Estimate: 0 minutes
>
> [this is to be checked against JBossAS 6.0M5 or newer]
> for a project which has target runtime set to JBossAS6/uses JBossWS 3.3.x
> -user should be allowed to set JAX-WS spec version in a top-down web service and web service client wizards to 2.2
> -editor should not show errors for following generated type of constructor:
>     public Info(WebServiceFeature ... features) {
>         super(WSDL_LOCATION, SERVICE, features);
>     }
> (in the other words editor/ide has to know about APIs from $JBOSS_HOME/lib/endorsed)

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira