JBossDeveloper

Does this still hold true for jBoss 3.2.1?
I've followed all the steps and still I get a 404 and the RootNotFoundHandler is registered in consequence that serves a page that shows all registered contexts.

I've got a feeling that this could be related to the fact that http-invoker delegates to jboss-web and as a result it is not jboss-web who determines what is mapped to '/'

So then the question would be: how do I register this webapplication with http-invoker to be mapped to root?

groetjes,
Joost

(the above post was a reply to the explanation of mapping a webapp to '/')

I've done some experimenting: it IS possible to serve a /index.jsp for instance from jBoss 3.2.1
But I haven't found the proper way to do it. At the moment I've put the index.jsp in the deploy/invoker.sar/invoker.war directory and added a line to deploy/invoker.sar/invoker.war/META-INF/jboss-web.xml so that the result reads:
<jboss-web>
<context-root>/</context-root>
<security-domain>java:/jaas/http-invoker</security-domain>
</jboss-web>

But I'm still interested in the proper way to do it.

groetjes,
Joost

Finally got it working. I'm logging my solution here in case anybody winds up here having the same problem: specifying the context by wrapping the war in an ear and specifying a context DOES work. See the jobss30quickstart.pdf
Good luck.

sir,

this actually not a reply but a question.
I am new to jboss . I just downloaded jboss latest version few days ago and i deployed a hello.jar and its getting deployed successfully. But when i try to run client application it gives me a runtime exception stating
classnotfoundexception: javax.socketFactory npt found.
Icouldnt figure out the error i have made.
If u could help me i could much obliged.

God Bless you