Jetty - embedded with Axis

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Jetty - embedded with Axis

Greg Kopff
G'day all.

We use Jetty here in a bunch of applications -- and what we love about
Jetty is that it's embeddable.  We use Jetty to _expose_ HTTP
functionality; we don't make our application sit in an application
server (to us, that would be turning the thing upside down).

My question then, relates to using Apache Axis and SOAP, from Jetty --
but still embedding Jetty.  But first, some context ...

My company builds betting systems (not internet casinos, but real
betting systems such as lotteries and totalisators), and to us,
efficiency is very important.  I confess then, that I strongly agree
with this paragraph from Wikipedia regarding SOAP:

   "SOAP makes use of an Internet application layer protocol
   as a transport protocol. Critics have argued that this is
   an abuse of such protocols, as it is not their intended
   purpose and therefore not a role they fulfil well."

However, we have been asked to explore the possibility of providing a
SOAP interface to some aspects of the system.  If I'm forced to do this,
I would like to use Jetty.

Having a quick read (using Safari) of "Building Web Services with Java:
Making Sense of XML, SOAP, WSDL, and UDDI, Second Edition", Apache Axis
seems to be a good place to start.  (So, I'd like to ask those who know
more than me: is it?)

I found here ( http://wiki.apache.org/ws/FrontPage/Axis/Install/Jetty )
some instructions for using Axis with Jetty, but this assumes you're
using Jetty as an application server.  Can anyone comment on whether or
not it feasible to use Jetty+Axis in an embedded configuration?

Or, can someone suggest something other than Axis?  I have quite simple
requirements.  I don't need (nor do I want!) to be able to "hot deploy"
anything, nor assemble new SOAP messages on-the-fly.  All I want is a
simple way of responding to fixed, known SOAP requests, and present
responses wrapped in a neat little SOAP envelope.

(I know I don't ask hard and fast questions, but I'm still at the
fishing for information stage).

Any insight, or links to useful information would be greatly appreciated.

Kindest regards,

--
  Greg Kopff
===================================================
[hidden email]      PowerSource Software
Chief Technologist    http://www.powersource.com.au
===================================================
   did you know 'if' is the middle word in 'life'?
===================================================
                     Typhoon
        a revolution in wagering & gaming
            http://www.typhoon.com.au/
===================================================

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Jetty-support mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/jetty-support
Reply | Threaded
Open this post in threaded view
|

Re: Jetty - embedded with Axis

jan_bartel
I'm not taking sides in the eternal SOAP wars ;-) ... but the other impl to
look closely at is XFire:

http://xfire.codehaus.org/


cheers
Jan

Greg Kopff wrote:

> G'day all.
>
> We use Jetty here in a bunch of applications -- and what we love about
> Jetty is that it's embeddable.  We use Jetty to _expose_ HTTP
> functionality; we don't make our application sit in an application
> server (to us, that would be turning the thing upside down).
>
> My question then, relates to using Apache Axis and SOAP, from Jetty --
> but still embedding Jetty.  But first, some context ...
>
> My company builds betting systems (not internet casinos, but real
> betting systems such as lotteries and totalisators), and to us,
> efficiency is very important.  I confess then, that I strongly agree
> with this paragraph from Wikipedia regarding SOAP:
>
>    "SOAP makes use of an Internet application layer protocol
>    as a transport protocol. Critics have argued that this is
>    an abuse of such protocols, as it is not their intended
>    purpose and therefore not a role they fulfil well."
>
> However, we have been asked to explore the possibility of providing a
> SOAP interface to some aspects of the system.  If I'm forced to do this,
> I would like to use Jetty.
>
> Having a quick read (using Safari) of "Building Web Services with Java:
> Making Sense of XML, SOAP, WSDL, and UDDI, Second Edition", Apache Axis
> seems to be a good place to start.  (So, I'd like to ask those who know
> more than me: is it?)
>
> I found here ( http://wiki.apache.org/ws/FrontPage/Axis/Install/Jetty )
> some instructions for using Axis with Jetty, but this assumes you're
> using Jetty as an application server.  Can anyone comment on whether or
> not it feasible to use Jetty+Axis in an embedded configuration?
>
> Or, can someone suggest something other than Axis?  I have quite simple
> requirements.  I don't need (nor do I want!) to be able to "hot deploy"
> anything, nor assemble new SOAP messages on-the-fly.  All I want is a
> simple way of responding to fixed, known SOAP requests, and present
> responses wrapped in a neat little SOAP envelope.
>
> (I know I don't ask hard and fast questions, but I'm still at the
> fishing for information stage).
>
> Any insight, or links to useful information would be greatly appreciated.
>
> Kindest regards,
>


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Jetty-support mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/jetty-support
Reply | Threaded
Open this post in threaded view
|

Re: Jetty - embedded with Axis

Nik Gonzalez
In reply to this post by Greg Kopff
Greg,

 From the wiki page you gave, seems like setting up Axis with jetty is
as simple as including some required jars in the classpath and deploying
the axis webapp. Let me point you to some helpful content on the Jetty wiki.

If you want to just specify a directory from where you can just drop
your webapps (or in this case the axis webapp) you can use the
WebAppDeployer (http://docs.codehaus.org/display/JETTY/WebAppDeployer)

You can also deploy webapps individually. There's an example here:
http://docs.codehaus.org/display/JETTY/How+to+serve+webbapp+A+from+portA+and+webapp+B+from+portB

The wiki pages above all configure jetty with jetty.xml but that's
easily converted to java code. Here's an example in the jetty/examples
that may help you on this:
http://jetty.mortbay.org/xref/org/mortbay/jetty/example/LikeJettyXml.html

HTH,
Nik

Greg Kopff wrote:

> G'day all.
>
> We use Jetty here in a bunch of applications -- and what we love about
> Jetty is that it's embeddable.  We use Jetty to _expose_ HTTP
> functionality; we don't make our application sit in an application
> server (to us, that would be turning the thing upside down).
>
> My question then, relates to using Apache Axis and SOAP, from Jetty --
> but still embedding Jetty.  But first, some context ...
>
> My company builds betting systems (not internet casinos, but real
> betting systems such as lotteries and totalisators), and to us,
> efficiency is very important.  I confess then, that I strongly agree
> with this paragraph from Wikipedia regarding SOAP:
>
>    "SOAP makes use of an Internet application layer protocol
>    as a transport protocol. Critics have argued that this is
>    an abuse of such protocols, as it is not their intended
>    purpose and therefore not a role they fulfil well."
>
> However, we have been asked to explore the possibility of providing a
> SOAP interface to some aspects of the system.  If I'm forced to do this,
> I would like to use Jetty.
>
> Having a quick read (using Safari) of "Building Web Services with Java:
> Making Sense of XML, SOAP, WSDL, and UDDI, Second Edition", Apache Axis
> seems to be a good place to start.  (So, I'd like to ask those who know
> more than me: is it?)
>
> I found here ( http://wiki.apache.org/ws/FrontPage/Axis/Install/Jetty )
> some instructions for using Axis with Jetty, but this assumes you're
> using Jetty as an application server.  Can anyone comment on whether or
> not it feasible to use Jetty+Axis in an embedded configuration?
>
> Or, can someone suggest something other than Axis?  I have quite simple
> requirements.  I don't need (nor do I want!) to be able to "hot deploy"
> anything, nor assemble new SOAP messages on-the-fly.  All I want is a
> simple way of responding to fixed, known SOAP requests, and present
> responses wrapped in a neat little SOAP envelope.
>
> (I know I don't ask hard and fast questions, but I'm still at the
> fishing for information stage).
>
> Any insight, or links to useful information would be greatly appreciated.
>
> Kindest regards,
>
>  


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Jetty-support mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/jetty-support