[
http://jira.jboss.com/jira/browse/JBAS-5464?page=all ]
Galder Zamarreno updated JBAS-5464:
-----------------------------------
Attachment: jboss-http-naming.jar
I've created this jar out of the classes in
deploy/http-invoker.sar/invoker.war/WEB-INF/classes/
and put it under the lib directory so that both http-invoker.sar and
unified-http-invoker.sar share
them.
We will need to produce such jar out of our build system for AS 4.2.x. For AS 5, we might
not need
it as legacy invoker descriptors are not distributed any more, but it'd be good to
keep things separate.
Distribute unified-http-invoker.sar package for accessing JNDI, EJB2s
and EJB3s over Unified HTTP invoker
---------------------------------------------------------------------------------------------------------
Key: JBAS-5464
URL:
http://jira.jboss.com/jira/browse/JBAS-5464
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Components: EJB2, Naming, Remoting, EJB3
Affects Versions: JBossAS-5.0.0.Beta4, JBossAS-4.2.2.GA
Reporter: Galder Zamarreno
Assigned To: Galder Zamarreno
Attachments: jboss-http-naming.jar
In the same way that we've been provided the http-invoker.sar, AS should
now distribute the Unified invoker equivalent. Instructions on how to build
this can be found in:
http://wiki.jboss.org/wiki/EJBAndJNDIOverHTTPWithUnifiedInvoker
The way we should package this is up for debate. I'll start a design forum
thread when the time discuss this comes.
I'll attach a fully working unified-http-invoker.sar and example EJB that uses
it in a minute.
Any potential outcome of generating unified-http-invoker.sar for AS should
probably also include services needed for EJB3:
http://wiki.jboss.org/wiki/Accessing_EJB3s_over_HTTP_HTTPS
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira