[
https://issues.apache.org/jira/browse/JUDDI-301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12870924#action_12870924
]
David Jitendranath commented on JUDDI-301:
------------------------------------------
Thanks Kurt for the response. Yes, the war is exploded.
What does 'use the custom install directory' mean?
Following the juddi user guide to deploy to JBoss 5.1, What I've done is
downloaded juddiv3.0.1.war and unzipped it to update persistence.xml and added
jboss-web.xml file.
The juddi_install_data/root_Publisher.xml is within the juddi-core-3.0.1.jar
and is part of the exploded war which I then deploy.
Can you please explain what I should do to use the custom install directory?
I tried juddiv3.0.2 too but then I get a ClassNotFoundException (see logs in my
previous comment).
I do see the classes within the juddi-core-3.0.1.jar though.
> 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.
