[
https://issues.apache.org/jira/browse/JUDDI-301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12870848#action_12870848
]
David Jitendranath commented on JUDDI-301:
------------------------------------------
I tried with juddi v3.0.1 on JBoss 5.1AS I still see the exception when I
deploy juddiv3.war (exploded).
Here are the log messages.
14:51:42,098 INFO [Install] Loading the content of file:
vfszip:/C:/jboss/ESB/jboss-5.1.0.GA/server/default/deploy/juddiv3.war/WEB-INF/lib/juddi-core-3.0.1.jar/juddi_install_data/root_Publisher.xml
14:51:42,317 ERROR [RegistryServlet] jUDDI registry could not be
started.java.lang.IllegalArgumentException: URI is not absolute
org.apache.commons.configuration.ConfigurationException:
java.lang.IllegalArgumentException: URI is not absolute
at
org.apache.juddi.config.AppConfig.getPersistentConfiguration(AppConfig.java:122)
at
org.apache.juddi.config.AppConfig.loadConfiguration(AppConfig.java:95)
When I try deploying juddiv3.0.2 on JBoss 5.1 AS I get a ClassNotFoundException
15:14:21,787 ERROR [[/juddiv3]] Servlet /juddiv3 threw load() exception
java.lang.ClassNotFoundException: org.apache.juddi.model.Address
Caused by: java.io.IOException: Child not found
juddiv3.war/WEB-INF/lib/juddi-core-3.0.1.jar/juddi_install_data/root_tModelKeyGen.xml/
for filehand...@3378572
> vfszip: URI protocol not absolute
> ---------------------------------
>
> Key: JUDDI-301
> URL: https://issues.apache.org/jira/browse/JUDDI-301
> Project: jUDDI
> Issue Type: Bug
> Components: core
> Affects Versions: 3.0
> Reporter: Kurt T Stam
> Assignee: Tom Cunningham
> Fix For: 3.0.1
>
>
> When deploying to jboss 5.1, when exploring the install data, if it is in the
> jar, the path is prefixed with vfszip:, which causes issues when turning this
> into a URI in the code.
> WORKAROUND; use the custom_juddi_install_data directory.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
