[ https://jira.jboss.org/jira/browse/JBESB-2738?page=com.atlassian.jira.plu... ] Work on JBESB-2738 started by Kevin Conner. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBESB-2738?page=com.atlassian.jira.plu... ] Kevin Conner updated JBESB-2738: -------------------------------- Summary: Support configuration of wise compilation classpath (was: Investigate workarounds for wise classloader creation) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBESB-2738?page=com.atlassian.jira.plu... ] Kevin Conner closed JBESB-2738. ------------------------------- Resolution: Done It turns out that the jar list within wise is irrelevant and can safely be ignored within both AS4 and AS5 environments. This may have had a purpose previously but it would seem that the reason is no more. There is now an aspect which returns an empty list for this method invocation. The real problem with the WSDL compilation is the way in which wise in handling the generation and compilation of the java proxies, as this depends on the jaxws tooling which is executed within the AS5 environment. As part of the generation, the jaxws tooling attempts to create a classpath based on the location of specific classes but it does not understand the vfszip protocol used within AS5. It is, therefore, necessary for us to handle the vfszip to file translation. A better solution would be to rework the way in which wise generates the proxies but this work should see us through the current project release. Updated in revision 28059. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira