This sounds very similar to what I'm already doing (everything in
webapps/axis is being put into a .war file, and we are adding our own
service .jar files into the WEB-INF/lib directory so that Axis can find
them).
We have the need to deploy Axis on a system, and then at random points in
the future, add new Axis services without shutting down JBoss or
re-deploying Axis itself. This would essentially mean dropping a new .jar
file on the system, and running the AdminClient. The problem is: how does
the Axis servlet know how to get at the newly deployed .jar file? It won't
be in the CLASSPATH when deployed on the system, and it won't be located
in the axis.war file.
As far as adding axis.jar to each service when it gets deployed, I'm not
sure this will work.
Have I misinterpreted your statement?
Thanks.
-Mark
--------------------------------------------------
There is no spoon.
--------------------------------------------------
"Steve
Loughran" To: <[EMAIL PROTECTED]>
<steve_l@isera cc:
n.com> Subject: Re: Web Service and EJB with
Axis and JBoss
05/20/2002
02:12 PM
Please respond
to axis-user
It's fairly easy to axis-enable your own webapp
1. add the axis.jar and other needed jars to your libs
2. add the axis configuration stuff to web.xml
that's it.
----- Original Message -----
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, May 20, 2002 10:48 AM
Subject: RE: Web Service and EJB with Axis and JBoss
> The axis.war contains the EJB client classes.
> The EJB server classes are deployed separately.
> But the EJB client classes are the implementation of my web services and
> they are part of the axis.war. I am not addressing what you are trying to
do
> for sure (which I am not sure there is a solution for, unless using proxy
> servlet or classes, I guess).
>
> Thomas
>
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Monday, May 20, 2002 1:16 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Web Service and EJB with Axis and JBoss
>
>
>
> Quick question for you on this Thomas (I have not had the time to look at
> the contents yet).
>
> When deploying under JBoss, did you combine your services within the .war
> file that you needed to deploy for Axis? Or were you able to
> deploy them separately (this is what I really have a need to do, and I'm
> not sure how you would go about it, or if it's even possible)? The key
> element here is not having to redeploy Axis each time a new service is to
> be added to the system.
>
> BTW, thanks for putting this example out for people - I'm sure many will
> appreciate it.
>
> -Mark
>
> --------------------------------------------------
> There is no spoon.
> --------------------------------------------------
>
>
>
>
> thomas.cherel@ascentialso
>
> ftware.com To:
> [EMAIL PROTECTED], [EMAIL PROTECTED]
> cc:
>
> 05/20/2002 12:58 PM Subject: Web
Service
> and EJB with Axis and JBoss
> Please respond to
>
> axis-user
>
>
>
>
>
>
>
>
>
> Here is a zip file containing some code and documentation to build and
run
> some web services implemented as EJBs. The EJBs are deployed in JBoss,
the
> web services are deployed into Axis. Axis is deployed into Tomcat (which
is
> bundled with JBoss). The web services are very simple (echo and count
type
> of operations). The point of this distribution is from an integration
point
> of view.
>
> Here is what is covered:
> Axis web services implemented using EJBs
> Request and session scope web service with stateless and
stateful
> EJBs
> JAAS security applied on the EJBs implementation, allowing
> security on the web services
> HTTPS encryption for some of the web services
> Java web service client application (using Axis client API)
with
> JAAS security and HTTPS.
> C# .NET web service client application with JAAS security and
> HTTPS.
> VBScript MSSoap Toolkit web service client application with
JAAS
> security. Could not yet make HTTPS working.
>
>
> The axis mailing list helped me a lot to put all that together, so feel
> free to reuse it as much as needed. If you find any issues or if you
> improve it, I will be happy to integrate the changes.
>
>
> To the Axis development team, if you want to include some of this (or all
> of it) in the Axis distribution and/or documentation, no problem for me.
>
>
> Thomas
>
>
> <<AxisJBossWebServices.zip>> (See attached file:
AxisJBossWebServices.zip)
>
>
>
>
>
>
