As far as I've seen from 1.0RC5 on SVN, new name of the security module
is rampart. Good choice :)
--- Eran Chinthaka [EMAIL PROTECTED] wrote:
Sanjiva Weerawarana wrote:
OK how about Apache Sigiri?
+1. And it was considered as one of the high security places in
ancient
days.
So
Hi all,
Does anyone know if AXIS is compliant with WSDL 2.0. I tried using the WSDL
to Java Ant task on a WSDL 2.0 file and got exceptions. It did not recognise
the description tag.
Regards
Jim
Hi Deepal,
I'm currently running 1.0RC5 and still have the same problem.
May be, as you said, I need somehow to use ListenerManager. Could you
please tell me what to do?
Thanks,
Ali Sadik Kumlali
--- Deepal Jayasinghe [EMAIL PROTECTED] wrote:
Hi Sadik;
In the current code base we done a
Can u please log a bug report? i almost missed this one.
thanks,
dims
On 4/30/06, robert lazarski [EMAIL PROTECTED] wrote:
Hi all,
I'm using RC4 for this example. I'm written a very simple example to
explain my problem. Can somebody please give a quick look - it must be
something simple but
Hello everyone,
We are STRUGGELING to connect our soap client to our axis server for some
time now, PLEASE HELP !
We suspect there is a problem with the encodingStyle. We created a test client
(using axis) and it works ok. After comparing the soap message (obtained
using sniffer)
from our
You have to engage addressing in client side as well. There should be
AddressingOutHandler in the client side to serialize the reference
parameters you have put.
I updated the documentation on this, and waiting for the Chatra to
update the site. In the mean while you can check it here :
Hi all,
As you know, EchoNonBlockingDualClient calls MyService and waits the
response by launching SimpleHTTPServer on port 6060.
Could someone check the correctness of the following flow, please?
C: client
S: server
[C-S] open connection to the server's endpoint
[C-S] send request SOAP with
Hello,
Is there really no way to enable encodingStyle when using rpc literal ?
In the request I recieve from some (soap) client there is an encodingStyle,
but the response from my axis server has no encodintStyle. I suspect this is
the cause why my clients to throw an exception.
client request:
Hello,
Is there really no way to enable encodingStyle when using rpc literal ?
In the request I recieve from some (soap) client there is an encodingStyle,
but the response from my axis server has no encodintStyle. I suspect this is
the cause why my clients to throw an exception.
client request:
Perhaps you can check this comand
Try this,
WSDL2Java -uri file.wsdl -ss -sd -p com.maryam.grid -d xmlbeans -g
if you are using namespaces in your wsdl, can use without specifiying
-p option.
Further you can send your wsdl for reference.
Kensky
On 5/1/06, Maryam Moazeni [EMAIL PROTECTED]
Hi Robert,
Thanks! After running maven release ran into 2 issues: 1st one was maven asking for a username. After specifying the user name on the cmd line, the build failed trying to create a process that would secure shell. Any tips here? The output from maven release and maven -
11 matches
Mail list logo