All -
I have a service in place the returns a set of attachments using SwA. These
attachments are generated on the server and placed in a tmp directory before
they are returned.
I've implemented the Lifecycle interface so I can cleanup the tmp files
after the service returns in the destroy metho
Issue resolved, thanks!
On Mon, Nov 29, 2010 at 11:38 AM, Andreas Veithen wrote:
> Yes. And you should configure your axis2.xml as described in [1].
>
> Andreas
>
> [1] http://axis.apache.org/axis2/java/core/docs/servlet-transport.html
>
> On Mon, Nov 29, 2010 at 17:32
1.5.2 Do you suggest an upgrade to 1.5.3 ?
On Mon, Nov 29, 2010 at 11:29 AM, Andreas Veithen wrote:
> Which version of Axis2 do you use? There are known problems in
> versions before 1.5.3.
>
> Andreas
>
> On Mon, Nov 29, 2010 at 17:01, Christopher Johnson
> wrote:
&
I tried the change to the transportReceiver, and saw no change the the
endpoint in the WSDL.
My transportSender is just using the default one provided by axis2, I do not
see a port parameter field in it.
On Mon, Nov 29, 2010 at 11:16 AM, Martin Gainty wrote:
> Receiver configuration in ./WEB-
All -
I've published a web service using Axis2 yet I have identified a mismatch
between the URI in the browser, and where the service is running compared to
the WSDL that is generated.
My browser address is:
https://myserver/axis2/services/MyService?wsdl
yet the address found in the WSDL look l
