For that war another option would be to simple reduce the session
timeout down to a few minutes and that should clean them up quicker,
won't proactively invalidate them but might be short term work
around.
Alternatively add a filter that wraps the axis services your wanting
to invalidate, the jus
ikant Sarade wrote:
> I had Created Web Service Java Client Using AXIS 2 (Using Eclipse IDE).
> But when i use client bean into JSP page for my Web App. I get errors...
>
>
> On Sun, Apr 8, 2012 at 10:33 PM, John Patrick
> wrote:
>>
>> More context in your que
Apr 8, 2012 at 8:09 PM, John Patrick wrote:
>>
>> If I understand your question correctly then, your client is not
>> limited to any language. That is the advantage of web services, as
>> long as the server and client are using the same wsdl then it works.
>>
>>
If I understand your question correctly then, your client is not
limited to any language. That is the advantage of web services, as
long as the server and client are using the same wsdl then it works.
But if your wanting to automatically generate a client using Axis 2,
your then limited to Java an
Is it possible to stop wsdl2java from generating xmlbeans?
I believe that I have check every combination of true and false in the
generate options, but still can't find a combination that stops the
xmlbeans from being generated.
I'm working on a JEE application that basically exists of 8 maven mo
