Bryan Pendleton wrote:
I can see juddi in the admin screen of Glassfish. In can enter
http://localhost:8080/juddiv3 and the welcome screen pops up.
Clicking on
juddi Portal also results in 404.
The portal is a separate WAR file, and must be separately deployed.
Did you do that step? (I wasn't sure from your mail.)
That's right, see the portal bundle.
Regarding your main question, I don't know why
http://localhost:8080/juddiv3
would work but http://localhost:8080/juddiv3/services would not.
Did you look in your app server logs for error messages? In particular,
try to figure out where your app server is placing 'juddi.log', which
has lots of useful information.
If you use a full-fledged appserver (recommeded) then the juddiv3.war
can be really small, as you can leverage the WS stack and JPA provider
from the appserver.
For JBoss a good example is
http://people.apache.org/~kstam/releases/juddi-3.0.0/jboss-5.1.0.GA.tgz
We'd love to add the documentation on how to deploy to glassfish.
Hope this helps,
bryan
