Hi Thomas, I´m just about to commit a pragmatic solution to that issue (need only to get the testcase running ;-).
Since we have the JSR109 sub-deployment solution, we have access to the parent deployment info including the local installation dir of the war. JSR109Service (or better the WebService metadata) will, upon the create step, replace any occurence of a "web-service-servlet" by our AxisServiceServlet tied to the AxisService/AxisServer where the POJO is installed as an ordinary service. (#1 - is then not a problem anymore, only in cases where JSR109 is not present ... But then, the webservices wont work anyway). #3 - The servlet/service context will be compiled into the MessageContext, anyway. Is there any place in the spec where this plays a role in the JavaBean? I do not know what question #2 is targetting at? CGJ > -----Ursprüngliche Nachricht----- > Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Gesendet: Montag, 17. November 2003 17:15 > An: Jung Christoph (E-mail); Stark Scott (E-mail); Bill Burke (E-mail) > Cc: Jboss-Development (E-mail) > Betreff: JBoss.NET: web service components as web module > > > Hi folks, > > J2EE1.4 compliant webservices can be implemented as web > components. First I'll tell you briefly how it works then > I'll come to some JBoss specific design issues/problems. > > This is how it works: > > 1. In webservices.xml specify a <servlet-link> MyService > </servlet-link> 2. In web.xml use <servlet-name> MyService > </servlet-name> 3. In web.xml use <servlet-class> > com.mypackage.MyServiceBean </servlet-class> to name the > service endpoint implementation bean > > So far so good, but com.mypackage.MyServiceBean can be any > ordinary POJO - it does not have to be javax.servlet.Servlet. > > Issues > ------ > > #1 How should the servlet container behave when > <servlet-class> is not a servlet > > #2 If the SE bean is a servlet, is there any way to invoke a > method (the actual service method) on it - the > org.jboss.web.AbstractWebContainer does not provide a list of > deployed (servlet) objects > > #3 I think we need the above mentioned access, in case the > service method needs access to the ServletContext or > ServletConfig parameters > > The current (draft) implementation creates a new service bean > for every request, regardless wether it is a servlet or not. > > Cheers > -thomas > > > > > ########################################### This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange. For more information, connect to http://www.F-Secure.com/ ------------------------------------------------------- This SF. Net email is sponsored by: GoToMyPC GoToMyPC is the fast, easy and secure way to access your computer from any Web browser or wireless device. Click here to Try it Free! https://www.gotomypc.com/tr/OSDN/AW/Q4_2003/t/g22lp?Target=mm/g22lp.tmpl _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
