Hi Paul, thanks for reply.No,basically I don't know if I need a servlet engine. This idea cames up to my mind because I saw that the Apache Muse is building a .war as deliverable and therefore in order to use it I need a servlet container. Otherwise I don't know how to install the muse built WS-DM (layer) module on a standalone axis.
Regards, Andrea 2008/11/10 Paul Fremantle <[EMAIL PROTECTED]> > Andrea > > Axis2 has a built in HTTP server, including a high-performance NIO > based one, so you don't need a servlet container if you don't want > one. Alternatively, Jetty is small and embeddable. > > Paul > > On Mon, Nov 10, 2008 at 11:55 AM, Andrea Gazzarini > <[EMAIL PROTECTED]> wrote: > > Hi Arnaud, we thought the same thing...just a moment please read the > > following : > > I was just having a look to apache muse and it seems that they have > > something we need.The problem is that the final artifacts is something > > deployable on a web server....but at this point I think it's the only > > way....WS-DM is an application protocol over SOAP so, if you want to use > it > > (SOAP) over HTTP (and we want because SOAP / RMI is still a java coupled > > solution) you need a HTTP Server and a servlet engine (i.e. web services > > engine) > > > > As proof of that Muse is using its layer for WS-DM and relying on > > preexisting Axis2 for web service > > > > I'm continuing to investigate... > > > > Thanks for reply > > > > Regards, > > Andrea > > > > 2008/11/10 Arnaud Simon <[EMAIL PROTECTED]> > > > >> Hi Andrea, > >> > >> Would it be possible to do 2) then 1) ? I.E. could we extend 2) so to > >> achieve 1)? > >> > >> Arnaud > >> > >> ----- "Andrea Gazzarini" <[EMAIL PROTECTED]> wrote: > >> > >> > Hi all, > >> > Considering that final goal of QMan is to expose remote broker(s) > >> > management through a standard and language-independent interface, > >> > what > >> > do you think about the following options? > >> > > >> > - WS-DM adapter will be developed as a JCA (1.5) inbound connector > >> > - WS-DM adapter will be developed as a plain JMX connector; > >> > > >> > The advantages of the first option are basically the preexisting > >> > capabilities offered by the JEE infrastructure (transactions, > >> > security, pooling, etc...) but in this way the connector will be > >> > available only when QMan is deployed on a JEE 1.3 (or higher) > >> > container > >> > For the second options the JMX connector should be deployed basically > >> > "from scratch" :( and therefore could have a high level of > >> > customization > >> > > >> > I've done some search on internet and I found. Something similar > >> > only > >> > on IBM web site: I don't know exactly but it seems they followed the > >> > first scenario > >> > > >> > Please let me know what is your opinion about that > >> > > >> > Regards, > >> > Andrea > >> > > > > > > -- > Paul Fremantle > Co-Founder and CTO, WSO2 > Apache Synapse PMC Chair > OASIS WS-RX TC Co-chair > > blog: http://pzf.fremantle.org > [EMAIL PROTECTED] > > "Oxygenating the Web Service Platform", www.wso2.com >
