[ https://jira.jboss.org/jira/browse/JBESB-2989?page=com.atlassian.jira.plu... ] Kevin Conner commented on JBESB-2989: ------------------------------------- jaxb-xjc.jar is present in the top level lib directory but not being picked up. Looks like a classloader issue of some sort. -- 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-2989?page=com.atlassian.jira.plu... ] Kevin Conner commented on JBESB-2989: ------------------------------------- Further investigation shows that this is not related to the previous issue, rather it is associated with the configuration of the server wrt the top level lib directory. The xjc jar, while present in the top level dir, is never referenced through any of the bootstrap xml files and, therefore, not part of the classpath. Investigating config alternatives. -- 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-2989?page=com.atlassian.jira.plu... ] Kevin Conner commented on JBESB-2989: ------------------------------------- Change of plan, we aspectise the jaxws-tools jar to handle vfszip schemes so will only do the jaxb-xjc jar. -- 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