axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Durham <david.durham...@gmail.com>
Subject Re: running axis server standalone
Date Wed, 10 Mar 2010 21:56:26 GMT
I should also add that I do not intend to have an axis2.xml file
anywhere.  I want to have complete control over the initialization of
my axis environment programatically.    These seems to be more
difficult than it should be.

Thanks,
Dave

On Wed, Mar 10, 2010 at 3:39 PM, David Durham <david.durham.jr@gmail.com> wrote:
> So I'm doing something unusual, I have a spring namespace handler so
> that I end up with a spring config like this:
>
> <bead id="myService" class="...">
>    <webservice:endpoint/>
> </bean>
>
>
> Where <webservice:endpoint/> is my magic where I end up with requests
> routed to a Handler.  Now, my handler logic looks basically like this:
>
> if (requestURL.endsWith(".wsdl") {
>
>    // serve up the wsdl
>
> } else {
>
>   // actually do the service call via soap
>
> }
>
> The first part works.  I'm having trouble with the second part,
> actually handling the service call.  My first instinct was just to try
> to extend AxisServlet and provide my own AxisConfigurator, and
> override some of the protected methods, createMessageContext(..) for
> instance.  But this is not going very well.  Can anyone point me to or
> provide me with some info about how to get this done?  I have a
> reference to the spring "bean" that will actually be invoked -- the
> one that would be returned by SpringServletContextObjectSupplier if I
> were going that route.
>
> Thanks,
> Dave
>

---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
For additional commands, e-mail: java-user-help@axis.apache.org


Mime
View raw message