You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Davanum Srinivas (JIRA)" <ax...@ws.apache.org> on 2005/08/22 09:00:22 UTC

[jira] Commented: (AXIS-2184) JWS Compiler invoked with incomplete classpath

    [ http://issues.apache.org/jira/browse/AXIS-2184?page=comments#action_12319552 ] 

Davanum Srinivas commented on AXIS-2184:
----------------------------------------

Could you please help come up with a patch? (against latest CVS)

thanks,
dims

> JWS Compiler invoked with incomplete classpath
> ----------------------------------------------
>
>          Key: AXIS-2184
>          URL: http://issues.apache.org/jira/browse/AXIS-2184
>      Project: Apache Axis
>         Type: Bug
>   Components: Deployment / Registries
>     Versions: 1.2.1
>     Reporter: Adrian Price

>
> org.apache.axis.handlers.JWSHandler.setupService(MessageContext) (JWSHandler.java:195) invokes the Java compiler but the classpath returned by org.apache.axis.utils.ClasspathUtils.getDefaultClasspath(MessageContext) is incomplete because although ClasspathUtils reads manifest Class-Path attributes from a JAR file it does not do the same for an exploded JAR (app servers frequently explode EJB-JAR, EAR or WAR when deploying them) . This means that the manifest Class-Path for exploded archives does not get included on the compiler's classpath.
> See also http://issues.apache.org/jira/browse/AXIS-1530 - I believe this to be a consequence of this problem.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira