[ http://jira.jboss.com/jira/browse/JBREM-35?page=history ]
Thomas Diesler updated JBREM-35:
Priority: Optional (was: Minor)
Fix Version: 1.2.0 beta
(was: 1.0.1 final)
It needs to be discussed who this would work with the WS4EE deployment model
for JSE. As a reminder, it uses the element to the declare the
endpoint implemenation bean.
What would be the benefit of running server side JBossWS with a dependency on
Remoting rather than Tomcat?
> Servlet Invoker - counterpart to HTTP Invoker (runs within web container)
> -
>
> Key: JBREM-35
> URL: http://jira.jboss.com/jira/browse/JBREM-35
> Project: JBoss Remoting
> Type: Feature Request
> Components: transport
> Versions: 1.0.1 beta
> Reporter: Tom Elrod
> Assignee: Tom Elrod
> Priority: Optional
> Fix For: 1.2.0 beta
>
>
> Need a servlet invoker that will be the same as the HTTP Invoker (which is
> its own web server), but will run inside a web container (such as Tomcat) as
> a servlet. Will then process request same as HTTP Invoker after
> doPost()/doGet() called.
--
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
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
