Re: Improved Error Response for Bad Requests on ADB
Hi Amila,
Sorry for the late response but I've been very busy last days trying to finish
my final project to get my degree.
Yes it is true that when there is a NPE the excepcion should be thrown as Axis2
fault. As you can see, in exception A, the message contains an Axis2 fault and
is well formed but the client seems to have a little confusion because when
client receives this one, it receives it as a Remote Exception instead of Axis2
fault.
If the client does e.getMessage(), the message printed is: unknown.
If it does e.printStackTrace(), the message printed is:
org.apache.axis2.AxisFault: unknown
at
org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:486)
at
org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:343)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:389)
at
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:211)
at org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)
at client.Medici_LinkStub.validate (Medici_LinkStub.java:1044)
at client.ClientUtilities.validateTest(ClientUtilities.java:57)
at client.Client.main(Client.java:72)
What is strange to me is the getInboundFaultFromMessageContext(Utils.java:486).
As I said, the exception is well formed but besides of being an Axis2 fault,
the action is validateDataAccessException and I don't know if that is right.
In the case of exception B, it was thrown from the message receiver, not from
the skeleton, in the try {}catch inside invokeBusinessLogic method, inside the
following if statement:
if((op.getName()!=null) ((methodName=
org.apache.axis2.util.JavaUtils.xmlNameToJava(op.getName.getLocalPart()))!=null))
I'm doing
if(sessionControl.getSystem==null)
buildValidationException(SYSTEM NOT VALIDATED. YOU MUST VALIDATE BEFORE
INVOKING A METHOD.);
that is the place where I sent exception B, and that is the case when the fault
action was sent wrongly. The buildValidationException method was this:
public static ValidationException buildValidationException(String _message,
Logger _logger){
if(_logger!=null)
_logger.error(_message);
ValidationException exception=new ValidationException(Validation
Fault);
ValidationFault fault=new ValidationFault();
fault.setDescription(_message);
exception.setFaultMessage (fault);
return exception;
}
Thanks,
Jorge Fernández
Exception A
HTTP/1.1 500 Error Interno del Servidor
Server: Apache-Coyote/1.1
Content-Type: application/soap+xml;
action=urn:validateDataAccessException;charset=UTF-8
Transfer-Encoding: chunked
Date: Fri, 31 Aug 2007 11:01:01 GMT
Connection: close
b36
?xml version='1.0' encoding='UTF-8'?
soapenv:Envelope xmlns:soapenv=
http://www.w3.org/2003/05/soap-envelope;
xmlns:wsa=http://www.w3.org/2005/08/addressing
soapenv:Header
wsa:Actionurn:validateDataAccessException/wsa:Action
wsa:RelatesTourn:uuid:578695F1A346B244751188558061265/wsa:RelatesTo
/soapenv:Header
soapenv:Body
soapenv:Fault
soapenv:Code
soapenv:Valuesoapenv:Receiver/soapenv:Value
/soapenv:Code
soapenv:Reason
soapenv:Text xml:lang=en-USunknown/soapenv:Text
/soapenv:Reason
soapenv:Detail
Exception
org.apache.axis2.AxisFault#xd; at
org.apache.axis2.AxisFault.makeFault(AxisFault.java:417)#xd;at
medici_link.Medici_LinkMessageReceiverInOut.invokeBusinessLogic(Medici_LinkMessageReceiverInOut.java:388)#xd;
at
org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.invokeBusinessLogic
(AbstractInOutSyncMessageReceiver.java:42)#xd; at
org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java
:96)#xd; at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java
:145)#xd; at
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:275)#xd;
at org.apache.axis2.transport.http.AxisServlet.doPost
(AxisServlet.java:120)#xd;at
javax.servlet.http.HttpServlet.service(HttpServlet.java:710)#xd;at
javax.servlet.http.HttpServlet.service(HttpServlet.java:803)#xd;at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter
(ApplicationFilterChain.java:290)#xd; at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)#xd;
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java
:228)#xd; at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)#xd;
at
RE: destroy
Hi, I didn't receive any response about that. Is this a bug? I close sessions manually and when I turn off Axis2, destroy method is called again so I got NPE because some elements I destroyed in that method were already destroyed. Thanks, Jorge Fernández Jorge Fernandez [EMAIL PROTECTED] escribió: Hi, I'm using SOAP sessions and I'm testing my Web service opening and closing sessions and I can see sometimes in the logs that the session is being closed more than once. Sometimes, this happens with more than one minute of difference. And when I shutdown Tomcat, all sessions are closed again. I have a method called logout that invokes destroy for cleaning axis2 session when the clients wants to close the session manually. How does Axis2 manage sessions? What may be happening here? Thanks, Jorge Fernández - Sé un Mejor Amante del Cine ¿Quieres saber cómo? ¡Deja que otras personas te ayuden! . - Sé un Mejor Amante del Cine ¿Quieres saber cómo? ¡Deja que otras personas te ayuden!.
RE: Timeout
Hi again, Could anybody tell me something about this? I'm in a hurry because I have to finish my project this week so I would like to know it in order to incorporate the changes that should be done to the project. Thanks, Jorge Fernández Jorge Fernandez [EMAIL PROTECTED] escribió: Hi all, I'm usign axis2 1.3 and I could see that one of the changes made was about timeout. Now, while debugging my service, I get timeouts because axis2 removes contexts but I was managing this timeouts myself so I would like to deactivate axis2 timeouts. Is this possible? I thought that maybe I could do it by setting timeout to 0 but it doesn't work. Thanks, Jorge Fernández - Sé un Mejor Amante del Cine ¿Quieres saber cómo? ¡Deja que otras personas te ayuden! . - Sé un Mejor Amante del Cine ¿Quieres saber cómo? ¡Deja que otras personas te ayuden!.
MTOM problems
Hi all, I'm having some problems in axis2 1.3 with MTOM attachments. When receiving message included in attached file message2 there is no problem but my client has this exception when receiving message included in attached file message1: org.apache.axis2.AxisFault: Referenced Attachment not found in the MIME Message. ContentID:1.urn:uuid:[EMAIL PROTECTED] at org.apache.axis2.AxisFault.makeFault(AxisFault.java:417) at client.Medici_LinkStub.fromOM(Medici_LinkStub.java:50213) at client.Medici_LinkStub.getSignalData(Medici_LinkStub.java:6500) at client.ClientUtilities.getSignalDataTest(ClientUtilities.java:600) at client.Client.main(Client.java:172) Caused by: org.apache.axiom.om.OMException: Referenced Attachment not found in the MIME Message. ContentID:1.urn:uuid:[EMAIL PROTECTED] at org.apache.axiom.soap.impl.builder.MTOMStAXSOAPModelBuilder.getDataHandler(MTOMStAXSOAPModelBuilder.java:106)Closing session... at client.Medici_LinkStub$ExtDataSegment$Factory.parse(Medici_LinkStub.java:34167) at client.Medici_LinkStub$ExtSignalData$Factory.parse(Medici_LinkStub.java:35862) at client.Medici_LinkStub$GetSignalDataResponse$Factory.parse(Medici_LinkStub.java:8777) at client.Medici_LinkStub.fromOM(Medici_LinkStub.java:49766) ... 3 more Some days before I was working with Rampart engaged and it worked fine. Message2 sent 8 bytes and Message1 sent 0 bytes but I think that the element wasn't null, so I think that may be the problem: sending 0 bytes. Thanks, Jorge Fernández - Sé un Mejor Amante del Cine ¿Quieres saber cómo? ¡Deja que otras personas te ayuden!.
RE: MTOM problems
Oops, forgot to attach files. They are in rar file. Jorge Fernandez [EMAIL PROTECTED] escribió: Hi all, I'm having some problems in axis2 1.3 with MTOM attachments. When receiving message included in attached file message2 there is no problem but my client has this exception when receiving message included in attached file message1: org.apache.axis2.AxisFault: Referenced Attachment not found in the MIME Message. ContentID:1.urn:uuid:[EMAIL PROTECTED] at org.apache.axis2.AxisFault.makeFault(AxisFault.java:417) at client.Medici_LinkStub.fromOM(Medici_LinkStub.java:50213) at client.Medici_LinkStub.getSignalData(Medici_LinkStub.java:6500) at client.ClientUtilities.getSignalDataTest(ClientUtilities.java:600) at client.Client.main(Client.java:172) Caused by: org.apache.axiom.om.OMException: Referenced Attachment not found in the MIME Message. ContentID:1.urn:uuid:[EMAIL PROTECTED] at org.apache.axiom.soap.impl.builder.MTOMStAXSOAPModelBuilder.getDataHandler(MTOMStAXSOAPModelBuilder.java:106)Closing session... at client.Medici_LinkStub$ExtDataSegment$Factory.parse(Medici_LinkStub.java:34167) at client.Medici_LinkStub$ExtSignalData$Factory.parse(Medici_LinkStub.java:35862) at client.Medici_LinkStub$GetSignalDataResponse$Factory.parse(Medici_LinkStub.java:8777) at client.Medici_LinkStub.fromOM(Medici_LinkStub.java:49766) ... 3 more Some days before I was working with Rampart engaged and it worked fine. Message2 sent 8 bytes and Message1 sent 0 bytes but I think that the element wasn't null, so I think that may be the problem: sending 0 bytes. Thanks, Jorge Fernández - Sé un Mejor Amante del Cine ¿Quieres saber cómo? ¡Deja que otras personas te ayuden! . - Sé un Mejor Amante del Cine ¿Quieres saber cómo? ¡Deja que otras personas te ayuden!. Escritorio.rar Description: 991782980-Escritorio.rar - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Improved Error Response for Bad Requests on ADB
Hi Amila,
For some exceptions it works fine. I'm getting 500 HTTP header for most or all
the exceptions but sometimes, the client doesn't get the reason of the
exception.
Attached file contains two exceptions received in the client. First one is a
null pointer exception. When client receives this one, it receives the
exception as a Remote Exception, and if it does e.getMessage(), the message
printed is: unknown.
If it does e.printStackTrace(), the message printed is:
org.apache.axis2.AxisFault: unknown
at
org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:486)
at
org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:343)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:389)
at
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:211)
at org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)
at client.Medici_LinkStub.validate(Medici_LinkStub.java:1044)
at client.ClientUtilities.validateTest(ClientUtilities.java:57)
at client.Client.main(Client.java:72)
As you can see in the message, there is a header describing the action and it
is this:
wsa:Actionurn:validateDataAccessException/wsa:Action
Why is it sending that action??
In services.xml, defined exceptions are:
faultActionMapping
faultName=ValidationExceptionurn:validateValidationException/faultActionMapping
faultActionMapping
faultName=DataAccessExceptionurn:validateDataAccessException/faultActionMapping
In second case I'm building a ValidationException in the service like this:
public static ValidationException buildValidationException(String _message,
Logger _logger){
if(_logger!=null)
_logger.error(_message);
ValidationException exception=new ValidationException(Validation
Fault);
ValidationFault fault=new ValidationFault();
fault.setDescription(_message);
exception.setFaultMessage(fault);
return exception;
}
but actions in SOAP message are those of DataAccessException. So it seems that
it's not working fine.
Client does:
System.out.println(AN EXCEPTION OCURRED: +e.getMessage()+:
+e.getFaultMessage().getDescription());
And the message printed is:
AN EXCEPTION OCURRED: ValidationException: SYSTEM NOT VALIDATED. YOU MUST
VALIDATE BEFORE INVOKING A METHOD.
So the client can see the exception OK but the SOAP message is not built
correctly.
Thanks,
Jorge Fernández
Amila Suriarachchi [EMAIL PROTECTED] escribió:
On 8/31/07, Geoff Peart [EMAIL PROTECTED] wrote: Took me until
now to upgrade to 1.3, and I agree, the error's are better now they zero in on
the one line of the exception that does matter:
faultstring org.apache.axis2.databinding.ADBException: Unexpected
subelement CategoryId / faultstring
this means ADB parser has encountered an in valid element. The reason for this
most of the time is the request
does not contain a requried element value.
eg lets take this element
xsd:element name=TestElement
xsd:complexType
xsd:sequence
xsd:element name=param1 type=xsd:string/
xsd:element name=param2 type=xsd:string/
/xsd:sequence
/xsd:complexType
/xsd:element
here both param1 and param2 are requried elements since they have the default
minOccurs=1 value.
a valid request for this elements is
TestElement
param1test/param1
param2test/param2
/TestElement
but if it receives a reqeust without param1 i.e.
TestElement
param2test/param2
/TestElement
Now after reading TestElement adb parser expects the param1 since it is a
required element. but it gets param2 which is an unexpected element.
So it throws an excpetion saying unexcpeted subelement param2.
To debug this first locate the CategoryID and check it has received the correct
element before that.
You can use the -Eosv option to let adb thinks every element is optional.
Amila.
But it doesn't really say where in the message that value was out of place, or
why its wrong, as in the case:
faultstring For input string: 2320asdf / faultstring
Where now I have the element in the correct location, but with an invalid
value (mixed text instead of a numerical value.)
So I'm at an impasse, do I rewrite my API to expect virtually any value, but
at least in a rigid structure, and do my validation in code, or leave my 3rd
parties with obscure error messages?
I'm hoping there is a 3rd choice I've missed?
Thanks
-
From: Jorge Fernandez [mailto:[EMAIL PROTECTED]
Sent: Friday, August 10, 2007 6:00 PM
To: axis-user@ws.apache.org; Geoff Peart
Subject: RE: Improved Error Response for Bad Requests on ADB
This is a known bug in Axis2 1.2 but seems to be resolved in 1.3
Re: Simple question about MTOM, Rampart and optimize parts
Hi Dimuthu, WSCOMMONS-238 opened. Please could you clarify a pair of things? Expected behaviour of Rampart is to add or MTOM elements as MIME parts isn't it? what exactly does Optimize parts? How does it optimize elements? does it reduze its size? Is it applicable for any element, not only MTOM? Thanks, Jorge Fernández Dimuthu [EMAIL PROTECTED] escribió: Hi, Please look at my comments in line. On Mon, 2007-08-27 at 17:49 +0200, Jorge Fernandez wrote: Hi all, I would like to know how does Rampart work with MTOM. I see that when using Rampart, MTOM elements are included as strings in the SOAP message instead of sending them outside the message as MIME parts, even if I don't do any operation with them (not signature, nor encryption), but these MIME parts appear empty in the HTTP message. Why is that? mmm .. looks like this is a bug in Axiom. We are looking at it. Please report a bug. Does optimize parts something about that? I don't understand much about this parameter. Using this parameter, people can manually specify which element needs to be optimized. For example if you want to optimize CipherValue in EncryptedData then you can specify using this parameter. It is effective if you have specified assertion in your policy. Syntax for the element is as follows[1]. So actually this is a workaround for the above problem. Hope this will help. Cheers, Dimuthu [1] //ns1:data1 //ns2:data2 If anybody could give me a hint about this, that would be great. Thanks, Jorge Fernández - Sé un Mejor Amante del Cine ¿Quieres saber cómo? ¡Deja que otras personas te ayuden!. -- http://wso2.org - Sé un Mejor Amante del Cine ¿Quieres saber cómo? ¡Deja que otras personas te ayuden!.
RE: Invalin null character error
Hi Dennis, I got this error when I tried to return a Java char type from my service. I was recovering it from a database and when it hadn't got any value there, the char I got was a non printable ASCII character and when I tried to serialize it to the soap message I think I got the same exception. So maybe there are problems with non printable characters but it's only my guess. Hope this helps. Regards, Jorge Fernández Dennis Schaaf [EMAIL PROTECTED] escribió: Hey, I am using ruby's soap4r library to connect to my axis2 application. I tried sending across some of my own classes, hoping that they'd be serialized properly and then rebuilt on the ruby end. But that does not happen. When I return such a class I get this error, which doesn't seem to have anything to do with what I might be doing wrong. Does anyone have any idea what might be causing this? What more information might be usefull, wsdl files? thanks for your help dennis the trace from the axis2 server org.apache.axis2.AxisFault: Invalid null character in text to output at org.apache.axis2.AxisFault.makeFault(AxisFault.java:417) at org.apache.axis2.transport.http.SOAPMessageFormatter.writeTo(SOAPMessageFormatter.java:72) at org.apache.axis2.transport.http.CommonsHTTPTransportSender.sendUsingOutputStream(CommonsHTTPTransportSender.java:294) at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:211) at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:396) at org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:43) at org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:96) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:145) at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:275) at org.apache.axis2.transport.http.HTTPWorker.service(HTTPWorker.java:256) at org.apache.axis2.transport.http.server.AxisHttpService.doService(AxisHttpService.java:259) at org.apache.axis2.transport.http.server.AxisHttpService.handleRequest(AxisHttpService.java:166) at org.apache.axis2.transport.http.server.HttpServiceProcessor.run(HttpServiceProcessor.java:85) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690) at java.lang.Thread.run(Thread.java:619) Caused by: com.ctc.wstx.exc.WstxIOException: Invalid null character in text to output at com.ctc.wstx.sw.BaseStreamWriter.writeCharacters(BaseStreamWriter.java:520) at org.apache.axiom.om.impl.MTOMXMLStreamWriter.writeCharacters(MTOMXMLStreamWriter.java:196) at org.apache.axiom.om.impl.llom.OMTextImpl.writeOutput(OMTextImpl.java:212) at org.apache.axiom.om.impl.llom.OMTextImpl.internalSerializeLocal(OMTextImpl.java:371) at org.apache.axiom.om.impl.llom.OMTextImpl.internalSerializeAndConsume(OMTextImpl.java:365) at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:785) at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerializeAndConsume(OMElementImpl.java:814) at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:785) at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerializeAndConsume(OMElementImpl.java:814) at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:785) at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerializeAndConsume(OMElementImpl.java:814) at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:785) at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerializeAndConsume(OMElementImpl.java:814) at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:785) at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerializeAndConsume(OMElementImpl.java:814) at org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.serializeInternally(SOAPEnvelopeImpl.java:237) at org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.internalSerialize(SOAPEnvelopeImpl.java:225) at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerializeAndConsume(OMElementImpl.java:814) at org.apache.axiom.om.impl.llom.OMNodeImpl.serializeAndConsume(OMNodeImpl.java:421) at org.apache.axis2.transport.http.SOAPMessageFormatter.writeTo(SOAPMessageFormatter.java:68) ... 14 more Caused by: java.io.IOException: Invalid null character in text to output at
Timeout
Hi all, I'm usign axis2 1.3 and I could see that one of the changes made was about timeout. Now, while debugging my service, I get timeouts because axis2 removes contexts but I was managing this timeouts myself so I would like to deactivate axis2 timeouts. Is this possible? I thought that maybe I could do it by setting timeout to 0 but it doesn't work. Thanks, Jorge Fernández - Sé un Mejor Amante del Cine ¿Quieres saber cómo? ¡Deja que otras personas te ayuden!.
Simple question about MTOM, Rampart and optimize parts
Hi all, I would like to know how does Rampart work with MTOM. I see that when using Rampart, MTOM elements are included as strings in the SOAP message instead of sending them outside the message as MIME parts, even if I don't do any operation with them (not signature, nor encryption), but these MIME parts appear empty in the HTTP message. Why is that? Does optimize parts something about that? I don't understand much about this parameter. If anybody could give me a hint about this, that would be great. Thanks, Jorge Fernández - Sé un Mejor Amante del Cine ¿Quieres saber cómo? ¡Deja que otras personas te ayuden!.
Re: Is there a rampart 1.3 version available for download?
Does it?? I tried but Axis2 1.3 doesn't detect it. It throws an exception Thanks, Jorge Fernández Ayhan Molla [EMAIL PROTECTED] escribió: rampart-1.2.zip works for 1.3 too Ihsan Demir [EMAIL PROTECTED] wrote: Hello, None of the links at the web site http://www.apache.org/dyn/mirrors/mirrors.cgi/ws/rampart/1_3/rampart-1.3.zip works for downloading the release. Do you know if there is a working link? If so, what is it? ihsan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Yahoo! oneSearch: Finally, mobile search that gives answers, not web links. - ¡Descubre una nueva forma de obtener respuestas a tus preguntas! Entra en Yahoo! Respuestas.
Cannot find Reference in Manifest
Hi all, I'm getting the exception below. Can anybody tell me what does this mean??? The only operation I was doing was timestamp signing but when I removed timestamp, I got this exception: org.apache.axis2.AxisFault: org.w3c.dom.DOMException: Cannot find Reference in Manifest at org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:486) at org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:343) at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:389) at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:211) at org.apache.axis2.client.OperationClient.execute(OperationClient.java:163) at client.Medici_LinkStub.validate(Medici_LinkStub.java:3228) at client.ClientUtilities.validateTest(ClientUtilities.java:57) at client.Client.main(Client.java:64) - Sé un Mejor Amante del Cine ¿Quieres saber cómo? ¡Deja que otras personas te ayuden!.
Re: can't store information in configuration context
Hi Deepal, My problem was on server side. Each time a client opened a session, properties were cleaned and the only information I could see was the one I stored in startUp. At this moment is working ok. Don't know why yesterday it didn't work because I haven't changed anything. If instead of storing that information in configurationContext, I do it in serviceContext or serviceGroupContext, do all the clients of the service have access to the same serviceContext (or serviceGroupContext) ? I though it was like this but I didn't get the results I expected. Thanks, Jorge Fernández Deepal jayasinghe [EMAIL PROTECTED] escribió: Jorge Fernandez wrote: Hi all, I'm trying to store some information in properties element in configuration context so I can access it from any service instance but each time a client opens a session, this information dissapears. Well its depend on the way you create the ServiceClient , if you create a ServiceClient with its default constructor then for each invocation new ConfigurationContext (CC) will be created. If you want to share the same CC then you have to create ServiceClient with one CC. Why is this happening? Is Configuration Context restored every time a client opens a session? In the Server side the answer is no , it uses only one CC throughout the lifetime of the system. In startUp method, I'm doing this: confContext.setProperty(serviceLogger,serviceLogger); confContext.setProperty(validatedSystems,new HashMap()); confContext.setProperty(validatedUsers,new HashMap()); ((HashMap)confContext.getProperty(validatedSystems)).put(hola, adios); So when a user validates I store an entry for him in validatedUsers and another entry in validatedSystem for the corresponding system but when a new client logins, those entries are cleaned, validatedUsers is empty and validatedSystems has the element I stored in startUp method as a test. Please, can anybody help me with this? Thanks, Jorge Fernández Thanks Deepal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Sé un Mejor Viajero ¿Quieres saber cómo? ¡Deja que otras personas te ayuden! .
can't store information in configuration context
Hi all, I'm trying to store some information in properties element in configuration context so I can access it from any service instance but each time a client opens a session, this information dissapears. Why is this happening? Is Configuration Context restored every time a client opens a session? In startUp method, I'm doing this: confContext.setProperty(serviceLogger,serviceLogger); confContext.setProperty(validatedSystems,new HashMap()); confContext.setProperty(validatedUsers,new HashMap()); ((HashMap)confContext.getProperty(validatedSystems)).put(hola, adios); So when a user validates I store an entry for him in validatedUsers and another entry in validatedSystem for the corresponding system but when a new client logins, those entries are cleaned, validatedUsers is empty and validatedSystems has the element I stored in startUp method as a test. Please, can anybody help me with this? Thanks, Jorge Fernández - Sé un Mejor Amante del Cine ¿Quieres saber cómo? ¡Deja que otras personas te ayuden!.
RE: serviceGroupContext problems
Hi, Any hint on this? Thanks, Jorge Fernández Jorge Fernandez [EMAIL PROTECTED] escribió: Hi again, Debugging my Web service with eclipse I'm having two clients and from the two of them I can see that configurationContext has only one entry in serviceGroupContextMap with the ID of the last connected client. I also would like to ask where should I store variables that should be visible from all the clients of one service because I observed that serviceGroupContext is particular for each client and I think that configurationContext was shared by all services. Thanks a lot, Jorge Fernández - Sé un Mejor Amante del Cine ¿Quieres saber cómo? ¡Deja que otras personas te ayuden! . - Sé un Mejor Amante del Cine ¿Quieres saber cómo? ¡Deja que otras personas te ayuden!.
RE: [ANN][Axis2]Axis2 1.3 Released
Hi, About new phase called addressing, is it possible to change the order in axis2.xml or is it mandatory to keep that order?? I'm asking this because in Inflow, Addressing appears before security and when I encrypt WS-Addressing headers I receive an exception from the service: org.apache.axis2.AxisFault: The org.apache.axis2.AxisFault: A required header representing a Message Addressing Property is not present I tried changind the order and I stopped having this exception (I have another related with rampart) but I don't know if this will cause any other problems. Also another question related with phases: Why security phase is not added to outFaultFlow??I wanted to encrypt faults and I tried adding it by hand but I saw no difference, the message is not encrypted Thanks, Jorge Fernández Deepal jayasinghe [EMAIL PROTECTED] escribió: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Just over 4 months since the original 1.2 release, we are very proud to announce the release of Apache Axis2 version 1.3. Downloads are available at: http://ws.apache.org/axis2/download.cgi Apache Axis2 is a complete re-design and re-write of the widely used Apache Axis engine and is a more efficient, more scalable, more modular and more XML-oriented Web services framework. It is carefully designed to support the easy addition of plug-in modules that extend its functionality for features such as security and reliability. Modules supporting WS-Security/Secure-Conversation (Apache Rampart), WS-Trust (Apache Rahas), WS-Reliable Messaging (Apache Sandesha) and WS-Eventing (Apache Savan) will be available soon after the Apache Axis2 1.3 release. Please see these projects' own sites for further information. Major Changes Since 1.2: - - Moved to maven2 from maven1 - - Significantly improved documentation - - Significantly improved support for POJO services and clients - - Significantly improved Deployment module and custom deployers - - Significantly improved support for Spring services - - Significantly improved Axis Data Binding (ADB) to increase schema coverage and overall stability - - Improved handler and module interfaces - - Improved Eclipse and Idea plugins - - Fixed tons of small and not-so-small bugs - - Major code cleanup and improved exception handling - - All the asynchronous MessageReceivers have been deprecated - - Deprecating the introspection to find init()/destroy() methods on service classes. - - Deprecated the Callback interface [http://wiki.apache.org/ws/FrontPage/Axis2/changesfrom1.2to1.3] - - Added a new phase called Addressing and moved all the addressing handlers into that phase - - Name of the wsdl2java generated Exception classes changed. Earlier it had the Exception suffix and from Axis2 1.3 it has been removed - - Interface changed in ADB Datasource class - - Classpath module loading support Known Issues and Limitations in 1.3 Release: - Java2WSDL and runtime WSDL generation only support doc-lit/bare and doc-lit/wrapped - Custom deployers only work in file system based repository. - POJO does not support HasMap , Hastable and Vectors. Apache Axis2 1.3 is a major new release compared to Axis2 1.2. We are striving for a simple and happy first time user experience as well as a satisfying experienced user experience with this release. We welcome any and all feedback at: axis-user@ws.apache.org (please include [axis2] in the subject) [EMAIL PROTECTED] (please include [axis2] in the subject) http://issues.apache.org/jira/browse/AXIS2 Thank you for your interest in Apache Axis2! The Axis2 Development Team http://ws.apache.org/axis2/ - Features of Apache Axis2: Programming Model - Simple XML-centric client API with full WSDL and policy support - Support for easy deployemnt of POJO with or without annotation - Support for Spring services and clients - Support for any message exchange pattern (MEP) - Synchronous and asynchronous programming model (both in client side and server side) - Archived based service deployment model supporting full service encapsulation - Directory based service deployment support - Archived module deployment model supporting controlled extensibility with versioning support - Hot deployment and Hot update suport for services - WS-Policy driven code generation extensions - Flexible service life cycle model and session managment - Automatic support for POX (REST) style invocation of services - Support for querying service's WSDL (with ?wsdl), schema (with ?xsd) and policies (with ?policy) - Java2WSDL support for both doclit/bare and doclit/wrapped - Support for custom deployers - Classpath module loading support Supported Specifications - SOAP 1.1 and 1.2 - Message Transmission Optimization Mechanism (MTOM) - XML Optimized Packaging (XOP) - SOAP with Attachments - WSDL 1.1 and
RE: [ANN][Axis2]Axis2 1.3 Released
Hi, I wanted to download eclipse code generator plugin and the links were broken. Links are kind of this: ./ws/axis2/tools/1_3/axis2-eclipse-codegen-wizard-1.3.zip but the real path is: .../ws/axis2/tools/1_3/axis2-eclipse-codegen-wizard.zip Thanks, Jorge Fernández Deepal jayasinghe [EMAIL PROTECTED] escribió: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Just over 4 months since the original 1.2 release, we are very proud to announce the release of Apache Axis2 version 1.3. Downloads are available at: http://ws.apache.org/axis2/download.cgi Apache Axis2 is a complete re-design and re-write of the widely used Apache Axis engine and is a more efficient, more scalable, more modular and more XML-oriented Web services framework. It is carefully designed to support the easy addition of plug-in modules that extend its functionality for features such as security and reliability. Modules supporting WS-Security/Secure-Conversation (Apache Rampart), WS-Trust (Apache Rahas), WS-Reliable Messaging (Apache Sandesha) and WS-Eventing (Apache Savan) will be available soon after the Apache Axis2 1.3 release. Please see these projects' own sites for further information. Major Changes Since 1.2: - - Moved to maven2 from maven1 - - Significantly improved documentation - - Significantly improved support for POJO services and clients - - Significantly improved Deployment module and custom deployers - - Significantly improved support for Spring services - - Significantly improved Axis Data Binding (ADB) to increase schema coverage and overall stability - - Improved handler and module interfaces - - Improved Eclipse and Idea plugins - - Fixed tons of small and not-so-small bugs - - Major code cleanup and improved exception handling - - All the asynchronous MessageReceivers have been deprecated - - Deprecating the introspection to find init()/destroy() methods on service classes. - - Deprecated the Callback interface [http://wiki.apache.org/ws/FrontPage/Axis2/changesfrom1.2to1.3] - - Added a new phase called Addressing and moved all the addressing handlers into that phase - - Name of the wsdl2java generated Exception classes changed. Earlier it had the Exception suffix and from Axis2 1.3 it has been removed - - Interface changed in ADB Datasource class - - Classpath module loading support Known Issues and Limitations in 1.3 Release: - Java2WSDL and runtime WSDL generation only support doc-lit/bare and doc-lit/wrapped - Custom deployers only work in file system based repository. - POJO does not support HasMap , Hastable and Vectors. Apache Axis2 1.3 is a major new release compared to Axis2 1.2. We are striving for a simple and happy first time user experience as well as a satisfying experienced user experience with this release. We welcome any and all feedback at: axis-user@ws.apache.org (please include [axis2] in the subject) [EMAIL PROTECTED] (please include [axis2] in the subject) http://issues.apache.org/jira/browse/AXIS2 Thank you for your interest in Apache Axis2! The Axis2 Development Team http://ws.apache.org/axis2/ - Features of Apache Axis2: Programming Model - Simple XML-centric client API with full WSDL and policy support - Support for easy deployemnt of POJO with or without annotation - Support for Spring services and clients - Support for any message exchange pattern (MEP) - Synchronous and asynchronous programming model (both in client side and server side) - Archived based service deployment model supporting full service encapsulation - Directory based service deployment support - Archived module deployment model supporting controlled extensibility with versioning support - Hot deployment and Hot update suport for services - WS-Policy driven code generation extensions - Flexible service life cycle model and session managment - Automatic support for POX (REST) style invocation of services - Support for querying service's WSDL (with ?wsdl), schema (with ?xsd) and policies (with ?policy) - Java2WSDL support for both doclit/bare and doclit/wrapped - Support for custom deployers - Classpath module loading support Supported Specifications - SOAP 1.1 and 1.2 - Message Transmission Optimization Mechanism (MTOM) - XML Optimized Packaging (XOP) - SOAP with Attachments - WSDL 1.1 and WSDL 2.0, including both SOAP and HTTP bindings - WS-Addressing submission and 1.0 - WS-Policy - SAAJ 1.1 Transports - HTTP/HTTPS - SMTP - JMS - TCP Supported Data Bindings - Axis Data Binding (ADB) - XMLBeans - JibX - JaxMe (Experimental) - JaxBRI (Experimental) Tools - WSDL2Java: Generate Java stubs and skeletons from a WSDL document. - Java2WSDL: Generate a WSDL document from a Java class. - Eclipse Plugins - IntelliJ Idea Plugins - Maven2 Plugins - Web application for
RE: exceptions on init
Hi again, I saw that DependencyManager.initServiceClass is the method that calls init and all it does with exception is logging them. Is there any way for me to destroy the session when an exception was thrown?? Thanks, Jorge Fernández Jorge Fernandez [EMAIL PROTECTED] escribió: Hi, Can anybody tell me how can I stop service invocation when I get an exception in init method? Thanks, Jorge Fernández - Sé un Mejor Amante del Cine ¿Quieres saber cómo? ¡Deja que otras personas te ayuden! . - Sé un Mejor Amante del Cine ¿Quieres saber cómo? ¡Deja que otras personas te ayuden!.
null values in attributes (hierarchies with ADB)
Hi, I'm observing that when I have an object with array attributes, ADB behaves different depending on whether that attribute is inherited or not. If I have an inherited array, and I don't call its set method, that element won't appear in the SOAP message. The client will see that the array is null. If in the same case, I set it to null, the element will appear as nil in the SOAP message. The client sees an array of one null component. With a non-inherited array, the element will appear as nil if I set it to null and if I don't call the method too. The client sees an array of one null component. If I have an attribute that is not an array (ex: a String). Its behaviour is the same if it's inherited or not. The element will appear as nil. My question are: Why does it work different for an inherited array?? Why my client sees the array with one null component when the array comes as nil?? Shouldn't him see it as a null array?? Why when an attribute is null it appears as nil in the soap message?? Shouldn't it be better that the attribute wouldn't appear in the message? Thanks, Jorge Fernández - Sé un Mejor Amante del Cine ¿Quieres saber cómo? ¡Deja que otras personas te ayuden!.
Re: exceptions on init
JIRA 3120 created. Thanks, Jorge Fernández Deepal jayasinghe [EMAIL PROTECTED] escribió: hi Jorge , Unfortunately no way to do that. Please create a JIRA so that we can fix that for 1.4 release. Thanks Deepal Hi again, I saw that DependencyManager.initServiceClass is the method that calls init and all it does with exception is logging them. Is there any way for me to destroy the session when an exception was thrown?? Thanks, Jorge Fernández */Jorge Fernandez /* escribió: Hi, Can anybody tell me how can I stop service invocation when I get an exception in init method? Thanks, Jorge Fernández Sé un Mejor Amante del Cine ¿Quieres saber cómo? ¡Deja que otras personas te ayuden! . Sé un Mejor Amante del Cine ¿Quieres saber cómo? ¡Deja que otras personas te ayuden! . - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Sé un Mejor Viajero ¿Quieres saber cómo? ¡Deja que otras personas te ayuden! .
RE: null values in attributes (hierarchies with ADB)
Hola Martin, See you're back. I meant setting the whole array to null. When setting one of the elements, there's no problem. For example, If I have a class disc and a class discography that has an array of discs as attribute, I can perfectly set any of the components to null. Also if I set the array to null doing setDiscs(null), there is no problem. The element is generated in the message. If I don't call setDiscs(), the element will be generated anyway. But if I create a class Elvis that extends discography and I don't call setDiscs(), the element won't be generated in the message. If instead I call setDiscs(null), the element will be generated. It works anyway but the behaviour is different. If element is generated, the client will interpret that discs has one component that is null discs[0]=null. If element is not generated, the client will interpret that discs=null. I thought that the correct behaviour should be the second: as the whole array is null, it won't generate any element in the message for that and the client will interpret that the array is null. Or in the second case, in spite of generating the element in the message, the client should interpret that the array is null Thanks, Jorge Fernández Martin Gainty [EMAIL PROTECTED] escribió: Jorge Looking for specifics on what you mean by setting it do you mean setting the array to null or one of the elements in the array? NULL is a representation of an uninitialised object the treatment of this uninitialised object is language dependent that said an Array of NULL objects is an allocated array object of uninitialised empty objects so..a java.lang.Arrays is an *allocated object*( which is represented by the Javadoc available here http://java.sun.com/j2se/1.5.0/docs/api/ To add more even more confusion Arrays of primitive types (ints/chars) are different than arrays of Objects which are pre-allocated entities http://java.sun.com/docs/books/jni/html/objtypes.html An Array of primitive types allocation is dependent on the number of elements BUT any array of pre-defined size is allocated http://java.sun.com/docs/books/jni/html/objtypes.html In JavaScript world the treatment of Arrays is even dependent on the browser JavaScript version e.g. Mozilla JavaScript1.2 converts an Array object to its length. Mozilla JavaScript1.1, JavaScript1.3-JavaScript1.5 converts an empty Array to 0 HTH/ Martin Gainty __ Disclaimer and confidentiality note Everything in this e-mail and any attachments relates to the official business of Sender. This transmission is of a confidential nature and Sender does not endorse distribution to any party other than intended recipient. Sender does not necessarily endorse content contained within this transmission. (mobile) 001-603-438-5053 From: Jorge Fernandez Reply-To: [EMAIL PROTECTED] To: axis-user Subject: null values in attributes (hierarchies with ADB) Date: Mon, 13 Aug 2007 15:40:56 +0200 (CEST) MIME-Version: 1.0 Received: from mail.apache.org ([140.211.11.2]) by bay0-mc3-f7.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.2668); Mon, 13 Aug 2007 06:41:37 -0700 Received: (qmail 48452 invoked by uid 500); 13 Aug 2007 13:41:28 - Received: (qmail 48441 invoked by uid 99); 13 Aug 2007 13:41:28 - Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 13 Aug 2007 06:41:28 -0700 Received: pass (nike.apache.org: local policy includes SPF record at spf.trusted-forwarder.org) Received: from [217.12.10.88] (HELO web26014.mail.ukl.yahoo.com) (217.12.10.88)by apache.org (qpsmtpd/0.29) with SMTP; Mon, 13 Aug 2007 13:41:29 + Received: (qmail 60995 invoked by uid 60001); 13 Aug 2007 13:40:56 - Received: from [84.78.70.217] by web26014.mail.ukl.yahoo.com via HTTP; Mon, 13 Aug 2007 15:40:56 CEST X-Message-Delivery: Vj0zLjQuMDt1cz0wO2k9MDtsPTA7YT0w X-Message-Info: JGTYoYF78jFqB8E5WzR+LBEQqsj3ei+0NzvpxfbZZbvfB0Vjt9AshFgkMxyC89WmXeUfrIBu53/rR/Zl+gqTSQ== Mailing-List: contact [EMAIL PROTECTED]; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list axis-user@ws.apache.org X-ASF-Spam-Status: No, hits=2.0 required=10.0tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.es; h=X-YMail-OSG:Received:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=lnJ74kNrTOROD2njDRpji0jNo8OZWrU5oCV3tSKXUZrfal8CQXF5N+gzoV1nyau8D5f9B0mnDBhDzATJdaAcYEYA9CfZVpwW98NSRVgQygXyctAO1r5iSsmGEyPR5TLY5mrVmDER4TXXKFwkYbjPfkY2xdHrNIDlilnj9LUIggE=; X-YMail-OSG: vQKm5F4VM1knWHtvn4kWcv8_Dn.NmjPxLEPTi601c2yv_cDT5.jefOVFTR38konOQg-- X-Virus-Checked: Checked by ClamAV on apache.org Return-Path: [EMAIL PROTECTED] X-OriginalArrivalTime: 13 Aug 2007 13:41:37.0072 (UTC) FILETIME=[AB903B00:01C7DDAF] Hi, I'm observing that when I
RE: Improved Error Response for Bad Requests on ADB
This is a known bug in Axis2 1.2 but seems to be resolved in 1.3. Regards, Jorge Fernández Geoff Peart [EMAIL PROTECTED] escribió: Using the default Data Binding, a badly formed request gets meaningless runtime exceptions making it difficult for a client to develop and debug their application. Is there a way to either override this behaviour, or plug-in better error handling? I don't want to get in and edit the generated code, but even if the runtime errors held more information like why its failing would be a step in the right direction? Any help would be great. Thanks G - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Sé un Mejor Amante del Cine ¿Quieres saber cómo? ¡Deja que otras personas te ayuden!.
getInboundFaultFromMessageContext in last RC
Hi all, I'm getting this exception in last RC when returning the exception below. What is the cause of that? I've tried with other exceptions and I had no problem. Thanks, Jorge Fernández org.apache.axis2.AxisFault: unknown at org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:486) at org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:343) at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:389) at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:211) at org.apache.axis2.client.OperationClient.execute(OperationClient.java:163) at client.Medici_LinkStub.logout(Medici_LinkStub.java:1016) at client.ClientUtilities.logoutTest(ClientUtilities.java:75) at client.Client.main(Client.java:72) HTTP/1.1 500 Error Interno del Servidor Server: Apache-Coyote/1.1 Content-Type: application/soap+xml; action=http://service.medici_link/Medici_LinkPortType/logout/Fault/DataAccessFault;charset=UTF-8 Transfer-Encoding: chunked Date: Thu, 09 Aug 2007 07:48:24 GMT Connection: close c28 ?xml version='1.0' encoding='UTF-8'? soapenv:Envelope xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope; xmlns:wsa=http://www.w3.org/2005/08/addressing; soapenv:Header wsa:Actionhttp://service.medici_link/Medici_LinkPortType/logout/Fault/DataAccessFault/wsa:Action wsa:RelatesTourn:uuid:4A7FC3D07CE6A724F41186645704829/wsa:RelatesTo /soapenv:Header soapenv:Body soapenv:Fault soapenv:Code soapenv:Valuesoapenv:Receiver/soapenv:Value /soapenv:Code soapenv:Reason soapenv:Text xml:lang=en-USunknown/soapenv:Text /soapenv:Reason soapenv:Detail Exceptionorg.apache.axis2.AxisFault#xd;at org.apache.axis2.AxisFault.makeFault(AxisFault.java:417)#xd;at tests.medici_link.service.Medici_LinkMessageReceiverInOutTest.invokeBusinessLogic(Medici_LinkMessageReceiverInOutTest.java:416)#xd; at org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.invokeBusinessLogic(AbstractInOutSyncMessageReceiver.java:42)#xd; at org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:96)#xd; at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:145)#xd; at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:275)#xd; at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:120)#xd; at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)#xd;at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)#xd;at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)#xd; at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)#xd; at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)#xd; at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)#xd; at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)#xd; at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)#xd; at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)#xd; at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:261)#xd; at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)#xd; at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:581)#xd; at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)#xd; at java.lang.Thread.run(Unknown Source)#xd;Caused by: java.lang.NullPointerException#xd;at java.lang.String.lt;init(Unknown Source)#xd;at ModeloDatos.ModeloDatosComunicacion.User.lt;init(User.java:39)#xd;at ModeloDatos.ModeloDatosComunicacion.ClinicalUser.lt;init(ClinicalUser.java:13)#xd; at tests.medici_link.service.Medici_LinkSkeletonTest.logout(Medici_LinkSkeletonTest.java:203)#xd; at tests.medici_link.service.Medici_LinkMessageReceiverInOutTest.invokeBusinessLogic(Medici_LinkMessageReceiverInOutTest.java:89)#xd; ... 19 more#xd;/Exception /soapenv:Detail /soapenv:Fault /soapenv:Body /soapenv:Envelope 0 - Sé un Mejor Amante del Cine ¿Quieres saber cómo? ¡Deja que otras personas te ayuden!.
destroy
Hi, I'm using SOAP sessions and I'm testing my Web service opening and closing sessions and I can see sometimes in the logs that the session is being closed more than once. Sometimes, this happens with more than one minute of difference. And when I shutdown Tomcat, all sessions are closed again. I have a method called logout that invokes destroy for cleaning axis2 session when the clients wants to close the session manually. How does Axis2 manage sessions? What may be happening here? Thanks, Jorge Fernández - Sé un Mejor Amante del Cine ¿Quieres saber cómo? ¡Deja que otras personas te ayuden!.
serviceGroupContext problems
Hi again, Debugging my Web service with eclipse I'm having two clients stopped and from the two of them I can see that configurationContext has in serviceGroupContextMap one only entry with the ID of the last connected client. I also would like to ask where should I store variables that should be visible from all my clients but only for this service because I see that serviceGroupContext is particular for each client and I thought that configurationContext was shared by all services. Thanks a lot, Jorge Fernández - Sé un Mejor Amante del Cine ¿Quieres saber cómo? ¡Deja que otras personas te ayuden!.
Rampart SNAPSHOT problems
Hi all, Im having some problems with last rampart snapshot. First, I'm using basic configuration on client as with 1.2 and policy on server side. Rampart is engaged in both. In server is engaged in service scope and in client at global scope. I receive an exception from service that makes me thing about a problem in phases order: org.apache.axis2.AxisFault: The org.apache.axis2.AxisFault: A required header representing a Message Addressing Property is not present at org.apache.axis2.addressing.AddressingFaultsHelper.triggerAddressingFault(AddressingFaultsHelper.java:355) at org.apache.axis2.addressing.AddressingFaultsHelper.triggerMessageAddressingRequiredFault(AddressingFaultsHelper.java:281) at org.apache.axis2.handlers.addressing.AddressingValidationHandler.checkMessageIDHeader(AddressingValidationHandler.java:168) at org.apache.axis2.handlers.addressing.AddressingValidationHandler.invoke(AddressingValidationHandler.java:56) at org.apache.axis2.engine.Phase.invoke(Phase.java:292) at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:212) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:132) at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:275) at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:120) at javax.servlet.http.HttpServlet.service(HttpServlet.java:710) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:261) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:581) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Unknown Source) header is required when WS-Addressing is in use but was not sent. at org.apache.axis2.handlers.addressing.AddressingInFaultHandler.invoke(AddressingInFaultHandler.java:114) at org.apache.axis2.engine.Phase.invoke(Phase.java:292) at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:212) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:132) at org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:336) at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:389) at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:211) at org.apache.axis2.client.OperationClient.execute(OperationClient.java:163) at client.Medici_LinkStub.validate(Medici_LinkStub.java:744) at client.ClientUtilities.validateTest(ClientUtilities.java:61) at client.Client.main(Client.java:34) Second, I removed configuration from client but keeping rampart engaged and I receive this exception from the service: org.apache.axis2.AxisFault: java.lang.NullPointerException at org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:486) at org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:343) at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:389) at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:211) at org.apache.axis2.client.OperationClient.execute(OperationClient.java:163) at client.Medici_LinkStub.validate(Medici_LinkStub.java:744) at client.ClientUtilities.validateTest(ClientUtilities.java:61) at client.Client.main(Client.java:34) Third, I remove module ref=rampart/ from services.xml and the first operation works ok but for the nexts I see an exception ocurred in the client: org.apache.axis2.AxisFault: Error in extracting message properties at org.apache.rampart.handler.RampartSender.invoke(RampartSender.java:68) at org.apache.axis2.engine.Phase.invoke(Phase.java:292) at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:212) at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:377) at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:374) at
Concurrent access to service group context
Hi all, Does Axis2 manage conflicts in concurrent access to service group context and other contexts? Thanks, Jorge Fernández - Sé un Mejor Amante del Cine ¿Quieres saber cómo? ¡Deja que otras personas te ayuden!.
RE: [Axis2] How to propagate exception for In-only operations
Hi Gul, You can't do that with in-only. You have to use robust-in-only MEP. http://www.w3.org/TR/2004/WD-wsdl20-extensions-20040803/ Regards, Jorge Fernández Gul Onural [EMAIL PROTECTED] escribió: [Axis2] How to propagate exception for In-only operations Hi, I am using RawXMLINOnlyMessageReceiver for my in-only operations. I tried the following signatures in my in-only methods, but my client doesn't seem to get any exception. How do I get my client receive exception for in-only methods ? Do I need to set a configuration parameter somewhere ? public void myMethod(OMElement inputMsg) throws RemoteException; OR public void myMethod(OMElement inputMsg) throws AxisFault; OR public void myMethod(OMElement inputMsg); - Sé un Mejor Amante del Cine ¿Quieres saber cómo? ¡Deja que otras personas te ayuden!.
exceptions on init
Hi, Can anybody tell me how can I stop service invocation when I get an exception in init method? Thanks, Jorge Fernández - Sé un Mejor Amante del Cine ¿Quieres saber cómo? ¡Deja que otras personas te ayuden!.
Re: [Axis2] Zero Blockers for 1.3
Hi Dims, Axis2 3076 created. Today I tried it again and it works different. It doesn'f finish when generating the client if I do it without -u option. Yesterday it didn't work when generating both client and server at a time. I have all my schemas defined in the wsdl. I noticed one change: In version 1.2, exceptions names were built from their message name, adding Exception and now they are only formed with message name. Is this right?? Now it generates Stub only for SOAP 1.2, doesn't it? Also, it is still generating faultExceptionNameMap.put() faultExceptionClassNameMap.put() faultMessageMap.put() for each operation that throws the exception, instead of generating one for each exception, in the client populateFaults() method. There is a JIRA already opened for that:Axis2 2326. Thanks, Jorge Fernández Davanum Srinivas [EMAIL PROTECTED] escribió: oops! hit send too fast...recrusion problem with wsdl imports or schema includes. -- dims On 8/5/07, Davanum Srinivas wrote: Please log a bug in JIRA with your stripped down test. could be a recursion problem. thanks, dims On 8/5/07, Jorge Fernandez wrote: Hi Dims, I'm getting one problem with RC3. I'm trying to generate my code for doing my testing but, wsdl2java doesn't return control back and it uses a big amount of resources. It seems that is generating the code or some of them but it never finishes. Regards, Jorge Fernández Davanum Srinivas escribió: Folks, At this moment there are zero blockers in JIRA for 1.3. Please try RC3 released friday (http://people.apache.org/~deepal/axis2/1.3-RC3/) or 1.3 branch's nightly build from here - http://people.apache.org/dist/axis2/nightly/ *Please* make sure you try it out as this is the last chance before we cut 1.3 Final early next week. thanks, dims -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Sé un Mejor Amante del Cine ¿Quieres saber cómo? ¡Deja que otras personas te ayuden! . -- Davanum Srinivas :: http://davanum.wordpress.com -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Sé un Mejor Amante del Cine ¿Quieres saber cómo? ¡Deja que otras personas te ayuden!.
Re: [Axis2] Zero Blockers for 1.3
- Sé un Mejor Amante del Cine ¿Quieres saber cómo? ¡Deja que otras personas te ayuden!. ---BeginMessage--- Yes, now it's much faster :). Do I need the library during runtime or compilation?? What about names of exceptions and redundant code I mentioned?? Other problems I'm getting now: Whenever I modify axis2.xml of the war distribution, I get an error page from listServices and in Hapiness Page I see: Examinin Version Service: There was a problem in Axis2 version service , may be the service not available or some thing has gone wrong. But this does not mean system is not working ! Try to upload some other service and check to see whether it is working. Even If I undo changes I continue getting that problem. The changes I do in axis2.xml are the port and sendStackTraceWithFault. When that happens I receive this at the client the message in the attached file Also I can see that each time I run tomcat, my services.xml is updated, apparently with no changes but is modified on disk and the same happens with axis2.xml Thanks, Jorge Fernández Davanum Srinivas [EMAIL PROTECTED] escribió: Try removing the jalopy jar. I think it is generating a huge file which jalopy has trouble reformatting. thanks, dims On 8/6/07, Jorge Fernandez wrote: Hi Dims Axis2 3076 created. Today I tried it again and it works different. It doesn'f finish when generating the client if I do it without -u option. Yesterday it didn't work when generating both client and server at a time. I have all my schemas defined in the wsdl. I noticed one change: In version 1.2, exceptions names were built from their message name, adding Exception and now they are only formed with message name. Is this right?? Now it generates Stub only for SOAP 1.2, doesn't it? Also, it is still generating faultExceptionNameMap.put() faultExceptionClassNameMap.put() faultMessageMap.put() for each operation that throws the exception, instead of generating one for each exception, in the client populateFaults() method. There is a JIRA already opened for that:Axis2 2326. Thanks, Jorge Fernández Davanum Srinivas escribió: oops! hit send too fast...recrusion problem with wsdl imports or schema includes. -- dims On 8/5/07, Davanum Srinivas wrote: Please log a bug in JIRA with your stripped down test. could be a recursion problem. thanks, dims On 8/5/07, Jorge Fernandez wrote: Hi Dims, I'm getting one problem with RC3. I'm trying to generate my code for doing my testing but, wsdl2java doesn't return control back and it uses a big amount of resources. It seems that is generating the code or some of them but it never finishes. Regards, Jorge Fernández Davanum Srinivas escribió: Folks, At this moment there are zero blockers in JIRA for 1.3. Please try RC3 released friday (http://people.apache.org/~deepal/axis2/1.3-RC3/) or 1.3 branch's nightly build from here - http://people.apache.org/dist/axis2/nightly/ *Please* make sure you try it out as this is the last chance before we cut 1.3 Final early next week. thanks, dims -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Sé un Mejor Amante del Cine ¿Quieres saber cómo? ¡Deja que otras personas te ayuden! . -- Davanum Srinivas :: http://davanum.wordpress.com -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Sé un Mejor Amante del Cine ¿Quieres saber cómo? ¡Deja que otras personas te ayuden! . -- Davanum Srinivas :: http://davanum.wordpress.com - Sé un Mejor Amante del Cine ¿Quieres saber cómo? ¡Deja que otras personas te ayuden!. HTTP/1.1 500 Server: Apache-Coyote/1.1 Set-Cookie: JSESSIONID=82A8896CFB303A8A44309E0417510B60; Path=/axis2 Content-Type: text/html;charset=iso-8859-1 Transfer-Encoding: chunked Date: Mon, 06 Aug 2007 15:41:18 GMT Connection: close 565 !DOCTYPE HTML PUBLIC -//W3C//DTD XHTML 1.0 Strict//EN http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd; html head base href=http://127.0.0.1:8082/axis2// titleAxis2 :: Internal server error/title link href=axis2-web/css/axis-style.css rel=stylesheet type=text/css/ meta http-equiv=Content-Type content=text/html; charset=iso-8859-1/ /head body table width=100% tr td align=left
RE: [Axis2] Zero Blockers for 1.3
Hi Dims, I'm getting one problem with RC3. I'm trying to generate my code for doing my testing but, wsdl2java doesn't return control back and it uses a big amount of resources. It seems that is generating the code or some of them but it never finishes. Regards, Jorge Fernández Davanum Srinivas [EMAIL PROTECTED] escribió: Folks, At this moment there are zero blockers in JIRA for 1.3. Please try RC3 released friday (http://people.apache.org/~deepal/axis2/1.3-RC3/) or 1.3 branch's nightly build from here - http://people.apache.org/dist/axis2/nightly/ *Please* make sure you try it out as this is the last chance before we cut 1.3 Final early next week. thanks, dims -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Sé un Mejor Amante del Cine ¿Quieres saber cómo? ¡Deja que otras personas te ayuden!.
Re: Check Signature confirmation: stored SV vector not empty
Hi Sardars, I got this exception when the service didn't send the SignatureConfirmation but the client expected it. I was using policy at the server and rampart basic configuration at the client. If this is your case, you can add MustSupportSignatureConfirmation assertion in the service (you can see ws-security policy specification for this) or setEnableSignatureConfirmation(false); for the inflow chain in the client. Hope this helps, Jorge Fernández [EMAIL PROTECTED] escribió: Hey I saw your article on mail archive web site, did you ever got this resolved, I am facing the same issue, I am trying to run sample 4, faultcodesoapenv:Client/faultcode faultstringWSDoAllReceiver: security processing failed/faultstring I would appreciate if you have any info, Thanks and Regards Sachin - Sé un Mejor Amante del Cine ¿Quieres saber cómo? ¡Deja que otras personas te ayuden!.
RE: Transport error: 400 Error: Bad Request
Hi David, There is some working around it. See https://issues.apache.org/jira/browse/AXIS2-2845 Regards, Jorge Fernández David Robertson [EMAIL PROTECTED] escribió: I'm wondering if something changed in the way a client handles SOAP faults between Axis2 1.1.1 and Axis2 1.2. Previously if a fault message was thrown, the client would receive the fault message. As of 1.2, we've always gotten the error in the subject line when a fault is thrown on the server. I believe that what comes back to the client is the correct message with the fault. This still occurs with the nightly build of 1.3. (We have modified our skeleton and exception classes to follow the latest code generation.) Any help would be greatly appreciated. -David Robertson - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Sé un Mejor Amante del Cine ¿Quieres saber cómo? ¡Deja que otras personas te ayuden!.
Issues with security configurations and useOriginalwsdl parameter
Hi all,
I'm having some issues with security configuration and I need some
clarifications because I'm just learning and I've been for a while with it. If
anybody could help me it would be great.
I'm using policy at my service, trying to force the client to send SKI
certificate reference so I have sp:RequireKeyIdentifierReference/ assertion
in both Initiator Token and RecipientToken and
sp:MustSupportRefKeyIdentifier/.
In the client, I'm sending IssuerSerial references but in the service policy I
haven't got MustSupportIssuerSerialReference, so I think the service should
reject
the request but it doesn't. Am I right?
Also, I expected that the service should send SKI reference always, but, for
the encryption key it sends IssuerSerial reference. Can I force it to use
always SKI reference?
In the client, I'm signing Timestamp and Body, but in the message I can only
see
Timestamp signature. Where is Body signature? Does rampart sign only one of
them?
The last problem is that when I replace signedParts by signedElements
assertion, I can access the service but the WSDL is not generated (when
useOriginalwsdl is false) because it throws an exception:
com.ctc.wstx.exc.WstxParsingException: Undeclared namespace prefix sp
at [row,col {unknown-source}]: [1,1040]
I'm sending configurations and messages generated below.
Can anybody point me in the right direction?
Thanks in advance,
Jorge Fernández
public static OutflowConfiguration getOutflowConfiguration(){
OutflowConfiguration ofc = new OutflowConfiguration();
ofc.setActionItems(Timestamp Signature Encrypt);
ofc.setUser(client1);
ofc.setPasswordCallbackClass(client.PWCBHandler);
ofc.setSignaturePropFile(client1.properties);
ofc.setSignatureKeyIdentifier(WSSHandlerConstants.ISSUER_SERIAL);
ofc.setEncryptionKeyIdentifier(WSSHandlerConstants.ISSUER_SERIAL);
ofc.setEncryptionUser(medici-link);
ofc.setSignatureParts({Element}{http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd}Timestamp;;);
ofc.setSignBody();
ofc.setEncryptBody();
return ofc;
}
POST /axis2/services/Medici_Link HTTP/1.1
Content-Type: application/soap+xml; charset=UTF-8; action=urn:validateSystem
User-Agent: Axis2
Host: 127.0.0.1:8082
Transfer-Encoding: chunked
e38
?xml version='1.0' encoding='UTF-8'?
soapenv:Envelope xmlns:wsa=http://www.w3.org/2005/08/addressing;
xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope;
xmlns:xenc=http://www.w3.org/2001/04/xmlenc#;
soapenv:Header
wsse:Security
xmlns:wsse=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd;
soapenv:mustUnderstand=true
xenc:EncryptedKey Id=EncKeyId-3916915
xenc:EncryptionMethod
Algorithm=http://www.w3.org/2001/04/xmlenc#rsa-1_5; /
ds:KeyInfo xmlns:ds=http://www.w3.org/2000/09/xmldsig#;
wsse:SecurityTokenReference
ds:X509Data
ds:X509IssuerSerial
ds:X509IssuerNameCN=CA,OU=X1,O=X2,L=Santiago,ST=Coruna,C=ES/ds:X509IssuerName
ds:X509SerialNumber14/ds:X509SerialNumber
/ds:X509IssuerSerial
/ds:X509Data
/wsse:SecurityTokenReference
/ds:KeyInfo
xenc:CipherData
xenc:CipherValuedr/IpAm4eczqbtJBxypHAPWwtDLdU6AveSBEvKLqWkxj770t8XTm5GrZsvgALxINEVU5lZL/v9QxDGu9I6CTH5JxkmBzWDtVmDWxD4hAkfjHtBiwfhUm227OlENApZqNCi9/zbQqvirl9e0IH65zm18IO0/LLGc/mDhH3Hu5YR8=/xenc:CipherValue
/xenc:CipherData
xenc:ReferenceList
xenc:DataReference URI=#EncDataId-29056009 /
/xenc:ReferenceList
/xenc:EncryptedKey
ds:Signature xmlns:ds=http://www.w3.org/2000/09/xmldsig#;
Id=Signature-33431531
ds:SignedInfo
ds:CanonicalizationMethod
Algorithm=http://www.w3.org/2001/10/xml-exc-c14n#; /
ds:SignatureMethod
Algorithm=http://www.w3.org/2000/09/xmldsig#rsa-sha1; /
ds:Reference URI=#Timestamp-15293014
ds:Transforms
ds:Transform
Algorithm=http://www.w3.org/2001/10/xml-exc-c14n#; /
/ds:Transforms
ds:DigestMethod
Algorithm=http://www.w3.org/2000/09/xmldsig#sha1; /
ds:DigestValueKHfeVCmFYGNhDXhFYAssmRV7DPo=/ds:DigestValue
/ds:Reference
/ds:SignedInfo
ds:SignatureValueQ1x8bI4520lAzba8m2c6aUP1f+dwApAjGWVAonkFwb//JdZa7pURoQP5fS1sjONegdx6Yc9oQiki3yuP7RJ8ieHbWt44Im5M9w5e0pba+nDR0xAm0OB+01ndy6NZ3v9dJ4puhk6Mew93VQTXPmBDaVd2Y3pmZ3/Tqt2mPtdjO4A=/ds:SignatureValue
ds:KeyInfo Id=KeyId-17905186
wsse:SecurityTokenReference
Re: Check Signature confirmation: stored SV vector not empty
Hi Dimithu, I'd read the specification but I'd missed that detail. Thanks for that. But my real problem was the Check Signature confirmation: stored SV vector not empty Exception. I resolved it adding the sp:RequireSignatureConfirmation/ assertion in the server policy because my client configured with basic rampart, seemed to expect that. I though it wasn't necessary. I also had to replace the Timestamp Signature Encrypt actions order with Signature Encrypt Timestamp in my client when changing form basic configuration on the server to policy but I don't know exactly why. Thanks a lot, Jorge Fernández Dimuthu [EMAIL PROTECTED] escribió: Hi, Please check 7.2 [Timestamp] Property section of Security Policy specification[1] Regards, Dimuthu [1]http://specs.xmlsoap.org/ws/2005/07/securitypolicy/ws-securitypolicy.pdf On Mon, 2007-07-30 at 18:15 +0200, Jorge Fernandez wrote: Hi, I'm getting that exception. I'm using axis2 1.2 and rampart 1.2 in both client and server sides. I receive that exception in the client. The first thing I can see in my client is : 30-jul-2007 16:46:51 org.apache.xml.security.signature.Reference verify INFO: Verification successful for URI #Timestamp-19502806 That is the Timestamp sent back from the server. It comes signed even if in my server policy I don't say that it should be signed. I searched for elements in the response as I could see in http://mail-archives.apache.org/mod_mbox/ws-wss4j-dev/200610.mbox/[EMAIL PROTECTED] and I didn't find any. When I used rampart configuration without policy, I didn't have any problem. Actually is what I'm using at the client side for sending the messages to the sever. In the server, I'm using sample3 policy from rampart distribution. Can anybody tell me why is this happening?? Thanks, Jorge Fernández This is the stack trace: org.apache.axis2.AxisFault: WSHandler: Check Signature confirmation: stored SV vector not empty at org.apache.rampart.handler.WSDoAllReceiver.processMessage(WSDoAllReceiver.java:100) at org.apache.rampart.handler.WSDoAllHandler.invoke(WSDoAllHandler.java:72) at org.apache.axis2.engine.Phase.invoke(Phase.java:383) at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:203) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:131) at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:378) at org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:294) at client.Medici_LinkSOAP12PortStub.validateSystem(Medici_LinkSOAP12PortStub.java:747) at client.ClientUtilities.validateSystemTest(ClientUtilities.java:62) at client.Client.main(Client.java:33) Caused by: org.apache.ws.security.WSSecurityException: WSHandler: Check Signature confirmation: stored SV vector not empty at org.apache.ws.security.handler.WSHandler.checkSignatureConfirmation(WSHandler.java:328) at org.apache.rampart.handler.WSDoAllReceiver.processBasic(WSDoAllReceiver.java:300) at org.apache.rampart.handler.WSDoAllReceiver.processMessage(WSDoAllReceiver.java:91) ... 9 more - Sé un Mejor Amante del Cine ¿Quieres saber cómo? ¡Deja que otras personas te ayuden!. -- http://wso2.org - Sé un Mejor Amante del Cine ¿Quieres saber cómo? ¡Deja que otras personas te ayuden!.
Check Signature confirmation: stored SV vector not empty
Hi, I'm getting that exception. I'm using axis2 1.2 and rampart 1.2 in both client and server sides. I receive that exception in the client. The first thing I can see in my client is : 30-jul-2007 16:46:51 org.apache.xml.security.signature.Reference verify INFO: Verification successful for URI #Timestamp-19502806 That is the Timestamp sent back from the server. It comes signed even if in my server policy I don't say that it should be signed. I searched for wsse:SignatureConfirmation elements in the response as I could see in http://mail-archives.apache.org/mod_mbox/ws-wss4j-dev/200610.mbox/[EMAIL PROTECTED] and I didn't find any. When I used rampart configuration without policy, I didn't have any problem. Actually is what I'm using at the client side for sending the messages to the sever. In the server, I'm using sample3 policy from rampart distribution. Can anybody tell me why is this happening?? Thanks, Jorge Fernández This is the stack trace: org.apache.axis2.AxisFault: WSHandler: Check Signature confirmation: stored SV vector not empty at org.apache.rampart.handler.WSDoAllReceiver.processMessage(WSDoAllReceiver.java:100) at org.apache.rampart.handler.WSDoAllHandler.invoke(WSDoAllHandler.java:72) at org.apache.axis2.engine.Phase.invoke(Phase.java:383) at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:203) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:131) at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:378) at org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:294) at client.Medici_LinkSOAP12PortStub.validateSystem(Medici_LinkSOAP12PortStub.java:747) at client.ClientUtilities.validateSystemTest(ClientUtilities.java:62) at client.Client.main(Client.java:33) Caused by: org.apache.ws.security.WSSecurityException: WSHandler: Check Signature confirmation: stored SV vector not empty at org.apache.ws.security.handler.WSHandler.checkSignatureConfirmation(WSHandler.java:328) at org.apache.rampart.handler.WSDoAllReceiver.processBasic(WSDoAllReceiver.java:300) at org.apache.rampart.handler.WSDoAllReceiver.processMessage(WSDoAllReceiver.java:91) ... 9 more - Sé un Mejor Amante del Cine ¿Quieres saber cómo? ¡Deja que otras personas te ayuden!.
message receiver code generation
Hi all, When I have operations in the WSDL that follow differente MEPs and I generate the message receivers I can see that toOM and toEnvelope methods are defined for every operation in each message receiver even if they don't use the MEP defined in that message receiver. Is the codegen expected to work like this?? Regards, Jorge Fernández - Sé un Mejor Amante del Cine ¿Quieres saber cómo? ¡Deja que otras personas te ayuden!.
Re: wsdl2java generates invalid xml file
Hi Babette, Maybe in this issue you can identify your problem: https://issues.apache.org/jira/browse/AXIS2-2325 Regards, Jorge Fernández Lahiru Sandakith [EMAIL PROTECTED] escribió: Hi Babette, Yes the plugin should work with multiple packages with service class and all the other dependent classes. All you need it to do is include the third party content or the folders that needed for the service class. http://ws.apache.org/axis2/tools/1_2/eclipse/wsdl2java-plugin.html if possible you could log a JIRA and attach the classes, we ll look in to it. Thanks Lahiru. On 7/26/07, Babette v. Gijlswijk [EMAIL PROTECTED] wrote: Hi, I have a question about the wsdl2java plugin for eclipse. I used the wsdl2Java plugin to generate a wsdl file. I have a service class and an exceptionclass which are defined in different packages. When I generate the wsdl file, the plugin defines a second namespace in a second shema definition tag which causes the wsdl file to be invalid. If I define the exception in the same package as the service the plugin produces a correct wsdl file. Does the plugin support multiple namespaces? Thanx Babette -- Thanks Lahiru Sandakith http://sandakith.wordpress.com/ GPG Key Fingerprint : 8CD8 68E0 4CBC 75CB 25BC 1AB1 FE5E 7464 1F01 9A0F - Sé un Mejor Viajero ¿Quieres saber cómo? ¡Deja que otras personas te ayuden! .
Re: [Axis2] Problem using SOAP12 vs SOAP11?
Hi Jose, There is some work around it. See: https://issues.apache.org/jira/browse/AXIS2-2845 http://marc.info/?l=axis-devm=118285729209577w=2 Regards, Jorge Fernández Jose Luis Alba [EMAIL PROTECTED] escribió: Hi Keith, The problem isn't the status code. The problem is that using SOAP11 I receive Exceptions that web service launches. But using SOAP12 always I receive an AxisFault with message 400: Bad Request, not the Exception I launched. Is for that I was talking about a bug. Any ideas? Thanks in advance, Jose keith chapman [EMAIL PROTECTED] escribió: Here are the details. http://www.w3.org/TR/soap12-part2/#http-respbindprocess Thanks, Keith. On 7/27/07, keith chapman [EMAIL PROTECTED] wrote: Ho Jose, This is not a bug. The SOAP 1.2 specification mentions that we should send HTTP code 400 in a fault if the fault code is soap:Sender. This is the reason for getting 400 when using SOAP 1.2 and 500 when using SOAP 1.1. Thanks, Keith. On 7/27/07, Jose Luis Alba [EMAIL PROTECTED] wrote: Hi, Recently I've been working on a test web service in Axis2 (1.3-RC1). That service launchs checked exceptions but the behavior is different if I use SOAP11 or SOAP12 from the client. When I use SOAP12 all responses from my exceptions are and AxisFault with error 400: Bad request. (That's done in MessageContextBuilder - createFaultEnvelope - getSenderFaultCode) When I use SOAP11 from the client I receive and AxisFault but this time with an status error 500 and with the message of my exception. That's is what I excepted! Why this behavior? There's a bug in the SOAP12? I'm missing something? Thanks, Jose - Sé un Mejor Amante del Cine ¿Quieres saber cómo? ¡Deja que otras personas te ayuden! . -- Keith Chapman WSO2 Inc. Oxygen for Web Services Developers. http://wso2.org/ -- Keith Chapman WSO2 Inc. Oxygen for Web Services Developers. http://wso2.org/ - Sé un Mejor Amante del Cine ¿Quieres saber cómo? ¡Deja que otras personas te ayuden! . - Sé un Mejor Amante del Cine ¿Quieres saber cómo? ¡Deja que otras personas te ayuden!.
RE: How to create certificate .cer file?
Hi Srini, You need to use the Java keytool. I think this is the command: rem keytool -export -alias myalias -file mycertificate.cer -keystore mykeystore.jks -storepass mypassword You can find all the information about keytool here: http://publib.boulder.ibm.com/html/as400/v5r1/ic2931/index.htm?info/rzaha/keytool.htm Regards, Jorge Fernández Srinivasa Rao K [EMAIL PROTECTED] escribió: Hi, Can we create .cer file from jks file.? I have trust/key jks files with me. How can I create the cer file to connect to https web services from C# client? Thanks, Srini - Looking for a deal? Find great prices on flights and hotels with Yahoo! FareChase. - ¡Descubre una nueva forma de obtener respuestas a tus preguntas! Entra en Yahoo! Respuestas.
Re: Unexpected subelement error using useOriginalWsdl in Axis2
Hola Jose,
I usually have those problems when using rampart but only with classes that
extend from others.
Regards,
Jorge Fernández
Jose Luis Alba [EMAIL PROTECTED] escribió: Hi Mike,
The InputData and OutputData are simple JavaBean classes as:
package dev.axis2.ws.data;
public class InputData {
private String data;
public String getData() {
return data;
}
public void setData(String data) {
this.data = data;
}
}
Recently I've tried with the last snapshot and with the Axis2 1.3 RC1 that
Deepal proposed to me.
Now the SOAP response has changed to:
soapenv:Envelope xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope;
soapenv:Body
ns:testDataResponse xmlns:ns=http://service.ws.axis2.dev;
ns:return type=dev.axis2.ws.data.OutputData
ns:datadatos de entrada/ns:data
/ns:return
/ns:testDataResponse
/soapenv:Body
/soapenv:Envelope
The solution is near but not sufficient. The return element that encloses the
data element now has a type attribute but the client continues to launch an
unexpected subelement exception due to incorrect namespace for data.
- I generated the clients in ADB mode.
Any more ideas? I will continue investigating..
Thanks all
Jose
Mike Patton [EMAIL PROTECTED] escribió: Jose,
Does your OutputData class extend a java collection object or similar data
type? If so, then this is why you are getting such an error. You should return
a single element; even if you have an array or so to return, wrap that in a
property of another class and return that other type instead.
Hope that helps.
Mike
Jose Luis Alba [EMAIL PROTECTED] wrote:
Hi,
- I'm using Axis2 1.2
I've create a POJO test web service that resides in package
dev.axis2.ws.service and uses in/out bean data from package dev.axis2.ws.data.
The interface is:
package dev.axis2.ws.service;
import dev.axis2.ws.data.InputData;
import dev.axis2.ws.data.OutputData;
public interface TestService {
public OutputData testData(InputData input);
}
1) When I use automatic wsdl generation from Axis (in the services.xml file)
all goes well. Here is the SOAP response of the execution:
soapenv:Envelope xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope;
soapenv:Body
ns:testDataResponse xmlns:ns=http://service.ws.axis2.dev/xsd;
ns:return
data xmlns=http://data.ws.axis2.dev/xsd;datos de entrada/data
/ns:return
/ns:testDataResponse
/soapenv:Body
/soapenv:Envelope
2) Things goes wrong when I use the parameter useOriginalWsdl in the
services.xml file. Here the services.xml file:
service name=TestService
messageReceivers
messageReceiver
mep=http://www.w3.org/2004/08/wsdl/in-only;
class=org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver /
messageReceiver
mep=http://www.w3.org/2004/08/wsdl/in-out;
class=org.apache.axis2.rpc.receivers.RPCMessageReceiver /
/messageReceivers
parameter locked=false
name=ServiceClassdev.axis2.ws.service.TestServiceImpl/parameter
parameter locked=false name=useOriginalwsdltrue/parameter
parameter locked=false name=modifyUserWSDLPortAddresstrue/parameter
/service
The SOAP response I receive in the client side is:
soapenv:Envelope xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope;
soapenv:Body
ns:testDataResponse xmlns:ns=http://service.ws.axis2.dev/xsd;
ns:return
ns:datadatos de entrada/ns:data
/ns:return
/ns:testDataResponse
/soapenv:Body
/soapenv:Envelope
In this case the namespace for the data element (it should map to
http://data.ws.axis2.dev/xsd) is missing and the client throws and Unexpected
subelement exception.
I have tried:
- Axis2 1.2
- Axis2 1.1.1
- Axis2 last snapshot
- Using the wsdl generated automatically
- Using the wsld generated by axis2 tools (ant task and by command line)
In all cases the behavior is the same: Unexpeted subelement and the missing
namespace in the response message.
Could you help me please? Thanks in advance!
Jose Luis
-
Sé un Mejor Amante del Cine
¿Quieres saber cómo? ¡Deja que otras personas te ayuden! .
-
Get the free Yahoo! toolbar and rest assured with the added security of spyware
protection.
-
Sé un Mejor Amante del Cine
¿Quieres saber cómo? ¡Deja que otras personas te ayuden! .
-
Sé un Mejor Amante del Cine
¿Quieres saber cómo? ¡Deja que otras personas te ayuden!.
RE: rpc-encoded vs rpc-literal vs document-literal migrate Axis1.4 wsdl (rpc-encoded) to Axis2 doc-lit
Hi David, I found this article very useful. Maybe it can help you: http://www-128.ibm.com/developerworks/webservices/library/ws-whichwsdl/ Regards, Jorge Fernández david [EMAIL PROTECTED] escribió: Hello Ann and all the Axis2/wsdl gurus and users, I have a .NET client generated WSDL (rpc-encoded). I want to convert this WSDL to either: rpc-literal or document-literal such that I can run Axis2 wsdl2java and generate an Axis2 service. Currently, this service is running as Axis1.4 and I would appreciate very much any and all ideas and suggestions as to how to migrate to Axis2. I know the Axis2 wsdl2java does not support rpc-encoded. I read Ann Manes blog about converting wsdls but I am not sure if this can be extended to rpc-encoded. I am secretly hoping Ann Manes will reply but any and all rants and raves welcomed. I can reply with the target wsdl in question. Please advise, David. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Sé un Mejor Amante del Cine ¿Quieres saber cómo? ¡Deja que otras personas te ayuden!.
RE: [axis2] SwA problem (DataHandler/DataSource problem)
Hi Zolv, I don't know if this will help you but there is another way. with org.apache.axiom.attachments.ByteArrayDataSource but you will have to transform your text data into bytes and then transform them into ByteArrayDataSource. There is an example in axis2 distribution to attach a file with SwA. Regards, Jorge Fernández Radek Adamiak [EMAIL PROTECTED] escribió: Hi I have found many tutorials and samples how to insert file attachment into SOAP message using Axis2: http://wso2.org/library/1148 http://ws.apache.org/axis2/1_2/mtom-guide.html ... but I didn't find how to put as attachment simple text using SwA (not MTOM with encoding into Base64). Esentially, I don't know how to instantiate class DataSource. There are only FileDataSource and URLDataSource classes and I didn't find any other ways to put attachment into message, only those ones. Thx for eventual reply zolv - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - LLama Gratis a cualquier PC del Mundo. Llamadas a fijos y móviles desde 1 céntimo por minuto. http://es.voice.yahoo.com
repeated namespaces definitions in soap messages
Hi all, I'm having some issues with the namespaces definitions in SOAP messages. Apparently it is due to definitions in the WSDL. I have the definitions of the SOAP messages bodies in one namespace and their content in another. For example I have this SOAP Message definition in http://op_messages.medici_link/xsd: xs:element name=getOntologySignalsResponse xs:complexType xs:sequence xs:element maxOccurs=unbounded name=signals nillable=true type=ns3:ontSignal/ /xs:sequence /xs:complexType /xs:element and the inner signals element in http://ontology.communication_data_model.medici_link/xsd: xs:complexType name=ontSignal xs:sequence xs:element name=abbreviation nillable=true type=xs:string/ xs:element name=code type=xs:int/ xs:element name=description nillable=true type=xs:string/ xs:element name=localization nillable=true type=xs:string/ xs:element name=name nillable=true type=xs:string/ xs:element name=nomenclature nillable=true type=xs:string/ xs:element name=valueUnit nillable=true type=ax24:ontUnit/ /xs:sequence /xs:complexType ontUnit is defined also in this namespace: xs:complexType name=ontUnit xs:sequence xs:element name=abbreviation nillable=true type=xs:string/ xs:element name=code type=xs:int/ xs:element name=name nillable=true type=xs:string/ xs:element name=nomenclature nillable=true type=xs:string/ xs:element name=type nillable=true type=xs:string/ /xs:sequence /xs:complexType The SOAP message generated is below. HTTP/1.1 200 OK Server: Apache-Coyote/1.1 Content-Type: application/soap+xml; action=urn:getOntologySignals;charset=UTF-8 Transfer-Encoding: chunked Date: Tue, 17 Jul 2007 15:40:29 GMT 2000 ?xml version='1.0' encoding='UTF-8'? soapenv:Envelope xmlns:wsa=http://www.w3.org/2005/08/addressing; xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope; soapenv:Header wsa:ReplyTo wsa:Addresshttp://www.w3.org/2005/08/addressing/none/wsa:Address wsa:ReferenceParameters axis2:ServiceGroupId xmlns:axis2=http://ws.apache.org/namespaces/axis2;urn:uuid:C280A13EC417DEC8D71184686819010/axis2:ServiceGroupId /wsa:ReferenceParameters /wsa:ReplyTo wsa:MessageIDurn:uuid:C280A13EC417DEC8D71184686821544/wsa:MessageID wsa:Actionurn:getOntologySignals/wsa:Action wsa:RelatesTourn:uuid:945F7F9F7EA37C1D7F1184686821454/wsa:RelatesTo /soapenv:Header soapenv:Body ns3:getOntologySignalsResponse xmlns:ns3=http://op_messages.medici_link/xsd; ns3:signals s1:abbreviation xmlns:s1=http://ontology.communication_data_model.medici_link/xsd;ECG aVR/s1:abbreviation s2:code xmlns:s2=http://ontology.communication_data_model.medici_link/xsd;62/s2:code s3:description xmlns:s3=http://ontology.communication_data_model.medici_link/xsd;/s3:description s4:localization xmlns:s4=http://ontology.communication_data_model.medici_link/xsd;aVR/s4:localization s5:name xmlns:s5=http://ontology.communication_data_model.medici_link/xsd;/s5:name s6:nomenclature xmlns:s6=http://ontology.communication_data_model.medici_link/xsd;IEEE1073/s6:nomenclature valueUnit xmlns=http://ontology.communication_data_model.medici_link/xsd; abbreviationmv/abbreviation code4274/code namemilivoltio/name nomenclatureIEEE1073/nomenclature typeVoltaje/type /valueUnit /ns3:signals /ns3:getOntologySignalsResponse /soapenv:Body /soapenv:Envelope0 The problem is that each element in ontSignal defines the same namespace with different prefixes generating redundant code. However, in the case of the valueUnit element, the namespace is defined in the wrapper element. I suppose that the difference is that in the first case, the wrapper element has a different namespace from its children elements and in the latter, both the wrapper element and its elements have the same namespace. Shouldn't the behaviour be always as in the latter case Thanks, Jorge Fernández - LLama Gratis a cualquier PC del Mundo. Llamadas a fijos y móviles desde 1 céntimo por minuto. http://es.voice.yahoo.com
RE: Web Services Interoperability
Hi, I have a doubt related with interoperability. I'm using soap session and I realized that ServiceGroupID has an axis2 namespace so I think this would make my servie incompatible with some clients. Is this right?? Any of the session scopes is compatible between all plataforms?? Thanks and regards, Jorge Fernández Srinivasa Rao K [EMAIL PROTECTED] escribió: Thank you! To be honest, WS-Addressing is new for me and I think we are not using the Adressing. Thanks Zachary Marshall [EMAIL PROTECTED] wrote: Are you using WS-Addressing? I had an interoperability problem going the other way, from Java client to .NET service. The problem was with mismatched namespaces. In that case, the following fixed the problem: _options.setProperty(AddressingConstants.WS_ADDRESSING_VERSION, AddressingConstants.Submission.WSA_NAMESPACE); Obviously, since you have a .NET client and a Java server, this might not be the issue. If you are using WS-Addressing, then I would examine the payload sent from .NET and ensure the namespaces match what you expect for your Java server. I can't specifically address your second question. - From: Srinivasa Rao K [mailto:[EMAIL PROTECTED] Sent: Monday, July 16, 2007 12:38 PM To: axis-user@ws.apache.org Subject: Web Services Interoperability Hi, I need some help on Web Services Interoperability. We have an applicati0n on WebShphere 6 (RAD Development environment) and Web Services are working fine with Java(Axis) Client environment. But one client is trying to access the same services from .Net/C# environment and we are not successful. WSDLs: The WSDL fils are generated dynamically and we have one service with 4 different names and in each service Style/Use and encoding are different, configuration in server-config.wsdd file as follows: service name=service1 provider=java:RPC style=document typeMapping ...encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; .../ service name=service2 provider=java:RPC style=document use=literal typeMapping ...encodingStyle= .../ service name=service3 provider=java:RPC typeMapping ... encodingStyle=http://schemas.xmlsoap.org/soap/encoding/.../ service name=service4 provider=java:RPC use=literal typeMapping ... encodingStyle= .../ All these 4 services point to a single service. Now my question is, which WSDL file generated out of the four services should be used for .Net/C# client. Any additional things need to be done for this interoperablity? I really appreciate any kind of help regarding the same. Thanks in advance. Regards Srinivas. - Get the free Yahoo! toolbar and rest assured with the added security of spyware protection. - Be a better Globetrotter. Get better travel answers from someone who knows. Yahoo! Answers - Check it out. - LLama Gratis a cualquier PC del Mundo. Llamadas a fijos y móviles desde 1 céntimo por minuto. http://es.voice.yahoo.com
Sessions
Hi, I've been stuck for a long time with this, searching form information and didn't find the information. I wanted to know how does Axis2 manage timeouts. I though that SessionContext was the one who that but I couldn't get any information to confirm that and don't even know how to manage it. I see in the axis2.xml the timeout interval set as 30 seconds but even though passing a lot of time waiting for it, I never reached that condition. I decided to build my own session control but I don't know which Axis2 resources do I have to release or which methods do I have to call to do that when I want to end a session. Could anybody help me?? Regards, Jorge Fernández - Sé un Mejor Amante del Cine ¿Quieres saber cómo? ¡Deja que otras personas te ayuden!.
RE: [Axis2] getInboundFaultFromMessageContext error when accessing the service
Hi,
I got the same problem sometimes, when deploying my service under Axis2 as
standalone server while having it running under Tomcat works out.
Does anybody know what's the problem with this??
Regards,
Jorge Fernández
Mike Patton [EMAIL PROTECTED] escribió: Hi,
I am new in the web service world and I am developing a simple web service
using Axis2, Eclipse, and the Axis2 Eclipse Plugin. I have a simple Pojo of
type Employee with getters and setters, and a service class called
EmployeeService that has only one method. The method has the following
signature: ListPerson getEmployees(String UserPrivilege, String username,
String password). Its implementation connects to a database and retrieves that
the necessary data to build and return a java.util.ArrayList of Employee
objects.
Using the Eclipse Plugin and following the tutorial on
http://wso2.org/library/1719, I generated a web service that exposes the class
EmployeeService's getEmployees(String, String, String) method. I also wrote a
client class called Main.java to test the service. However, when I run the
client, I get the following error:
org.apache.axis2.AxisFault: The service cannot be found for the endpoint
reference (EPR) http://localhost:8080/axis2/services/EmployeeService
at
org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:434)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:373)
at
org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:294)
at
com.myCompany.service.EmployeeServiceSOAP11PortStub.getEmployees(EmployeeServiceSOAP11PortStub.java:151)
at com.myCompany.client.Main.main(Main.java:34)
-
Line 34 of Main.java has the following statement:
EmployeeServiceSOAP11PortStub.GetEmployeesResponse getEmployeesResponse =
stub.getEmployees(getEmployees);
-
The core client code is below.
try{
stub = new
EmployeeServiceSOAP11PortStub(http://localhost:8080/axis2/services/EmployeeService;);
EmployeeServiceSOAP11PortStub.GetEmployees getEmployees = new
EmployeeServiceSOAP11PortStub.GetEmployees();
EmployeeServiceSOAP11PortStub.GetEmployeesResponse getEmployeesResponse =
stub.getEmployees(getEmployees);
OMElement omelement = getEmployeesResponse.get_return();
System.out.println(omelement.toStringWithConsume());
}catch(AxisFault e){
e.printStackTrace();
}catch(RemoteException e){
e.printStackTrace();
}catch(XMLStreamException e){
e.printStackTrace();
}
Thank you in advance for your comments or suggestions. I am also placing the
WSDL file below.
wsdl:definitions xmlns:soap12=http://schemas.xmlsoap.org/wsdl/soap12/;
xmlns:http=http://schemas.xmlsoap.org/wsdl/http/;
xmlns:mime=http://schemas.xmlsoap.org/wsdl/mime/;
xmlns:xsd=http://service.myCompany.com/xsd;
xmlns:ns=http://service.myCompany.com;
xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/;
xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/;
targetNamespace=http://service.myCompany.com;
wsdl:types
xs:schema xmlns:xs=http://www.w3.org/2001/XMLSchema;
attributeFormDefault=qualified
elementFormDefault=qualified
targetNamespace=http://service.myCompany.com/xsd;
xs:element name=getEmployees
xs:complexType
xs:sequence
xs:element name=userPrivilege nillable=true type=xs:string /
xs:element name=username nillable=true type=xs:string /
xs:element name=password nillable=true type=xs:string /
/xs:sequence
/xs:complexType
/xs:element
xs:element name=getEmployeesResponse
xs:complexType
xs:sequence
xs:element name=return nillable=true type=xs:anyType /
/xs:sequence
/xs:complexType
/xs:element
/xs:schema
/wsdl:types
wsdl:message name=getEmployeesMessage
wsdl:part name=part1 element=xsd:getEmployees /
/wsdl:message
wsdl:message name=getEmployeesResponseMessage
wsdl:part name=part1 element=xsd:getEmployeesResponse /
/wsdl:message
wsdl:portType name=EmployeeServicePortType
wsdl:operation name=getEmployees
wsdl:input xmlns:wsaw=http://www.w3.org/2006/05/addressing/wsdl;
wsaw:Action=urn:getEmployees
message=ns:getEmployeesMessage /
wsdl:output xmlns:wsaw=http://www.w3.org/2006/05/addressing/wsdl;
message=ns:getEmployeesResponseMessage
wsaw:Action=urn:getEmployees /
/wsdl:operation
/wsdl:portType
wsdl:binding name=EmployeeServiceSOAP11Binding
type=ns:EmployeeServicePortType
soap:binding transport=http://schemas.xmlsoap.org/soap/http;
style=document /
wsdl:operation name=getEmployeessoap:operation
soapAction=urn:getEmployees style=document /
wsdl:inputsoap:body use=literal /
/wsdl:inputwsdl:outputsoap:body use=literal
RE: Unexpected number of X509Data: for encryption
Hi Richard, As far as I know, that with the line on the services.xml parameter name=''encryptionUser value=useReqSigCert you are telling the service that for encrypting the message it has to use the key or the reference that the client sent on the message. If in the client you don't define the signatureKeyIdentifier or you have signatureKeyIdentifierIssuerSerial/signatureKeyIdentifier or signatureKeyIdentifierSKIKeyIdentifier/signatureKeyIdentifier You need to have the client's public key in the services keystore because with these definitions, the client sends a reference to the public key and not the key itself. If, instead you put in the client the line: signatureKeyIdentifierDirectReference/signatureKeyIdentifier the client will send the key and you don't have to import it at the service keystore. The default option is IssuerSerial. Hope this will help you Regards, Jorge Fernández Richard DeGrande [EMAIL PROTECTED] escribió: Hi, I keep getting the above error when making a request. This started after I added My key contains one alias that is has a chain length of 2 (the private key and certificate)... Keystore type: jks Keystore provider: SUN Your keystore contains 1 entry Alias name: webservice Creation date: Jun 27, 2007 Entry type: keyEntry Certificate chain length: 2 Certificate[1]: Owner: CN=webservice, OU=Weblogic, O=some company, L=Golden, ST=Colorado, C=US Issuer: [EMAIL PROTECTED], CN=somecompany, O=webservice, L=Golden, ST=Colorado, C=US Serial number: 26 Valid from: Wed Jun 27 10:45:06 MDT 2007 until: Sat Jun 24 10:45:06 MDT 2017 Certificate fingerprints: MD5: DF:15:17:4C:B1:93:B6:83:A1:3B:60:83:2D:B8:36:8B SHA1: 48:9E:5E:97:23:8C:1D:A4:95:97:8E:73:0A:C7:84:00:18:25:17:BD Certificate[2]: Owner: [EMAIL PROTECTED], CN=somecompany, O=webservice, L=Golden, ST=Colorado, C=US Issuer: [EMAIL PROTECTED], CN=somecompany, O=webservice, L=Golden, ST=Colorado, C=US Serial number: 0 Valid from: Tue Mar 01 11:15:08 MST 2005 until: Fri Feb 27 11:15:08 MST 2015 Certificate fingerprints: MD5: 37:60:62:2D:6B:E8:FA:71:D9:F6:DA:9B:B4:2E:B0:C5 SHA1: 43:AD:25:98:1F:42:71:B8:54:15:48:04:06:59:28:E7:90:6F:51:07 What is the cause of this error ? thanks in advance - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Sé un Mejor Amante del Cine ¿Quieres saber cómo? ¡Deja que otras personas te ayuden!.
Re: rampart causes problems with hierarchies
https://issues.apache.org/jira/browse/RAMPART-53 created Davanum Srinivas [EMAIL PROTECTED] escribió: Jorge, Please log a new bug with your test case. thanks, dims On 7/4/07, Jorge Fernandez wrote: Hi, Some months ago, I had some problems with the use of hierarchies with adb and xmlbeans. Apparently they were resolved with adb but know, I'm getting the same error. For example: I have an array of an object called parent and I put into that array instances of child1 or child2 (those inherit from parent). In the xml generated from that array should appear the xsi:type attribute but when I engage rampart module, that attribute dissapears. So maybe that was the cause of the problems I had before. See https://issues.apache.org/jira/browse/XMLBEANS-329 and https://issues.apache.org/jira/browse/AXIS2-2578. ¡Descubre una nueva forma de obtener respuestas a tus preguntas! Entra en Yahoo! Respuestas. -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - ¡Descubre una nueva forma de obtener respuestas a tus preguntas! Entra en Yahoo! Respuestas.
xs:element in schemas
Hi, I see in the schemas generated by WSDL that there are elements called xs:ComplexType and elements xs:element with the same name. What is the purpose for the last ones?? Regards, Jorge Fernández - ¡Descubre una nueva forma de obtener respuestas a tus preguntas! Entra en Yahoo! Respuestas.
Re: rampart causes problems with hierarchies
While this issue is not fixed, Is there a way I can engage the rampart module per operation, so I can desactivate it for those operations having problems??? I tried in the services.xml but it's not possible. Thanks, Jorge Fernández Jorge Fernandez [EMAIL PROTECTED] escribió: https://issues.apache.org/jira/browse/RAMPART-53 created Davanum Srinivas [EMAIL PROTECTED] escribió: Jorge, Please log a new bug with your test case. thanks, dims On 7/4/07, Jorge Fernandez wrote: Hi, Some months ago, I had some problems with the use of hierarchies with adb and xmlbeans. Apparently they were resolved with adb but know, I'm getting the same error. For example: I have an array of an object called parent and I put into that array instances of child1 or child2 (those inherit from parent). In the xml generated from that array should appear the xsi:type attribute but when I engage rampart module, that attribute dissapears. So maybe that was the cause of the problems I had before. See https://issues.apache.org/jira/browse/XMLBEANS-329 and https://issues.apache.org/jira/browse/AXIS2-2578. ¡Descubre una nueva forma de obtener respuestas a tus preguntas! Entra en Yahoo! Respuestas. -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - ¡Descubre una nueva forma de obtener respuestas a tus preguntas! Entra en Yahoo! Respuestas. - Sé un Mejor Amante del Cine ¿Quieres saber cómo? ¡Deja que otras personas te ayuden!.
Re: Exception in rampart configuration with inflow - outflow classes
It worked!!
Thanks a lot.
About Policies, do you know where can I find any sample on how to get a service
policy from the client and check the compatibility with client's policy?? In
rampart samples, policies are set on services.xml and I don't know how can the
client access them. Should I put them in the WSDL and read them with any
special method??
Could someone point me on a nice sample on that??
Regards,
Jorge Fernández
Dimuthu [EMAIL PROTECTED] escribió: Hi,
Please try this,
stub._getServiceClient().getOptions().setProperty(WSSHandlerConstants.OUTFLOW_SECURITY,
ClientUtilities.getOutflowConfiguration().getProperty());
stub._getServiceClient().getOptions().setProperty(WSSHandlerConstants.INFLOW_SECURITY,
ClientUtilities.getInflowConfiguration().getProperty());
You can also load different policy objects for different client calls.
Cheers,
Dimuthu
On Wed, 2007-07-04 at 00:07 +0200, Jorge Fernandez wrote:
Hi,
For quite a long time I've been trying to configure a client that is
invoking some operations to encrypt just some of the messages. I have
read in this page that the rampart 1.0 configuration style could be
use even though is marked as deprecated.
http://ruchith.blogspot.com/2007/06/apache-rampart-12-released.html
So I tried to do it and I'm getting the following exception:
rg.apache.axis2.AxisFault: Configureation error
at
org.apache.rampart.handler.WSDoAllSender.processMessage(WSDoAllSender.java:94)
at
org.apache.rampart.handler.WSDoAllHandler.invoke(WSDoAllHandler.java:72)
at org.apache.axis2.engine.Phase.invoke(Phase.java:383)
at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:203)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:433)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:330)
at
org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:294)
at
client.Medici_LinkSOAP12PortStub.validateSystem(Medici_LinkSOAP12PortStub.java:747)Validating
system ch4_001mu...
at
client.ClientUtilities.validateSystemTest(ClientUtilities.java:73)
at client.Client.main(Client.java:33)
Caused by: org.apache.axis2.AxisFault: Configureation error
at
org.apache.rampart.handler.WSDoAllSender.processBasic(WSDoAllSender.java:151)
at
org.apache.rampart.handler.WSDoAllSender.processMessage(WSDoAllSender.java:88)
... 9 more
Caused by: java.lang.ClassCastException:
org.apache.rampart.handler.config.InflowConfiguration cannot be cast
to org.apache.axis2.description.Parameter
at
org.apache.rampart.util.HandlerParameterDecoder.processParameters(HandlerParameterDecoder.java:63)
at
org.apache.rampart.handler.WSDoAllSender.processBasic(WSDoAllSender.java:149)
... 10 more
I'm doing this:
stub._getServiceClient().getOptions().setProperty(WSSHandlerConstants.OUTFLOW_SECURITY,
ClientUtilities.getOutflowConfiguration());
stub._getServiceClient().getOptions().setProperty(WSSHandlerConstants.INFLOW_SECURITY,
ClientUtilities.getInflowConfiguration());
public static OutflowConfiguration getOutflowConfiguration(){
OutflowConfiguration ofc = new OutflowConfiguration();
ofc.setActionItems(Timestamp Signature Encrypt);
ofc.setUser(client1);
ofc.setPasswordCallbackClass(client.PWCBHandler);
ofc.setSignaturePropFile(client1.properties);
ofc.setSignatureKeyIdentifier(WSSHandlerConstants.BST_DIRECT_REFERENCE);
//ofc.setEncryptionKeyIdentifier(WSSHandlerConstants.SKI_KEY_IDENTIFIER);
ofc.setEncryptionUser(service);
ofc.getProperty();
return ofc;
}
public static InflowConfiguration getInflowConfiguration(){
InflowConfiguration ifc = new InflowConfiguration();
ifc.setActionItems(Timestamp Signature Encrypt);
ifc.setPasswordCallbackClass(client.PWCBHandler);
ifc.setSignaturePropFile(client1.properties);
ifc.getProperty();
return ifc;
}
Can anybody tell me what's the problem??? or tell me another way to
configure the client to encrypt certain messages???
Thanks a lot,
Jorge Fernández
__
LLama Gratis a cualquier PC del Mundo.
Llamadas a fijos y móviles desde 1 céntimo por minuto.
http://es.voice.yahoo.com
-
¡Descubre una nueva forma de obtener respuestas a tus preguntas!
Entra en Yahoo! Respuestas.
simple question about request scope
Hi, My question is: using request scope, ServiceGroupContext has the same life time as the invocation of the operation??? Do I have to use ConfigurationContext if I want to keep something in common to all service invocations or do I have another option??? Thanks in advance, Jorge Fernández - LLama Gratis a cualquier PC del Mundo. Llamadas a fijos y móviles desde 1 céntimo por minuto. http://es.voice.yahoo.com
rampart causes problems with hierarchies
Hi, Some months ago, I had some problems with the use of hierarchies with adb and xmlbeans. Apparently they were resolved with adb but know, I'm getting the same error. For example: I have an array of an object called parent and I put into that array instances of child1 or child2 (those inherit from parent). In the xml generated from that array should appear the xsi:type attribute but when I engage rampart module, that attribute dissapears. So maybe that was the cause of the problems I had before. See https://issues.apache.org/jira/browse/XMLBEANS-329 and https://issues.apache.org/jira/browse/AXIS2-2578. - ¡Descubre una nueva forma de obtener respuestas a tus preguntas! Entra en Yahoo! Respuestas.
Exception in rampart configuration with inflow - outflow classes
Hi,
For quite a long time I've been trying to configure a client that is invoking
some operations to encrypt just some of the messages. I have read in this page
that the rampart 1.0 configuration style could be use even though is marked as
deprecated.
http://ruchith.blogspot.com/2007/06/apache-rampart-12-released.html
So I tried to do it and I'm getting the following exception:
rg.apache.axis2.AxisFault: Configureation error
at
org.apache.rampart.handler.WSDoAllSender.processMessage(WSDoAllSender.java:94)
at org.apache.rampart.handler.WSDoAllHandler.invoke(WSDoAllHandler.java:72)
at org.apache.axis2.engine.Phase.invoke(Phase.java:383)
at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:203)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:433)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:330)
at
org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:294)
at
client.Medici_LinkSOAP12PortStub.validateSystem(Medici_LinkSOAP12PortStub.java:747)Validating
system ch4_001mu...
at client.ClientUtilities.validateSystemTest(ClientUtilities.java:73)
at client.Client.main(Client.java:33)
Caused by: org.apache.axis2.AxisFault: Configureation error
at
org.apache.rampart.handler.WSDoAllSender.processBasic(WSDoAllSender.java:151)
at
org.apache.rampart.handler.WSDoAllSender.processMessage(WSDoAllSender.java:88)
... 9 more
Caused by: java.lang.ClassCastException:
org.apache.rampart.handler.config.InflowConfiguration cannot be cast to
org.apache.axis2.description.Parameter
at
org.apache.rampart.util.HandlerParameterDecoder.processParameters(HandlerParameterDecoder.java:63)
at
org.apache.rampart.handler.WSDoAllSender.processBasic(WSDoAllSender.java:149)
... 10 more
I'm doing this:
stub._getServiceClient().getOptions().setProperty(WSSHandlerConstants.OUTFLOW_SECURITY,
ClientUtilities.getOutflowConfiguration());
stub._getServiceClient().getOptions().setProperty(WSSHandlerConstants.INFLOW_SECURITY,
ClientUtilities.getInflowConfiguration());
public static OutflowConfiguration getOutflowConfiguration(){
OutflowConfiguration ofc = new OutflowConfiguration();
ofc.setActionItems(Timestamp Signature Encrypt);
ofc.setUser(client1);
ofc.setPasswordCallbackClass(client.PWCBHandler);
ofc.setSignaturePropFile(client1.properties);
ofc.setSignatureKeyIdentifier(WSSHandlerConstants.BST_DIRECT_REFERENCE);
//ofc.setEncryptionKeyIdentifier(WSSHandlerConstants.SKI_KEY_IDENTIFIER);
ofc.setEncryptionUser(service);
ofc.getProperty();
return ofc;
}
public static InflowConfiguration getInflowConfiguration(){
InflowConfiguration ifc = new InflowConfiguration();
ifc.setActionItems(Timestamp Signature Encrypt);
ifc.setPasswordCallbackClass(client.PWCBHandler);
ifc.setSignaturePropFile(client1.properties);
ifc.getProperty();
return ifc;
}
Can anybody tell me what's the problem??? or tell me another way to configure
the client to encrypt certain messages???
Thanks a lot,
Jorge Fernández
-
LLama Gratis a cualquier PC del Mundo.
Llamadas a fijos y móviles desde 1 céntimo por minuto.
http://es.voice.yahoo.com
Re: ServiceGroupID
Any ideas on this?? Using SOAP sessin, If I call a method and it throws an exception, and just after that I call a second one I observe different behaviour depending on this second method. If the second method is the same as the first, Axis2 recognises that the session was opened. Buf if the second method is a different one, Axis2 opens a new SOAP session. I'm always using the same client and the same service. Thanks in advance, Jorge Fernández Jorge Fernandez [EMAIL PROTECTED] escribió: Hi Deepal, I was asking this because I'm trying to implement SOAP sessions using the service group id as an id for the session on my own and I'm having a strange behaviour. First my client validates, after that, ha can do any operation. If he receives a exception for any reason, he should be able to do the operation again or invoke another. I'm throwing exceptions when a non-logged user invokes an operation and when a user validates twice with the same session ID. When he invokes another operation, axis gives him another serviceGroupID, so the session is new and he receives an exception because he hasn't validated. But if he tries to validate again instead of that, he receives an exception telling that he was already validated. How is this possible?? What depends the generation of the service group id on??? Thanks, Jorge Fernández Deepal Jayasinghe [EMAIL PROTECTED] escribió: Hi Jorge , Nope you can not do so, the service group id will be send by the server after the first request. Thanks Deepal Hi! Can anybody tell me if it's possible to set the service group id from the client in a first call to a service??? Thanks in advandce, Jorge Fernández - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - LLama Gratis a cualquier PC del Mundo. Llamadas a fijos y móviles desde 1 céntimo por minuto. http://es.voice.yahoo.com - ¡Descubre una nueva forma de obtener respuestas a tus preguntas! Entra en Yahoo! Respuestas.
RE: ServiceGroupID
Hi Hailong,
Yes, what you say is true. I know that.
If I invoke different methods secuentially, I get the same ServiceGroupID but
my problem is: if I receive an exception from one of them and I try to invoke
another method after that, depending on which method is this, I receive the
same ServiceGroupID or a different one and I don't know why.
Thanks
Jorge Fernández
Wang, Hailong (NIH/CIT) [C] [EMAIL PROTECTED] escribió:v\:*
{behavior:url(#default#VML);} o\:* {behavior:url(#default#VML);} w\:*
{behavior:url(#default#VML);} .shape {behavior:url(#default#VML);}
ServiceGroupID is used as a SessionID. So same ServiceGroupID means same
session.
Hailong
-
From: Jorge Fernandez [mailto:[EMAIL PROTECTED]
Sent: Monday, July 02, 2007 4:53 PM
To: axis-user
Subject: Re: ServiceGroupID
Any ideas on this??
Using SOAP sessin, If I call a method and it throws an exception, and just
after that I call a second one I observe different behaviour depending on this
second method.
If the second method is the same as the first, Axis2 recognises that the
session was opened. Buf if the second method is a different one, Axis2 opens a
new SOAP session.
I'm always using the same client and the same service.
Thanks in advance,
Jorge Fernández
Jorge Fernandez [EMAIL PROTECTED] escribió:
Hi Deepal,
I was asking this because I'm trying to implement SOAP sessions using the
service group id as an id for the session on my own and I'm having a strange
behaviour.
First my client validates, after that, ha can do any operation. If he receives
a exception for any reason, he should be able to do the operation again or
invoke another.
I'm throwing exceptions when a non-logged user invokes an operation and when a
user validates twice with the same session ID.
When he invokes another operation, axis gives him another serviceGroupID, so
the session is new and he receives an exception because he hasn't validated.
But if he tries to validate again instead of that, he receives an exception
telling that he was already validated.
How is this possible?? What depends the generation of the service group id
on???
Thanks,
Jorge Fernández
Deepal Jayasinghe [EMAIL PROTECTED] escribió:
Hi Jorge ,
Nope you can not do so, the service group id will be send by the server
after the first request.
Thanks
Deepal
Hi!
Can anybody tell me if it's possible to set the service group id from
the client in a first call to a service???
Thanks in advandce,
Jorge Fernández
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
LLama Gratis a cualquier PC del Mundo.
Llamadas a fijos y móviles desde 1 céntimo por minuto.
http://es.voice.yahoo.com
-
¡Descubre una nueva forma de obtener respuestas a tus preguntas!
Entra en Yahoo! Respuestas.
-
LLama Gratis a cualquier PC del Mundo.
Llamadas a fijos y móviles desde 1 céntimo por minuto.
http://es.voice.yahoo.com
RE: axis2 -- duplicate elements in wsdl when multiple methods throw same Exception/faults
Hi Shiv, The wsdl duplicating faults is a known issue. Please look at: https://issues.apache.org/jira/browse/AXIS2-2325. Regards, Jorge Fernández Shiv [EMAIL PROTECTED] escribió: In the pojo example (under axis2 samples), I added a new class AddressException that extends AxisFault, and modified AddressBookService.java so that both the methods thow AddressBookException. public void addEntry(Entry entry) throws AddressException public Entry[] findEntry(String name) throws AddressException The AddressException.java is a simple class that just extends AxisFault. public class AddressException extends AxisFault The wsdl generated from the above implementation has duplicate element AddressExceptionFault (I used ant generate.service) Running the client program (adb version also gives problems). If the 'throws' is removed from the methods, the wsdl looks ok and the client program runs fine. Our product code has 'throws AxisFault' in every method and this worked fine with axis 1.4. Axis 2 has broken all of this. Even having an exception class that derives from java.lang.Exception does not help (it also results in duplicate elements in wsdl). ant adb.client -D=http://localhost:8804/axis2/services/AddressBookService?wsdl C:\axis\axis2-1.2\samples\pojoant adb.client -D=http://localhost:8804/axis2/ser vices/AddressBookService?wsdl Buildfile: build.xml check-parameters: print-usage: adb.client: clean: [delete] Deleting directory C:\axis\axis2-1.2\samples\pojo\build [delete] DEPRECATED - Use of the implicit FileSet is deprecated. Use a neste d fileset element instead. prepare: [mkdir] Created dir: C:\axis\axis2-1.2\samples\pojo\build [mkdir] Created dir: C:\axis\axis2-1.2\samples\pojo\build\classes [mkdir] Created dir: C:\axis\axis2-1.2\samples\pojo\build\lib [mkdir] Created dir: C:\axis\axis2-1.2\samples\pojo\build\classes\META-INF adb.client.codegen-stub: [java] Jun 28, 2007 2:58:43 PM org.apache.axis2.wsdl.codegen.writer.ClassWr iter createOutFile [java] INFO: The src\sample\addressbook\stub\AddEntryFaultException.java fi le cannot be overwritten. [java] Jun 28, 2007 2:58:44 PM org.apache.axis2.wsdl.codegen.writer.ClassWr iter createOutFile [java] INFO: The src\sample\addressbook\stub\AddEntryFaultException.java fi le cannot be overwritten. adb.client.compile: [javac] Compiling 8 source files to C:\axis\axis2-1.2\samples\pojo\build\cla sses adb.client.jar: [jar] Building jar: C:\axis\axis2-1.2\samples\pojo\build\lib\adb-client.ja r adb.client.run: [java] org.apache.axis2.AxisFault: Message Receiver not found for AxisOpera tion: addEntry [java] at org.apache.axis2.util.Utils.getInboundFaultFromMessageContext (Utils.java:434) [java] at org.apache.axis2.description.RobustOutOnlyAxisOperation$Robus tOutOnlyOperationClient.send(RobustOutOnlyAxisOperation.java:108) [java] at org.apache.axis2.description.OutInAxisOperationClient.execute (OutInAxisOperation.java:294) [java] at sample.addressbook.stub.AddressBookServiceAddressBookServiceS OAP11Port_httpStub.addEntry(Unknown Source) [java] at sample.addressbook.adbclient.AddressBookADBClient.main(Unknow n Source) [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [java] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcces sorImpl.java:39) [java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMet hodAccessorImpl.java:25) [java] at java.lang.reflect.Method.invoke(Method.java:324) [java] at org.apache.tools.ant.taskdefs.ExecuteJava.run(ExecuteJava.jav a:193) [java] at org.apache.tools.ant.taskdefs.ExecuteJava.execute(ExecuteJava .java:130) [java] at org.apache.tools.ant.taskdefs.Java.run(Java.java:705) [java] at org.apache.tools.ant.taskdefs.Java.executeJava(Java.java:177) [java] at org.apache.tools.ant.taskdefs.Java.execute(Java.java:83) [java] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.ja va:275) [java] at org.apache.tools.ant.Task.perform(Task.java:364) [java] at org.apache.tools.ant.Target.execute(Target.java:341) [java] at org.apache.tools.ant.Target.performTasks(Target.java:369) [java] at org.apache.tools.ant.Project.executeTarget(Project.java:1214) [java] at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:386) [java] at org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget.j ava:106) [java] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.ja va:275) [java] at org.apache.tools.ant.Task.perform(Task.java:364) [java] at org.apache.tools.ant.Target.execute(Target.java:341) [java] at org.apache.tools.ant.Target.performTasks(Target.java:369) [java] at
ServiceGroupID
Hi! Can anybody tell me if it's possible to set the service group id from the client in a first call to a service??? Thanks in advandce, Jorge Fernández - ¡Descubre una nueva forma de obtener respuestas a tus preguntas! Entra en Yahoo! Respuestas.
Re: ServiceGroupID
Hi Deepal, I was asking this because I'm trying to implement SOAP sessions using the service group id as an id for the session on my own and I'm having a strange behaviour. First my client validates, after that, ha can do any operation. If he receives a exception for any reason, he should be able to do the operation again or invoke another. I'm throwing exceptions when a non-logged user invokes an operation and when a user validates twice with the same session ID. When he invokes another operation, axis gives him another serviceGroupID, so the session is new and he receives an exception because he hasn't validated. But if he tries to validate again instead of that, he receives an exception telling that he was already validated. How is this possible?? What depends the generation of the service group id on??? Thanks, Jorge Fernández Deepal Jayasinghe [EMAIL PROTECTED] escribió: Hi Jorge , Nope you can not do so, the service group id will be send by the server after the first request. Thanks Deepal Hi! Can anybody tell me if it's possible to set the service group id from the client in a first call to a service??? Thanks in advandce, Jorge Fernández - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - LLama Gratis a cualquier PC del Mundo. Llamadas a fijos y móviles desde 1 céntimo por minuto. http://es.voice.yahoo.com
Sessions
Hi, Has axis2 any timeout managing similar as the client, when is used at the server side? I tried with SessionContext but I couldn't get it working. Thanks and regards, Jorge Fernández - ¡Descubre una nueva forma de obtener respuestas a tus preguntas! Entra en Yahoo! Respuestas.
HTTP/1.1 400 Bad Request
Hi again, I was trying to get some information on this problem but I couldn't know what is happening so I'm trying again. Does anybody know anything about how can I fix this??? Thanks a lot, Jorge Fernández Jorge Fernandez [EMAIL PROTECTED] escribió: Hi all, I'm having problems only when throwing exceptions. I'm getting bad request. This problem appeared since I moved to axis2 1.2, using it with Tomcat. If I use axis as standalone server there's no problem. The messages are apparently the same except for some minimal changes in the order of HTTP header, the prefix for the description element namespace and that the final character after envelope in one case appears in the following line. This are the messages: The correct one with standalone axis: HTTP/1.1 500 Internal server error Date: Wed, 13 Jun 2007 08:22:37 GMT Content-Type: application/soap+xml; action=http://medici_link/Medici_LinkPortType/validateUser/Fault/ValidationFault; Server: Simple-Server/1.1 Transfer-Encoding: chunked Connection: Close 3a2 ?xml version='1.0' encoding='UTF-8'? soapenv:Envelope xmlns:wsa=http://www.w3.org/2005/08/addressing; xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope; soapenv:Header wsa:Actionhttp://medici_link/Medici_LinkPortType/validateUser/Fault/ValidationFault/wsa:Action wsa:RelatesTourn:uuid:B2AFE74A4124DE7BFF1181722957402/wsa:RelatesTo /soapenv:Header soapenv:Body soapenv:Fault soapenv:Code soapenv:Valuesoapenv:Sender/soapenv:Value /soapenv:Code soapenv:Reason soapenv:Text xml:lang=en-USValidationFaultException/soapenv:Text /soapenv:Reason soapenv:Detail ns4:ValidationException xmlns:ns4=http://op_messages.medici_link/xsd; ns4:ValidationFault s2:description xmlns:s2=http://faults.medici_link/xsd;User not validated. You must validate before invoking a method./s2:description /ns4:ValidationFault /ns4:ValidationException /soapenv:Detail /soapenv:Fault /soapenv:Body /soapenv:Envelope0 The bad one with tomcat: HTTP/1.1 400 Petición incorrecta Server: Apache-Coyote/1.1 Content-Type: application/soap+xml; action=http://medici_link/Medici_LinkPortType/validateUser/Fault/ValidationFault;charset=UTF-8 Transfer-Encoding: chunked Date: Wed, 13 Jun 2007 08:12:50 GMT Connection: close 3a2 ?xml version='1.0' encoding='UTF-8'? soapenv:Envelope xmlns:wsa=http://www.w3.org/2005/08/addressing; xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope; soapenv:Header wsa:Actionhttp://medici_link/Medici_LinkPortType/validateUser/Fault/ValidationFault/wsa:Action wsa:RelatesTourn:uuid:61931C3AAB6FF83F181181722371001/wsa:RelatesTo /soapenv:Header soapenv:Body soapenv:Fault soapenv:Code soapenv:Valuesoapenv:Sender/soapenv:Value /soapenv:Code soapenv:Reason soapenv:Text xml:lang=en-USValidationFaultException/soapenv:Text /soapenv:Reason soapenv:Detail ns4:ValidationException xmlns:ns4=http://op_messages.medici_link/xsd; ns4:ValidationFault s1:description xmlns:s1=http://faults.medici_link/xsd;User not validated. You must validate before invoking a method./s1:description /ns4:ValidationFault /ns4:ValidationException /soapenv:Detail /soapenv:Fault /soapenv:Body /soapenv:Envelope 0 - LLama Gratis a cualquier PC del Mundo. Llamadas a fijos y móviles desde 1 céntimo por minuto. http://es.voice.yahoo.com - ¡Descubre una nueva forma de obtener respuestas a tus preguntas! Entra en Yahoo! Respuestas.
Re: HTTP/1.1 400 Bad Request
Hola Martin: I tried what you said but the problem is the same. Furthermore, those characters remain appearing even commenting every Transfer-Encoding parameter. I think that it's something related to Tomcat because the code 400 on HTTP header only appears when deploying Axis2 under Tomcat. Saludos y muchas gracias again, Jorge Fernandez Martin Gainty [EMAIL PROTECTED] escribió: undecipherable characters (specifically 3a2) is being introduced before the beginning xml tag which neither the servlet or the client stub can interpret I have seen this happen with Chunked encoding try to disable parameter name=Transfer-Encoding (commenting out the parameter name=Transfer-Encoding from axis2.xml) and re-deploy Saludos M-- This email message and any files transmitted with it contain confidential information intended only for the person(s) to whom this email message is addressed. If you have received this email message in error, please notify the sender immediately by telephone or email and destroy the original message without making a copy. Thank you. - Original Message - From:Jorge Fernandez To: axis-user@ws.apache.org Sent: Thursday, June 21, 2007 3:40PM Subject: HTTP/1.1 400 Bad Request Hi again, I was trying to get some information on thisproblem but I couldn't know what is happening so I'm trying again. Doesanybody know anything about how can I fix this??? Thanks alot, Jorge Fernández Jorge Fernandez [EMAIL PROTECTED]escribió: Hi all, I'm having problems only when throwing exceptions. I'm getting bad request. This problem appeared since I moved to axis2 1.2, using it with Tomcat. If I use axis as standalone server there's no problem. The messages are apparently the same except for some minimal changes in the order of HTTP header, the prefix for the description element namespace and that the final character after envelope in one case appears in the following line. This are the messages: The correct one with standalone axis: HTTP/1.1 500 Internal server error Date: Wed, 13 Jun 2007 08:22:37 GMT Content-Type: application/soap+xml; action=http://medici_link/Medici_LinkPortType/validateUser/Fault/ValidationFault; Server: Simple-Server/1.1 Transfer-Encoding: chunked Connection: Close 3a2 ?xml version='1.0' encoding='UTF-8'? soapenv:Envelope xmlns:wsa=http://www.w3.org/2005/08/addressing; xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope; soapenv:Header wsa:Actionhttp://medici_link/Medici_LinkPortType/validateUser/Fault/ValidationFault/wsa:Action wsa:RelatesTourn:uuid:B2AFE74A4124DE7BFF1181722957402/wsa:RelatesTo /soapenv:Header soapenv:Body soapenv:Fault soapenv:Code soapenv:Valuesoapenv:Sender/soapenv:Value /soapenv:Code soapenv:Reason soapenv:Text xml:lang=en-USValidationFaultException/soapenv:Text /soapenv:Reason soapenv:Detail ns4:ValidationException xmlns:ns4=http://op_messages.medici_link/xsd; ns4:ValidationFault s2:description xmlns:s2=http://faults.medici_link/xsd;User not validated. You must validate before invoking a method./s2:description /ns4:ValidationFault /ns4:ValidationException /soapenv:Detail /soapenv:Fault /soapenv:Body /soapenv:Envelope0 The bad one with tomcat: HTTP/1.1 400 Petición incorrecta Server: Apache-Coyote/1.1 Content-Type: application/soap+xml; action=http://medici_link/Medici_LinkPortType/validateUser/Fault/ValidationFault;charset=UTF-8 Transfer-Encoding: chunked Date: Wed, 13 Jun 2007 08:12:50 GMT Connection: close 3a2 ?xml version='1.0' encoding='UTF-8'? soapenv:Envelope xmlns:wsa=http://www.w3.org/2005/08/addressing; xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope; soapenv:Header wsa:Actionhttp://medici_link/Medici_LinkPortType/validateUser/Fault/ValidationFault/wsa:Action wsa:RelatesTourn:uuid:61931C3AAB6FF83F181181722371001/wsa:RelatesTo /soapenv:Header soapenv:Body soapenv:Fault soapenv:Code soapenv:Valuesoapenv:Sender/soapenv:Value /soapenv:Code soapenv:Reason soapenv:Text xml:lang=en-USValidationFaultException/soapenv:Text /soapenv:Reason soapenv:Detail ns4:ValidationException xmlns:ns4=http://op_messages.medici_link/xsd; ns4:ValidationFault s1:description xmlns:s1
HTTP/1.1 400 Petición incorrecta
Hi all, I'm having problems only when throwing exceptions. I'm getting bad request. This problem appeared since I moved to axis2 1.2, using it with Tomcat. If I use axis as standalone server there's no problem. The messages are apparently the same except for some minimal changes in the order of HTTP header, the prefix for the description element namespace and that the final character after envelope in one case appears in the following line. This are the messages: The correct one with standalone axis: HTTP/1.1 500 Internal server error Date: Wed, 13 Jun 2007 08:22:37 GMT Content-Type: application/soap+xml; action=http://medici_link/Medici_LinkPortType/validateUser/Fault/ValidationFault; Server: Simple-Server/1.1 Transfer-Encoding: chunked Connection: Close 3a2 ?xml version='1.0' encoding='UTF-8'? soapenv:Envelope xmlns:wsa=http://www.w3.org/2005/08/addressing; xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope; soapenv:Header wsa:Actionhttp://medici_link/Medici_LinkPortType/validateUser/Fault/ValidationFault/wsa:Action wsa:RelatesTourn:uuid:B2AFE74A4124DE7BFF1181722957402/wsa:RelatesTo /soapenv:Header soapenv:Body soapenv:Fault soapenv:Code soapenv:Valuesoapenv:Sender/soapenv:Value /soapenv:Code soapenv:Reason soapenv:Text xml:lang=en-USValidationFaultException/soapenv:Text /soapenv:Reason soapenv:Detail ns4:ValidationException xmlns:ns4=http://op_messages.medici_link/xsd; ns4:ValidationFault s2:description xmlns:s2=http://faults.medici_link/xsd;User not validated. You must validate before invoking a method./s2:description /ns4:ValidationFault /ns4:ValidationException /soapenv:Detail /soapenv:Fault /soapenv:Body /soapenv:Envelope0 The bad one with tomcat: HTTP/1.1 400 Petición incorrecta Server: Apache-Coyote/1.1 Content-Type: application/soap+xml; action=http://medici_link/Medici_LinkPortType/validateUser/Fault/ValidationFault;charset=UTF-8 Transfer-Encoding: chunked Date: Wed, 13 Jun 2007 08:12:50 GMT Connection: close 3a2 ?xml version='1.0' encoding='UTF-8'? soapenv:Envelope xmlns:wsa=http://www.w3.org/2005/08/addressing; xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope; soapenv:Header wsa:Actionhttp://medici_link/Medici_LinkPortType/validateUser/Fault/ValidationFault/wsa:Action wsa:RelatesTourn:uuid:61931C3AAB6FF83F181181722371001/wsa:RelatesTo /soapenv:Header soapenv:Body soapenv:Fault soapenv:Code soapenv:Valuesoapenv:Sender/soapenv:Value /soapenv:Code soapenv:Reason soapenv:Text xml:lang=en-USValidationFaultException/soapenv:Text /soapenv:Reason soapenv:Detail ns4:ValidationException xmlns:ns4=http://op_messages.medici_link/xsd; ns4:ValidationFault s1:description xmlns:s1=http://faults.medici_link/xsd;User not validated. You must validate before invoking a method./s1:description /ns4:ValidationFault /ns4:ValidationException /soapenv:Detail /soapenv:Fault /soapenv:Body /soapenv:Envelope 0 - LLama Gratis a cualquier PC del Mundo. Llamadas a fijos y móviles desde 1 céntimo por minuto. http://es.voice.yahoo.com
URGENT Help with sessions
Hi, Few days ago I wrote a message to ask some questions about sessions. I'm stuck on that because I'm lost in how should I implement my session managing. I can't find any detailed example or tutorial that could show me which one is the best for me, how they work in detail, and how to use contexts for that. Now, I'm near the desperation because I'm on the edge to present my final project to graduate so any kind of information would be VERY appreciated. This are my questions: At this moment I'm using SOAP session scope. I have to validate a system and then an user (sometimes only a system) so I have an operation for each. Any user should invoke both at the first time but I can't force that happening, can I? Can I specify the order in which operations should be called? What I'm doing at the moment is throw an exception if the client invoke an operation and didn't validate but my understanding is that by the time I do that, Axis2 has created a session. I would like to avoid that because I would that my session would last about 5 minutes and I don't want to keep one session open for such a long time each time a client invokes an operation. The second thing I want to do is establish my timeout. I tried modifying the parameter ConfigContextTimeoutInterval from the axis configuration file but apparently it didn't work. I tested it with a value 30 miliseconds calling two operations sequencially from the same client and adding a big delay between them. But the group session id was the same. Is this the way it's supposed to work? Do I have to do something to catch the timeout event and then call destroy? Also I want to stop my timer when my client is inside an operation. Does Axis2 do that?? About the session information to keep at the service, my understanding is that I should use the properties of the ServiceContext (so it can be accessed from all instances of the service) or the properties of SessionContext (for keeping it local to the instance). Am I right? How can I delete that information in the former case when the session ends?? The last question is: the first time a client calls any operation, the ServiceGroupID is generated. When is that happening? I would like to store that session id at my service with my session information. Thanks a lot, Jorge Fernández - LLama Gratis a cualquier PC del Mundo. Llamadas a fijos y móviles desde 1 céntimo por minuto. http://es.voice.yahoo.com
Session duration
Hi, I would like to know If axis2 has any timeout managing similar as the client, when is used at the server side. And if it does, does it call the destroy method when having a timeout?? And also another question: I'm using soap session and I know that when my client calls my service for the first time, a ServiceGroupID is generated and sent to the client so he can use it as a identifier for the sesion. I was wondering if I could get that ServiceGroupID at the time the client makes the first call. Thanks and regards, Jorge Fernández - ¡Descubre una nueva forma de obtener respuestas a tus preguntas! Entra en Yahoo! Respuestas.
RE: [Axis2] Re: XMLBeans, Attachments and Rampart
Hi Dennis, Thanks for the information. I wonder if there is a limit on the size of attachments only when I want to encrypt them because in some cases I don't need to do it and AFAIK, with rampart you can choose which parts you want to encrypt. A question for Thilina: When a client invokes a method from my Axis2 Web Service and the response message is going to be very big, so I use http chunking: Does axis build all the message at once in memory and then break it pieces?? I possible to build each part in memory and send it, release memory and build - send the next one?? I'm having some memory issues after invoking some methods that build big messages. I'm using Axis2 under Tomcat and the memory size ot Tomcat increases from 50 MB to 300 MB and I didn't see it decreasing. Thanks and regards, Jorge Fernández Dennis Sosnoski [EMAIL PROTECTED] escribió: Hi Jorge, I haven't verified Rampart handling of attachments, but based on what I've seen in other cases I suspect it will build an in-memory representation of the entire document (including attachments, as embedded base64 text) any time Rampart is engaged for a service. This should really only be necessary when you're signing or encrypting the body, but in my trials Rampart built the in-memory tree even when just adding timestamps. The reason why the attachments need to be part of the tree goes back to the design of XOP/MTOM and WS-Security. Attachments using XOP/MTOM are treated just as if they were embedded directly in the XML document, using base64 encoding - MTOM is *only* a transport level optimization. This means that when you use WS-Security you need to have a view of the document with the attachments present as the base64 strings. AFAIK there's no way around this issue, since it was by design. It would be possible in theory for the WS-Security implementation to be smart about handling attachments, and basically just generate a streaming version of the base64 representation for the attachment data as needed when signing (digesting, actually) or encrypting. But this would require changes all the way down to the underlying XML Signature and XML Encryption implementations, and I'd suspect such changes are unlikely to occur without a lot of user demand. In the meantime, I suspect the practical limit for attachment size with Rampart engaged will be somewhere in the 10 MB range. - Dennis Dennis M. Sosnoski SOA and Web Services in Java Training and Consulting http://www.sosnoski.com - http://www.sosnoski.co.nz Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117 Jorge Fernandez wrote: Hi again, I didn't have answer for my question. So I'll try again. My problem is that I was using XMLBeans for my project. But XMLBeans doesn't support MTOM. So I tried to use ADB but I have some problems with the mapping of my objects to xml so I would like keep using XMLBeans. Also I want to secure my message also and I found that Rampart and MTOM have memory problems. This are my questions: - When I used ADB and MTOM I could see that if I don't enable MTOM, the attachment is sent in binary code as a String inside de SOAP message but if I enable MTOM, it's send outside the message in clear text (I used an xml file as example of attachment). I would like to send the attachment outside the message in binary code. Is this possible?? - I know that MTOM is better than SwA, but what are the reasons? - Is there any limit in the size of messages that axis2 can send, I mean in both the envelope and as attachments?? I'll have to send huge arrays of int or other data. I'll have to send some of them as attachments to avoid the multiple tags the xml would generate. - The last one: As I'm building big messages, I'm having memory problems and I would like to know if axis can build this messages in parts, like build the first part of the message when it reach a limit size and send it, then build another one and send it.. Any help will be appreciated. Thanks in advance, Jorge Fernández */Jorge Fernandez /* escribió: Hi all, I would like to know if it's possible to use XMLBeans and Rampart with attachtments cos I heard that XMLBeans doesn't support MTOM and I doubt if Rampart supports SwA or there is any problem in that combination. Thanks and regards, Jorge Fernández LLama Gratis a cualquier PC del Mundo. Llamadas a fijos y móviles desde 1 céntimo por minuto. http://es.voice.yahoo.com LLama Gratis a cualquier PC del Mundo. Llamadas a fijos y móviles desde 1 céntimo por minuto. http://es.voice.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail
RE: [Axis2] Re: XMLBeans, Attachments and Rampart
Also the last thing I would like to know is how can I transfer a short array because in the xml it generates lots of tags so I thought of sending it as an attachment but I think that I have to transform it to I byte array, am I right? Is it possible to transfer it as an attachment without having to transform it?? Jorge Fernandez [EMAIL PROTECTED] escribió: Hi Dennis, Thanks for the information. I wonder if there is a limit on the size of attachments only when I want to encrypt them because in some cases I don't need to do it and AFAIK, with rampart you can choose which parts you want to encrypt. A question for Thilina: When a client invokes a method from my Axis2 Web Service and the response message is going to be very big, so I use http chunking: Does axis build all the message at once in memory and then break it pieces?? I possible to build each part in memory and send it, release memory and build - send the next one?? I'm having some memory issues after invoking some methods that build big messages. I'm using Axis2 under Tomcat and the memory size ot Tomcat increases from 50 MB to 300 MB and I didn't see it decreasing. Thanks and regards, Jorge Fernández Dennis Sosnoski [EMAIL PROTECTED] escribió: Hi Jorge, I haven't verified Rampart handling of attachments, but based on what I've seen in other cases I suspect it will build an in-memory representation of the entire document (including attachments, as embedded base64 text) any time Rampart is engaged for a service. This should really only be necessary when you're signing or encrypting the body, but in my trials Rampart built the in-memory tree even when just adding timestamps. The reason why the attachments need to be part of the tree goes back to the design of XOP/MTOM and WS-Security. Attachments using XOP/MTOM are treated just as if they were embedded directly in the XML document, using base64 encoding - MTOM is *only* a transport level optimization. This means that when you use WS-Security you need to have a view of the document with the attachments present as the base64 strings. AFAIK there's no way around this issue, since it was by design. It would be possible in theory for the WS-Security implementation to be smart about handling attachments, and basically just generate a streaming version of the base64 representation for the attachment data as needed when signing (digesting, actually) or encrypting. But this would require changes all the way down to the underlying XML Signature and XML Encryption implementations, and I'd suspect such changes are unlikely to occur without a lot of user demand. In the meantime, I suspect the practical limit for attachment size with Rampart engaged will be somewhere in the 10 MB range. - Dennis Dennis M. Sosnoski SOA and Web Services in Java Training and Consulting http://www.sosnoski.com - http://www.sosnoski.co.nz Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117 Jorge Fernandez wrote: Hi again, I didn't have answer for my question. So I'll try again. My problem is that I was using XMLBeans for my project. But XMLBeans doesn't support MTOM. So I tried to use ADB but I have some problems with the mapping of my objects to xml so I would like keep using XMLBeans. Also I want to secure my message also and I found that Rampart and MTOM have memory problems. This are my questions: - When I used ADB and MTOM I could see that if I don't enable MTOM, the attachment is sent in binary code as a String inside de SOAP message but if I enable MTOM, it's send outside the message in clear text (I used an xml file as example of attachment). I would like to send the attachment outside the message in binary code. Is this possible?? - I know that MTOM is better than SwA, but what are the reasons? - Is there any limit in the size of messages that axis2 can send, I mean in both the envelope and as attachments?? I'll have to send huge arrays of int or other data. I'll have to send some of them as attachments to avoid the multiple tags the xml would generate. - The last one: As I'm building big messages, I'm having memory problems and I would like to know if axis can build this messages in parts, like build the first part of the message when it reach a limit size and send it, then build another one and send it.. Any help will be appreciated. Thanks in advance, Jorge Fernández */Jorge Fernandez /* escribió: Hi all, I would like to know if it's possible to use XMLBeans and Rampart with attachtments cos I heard that XMLBeans doesn't support MTOM and I doubt if Rampart supports SwA or there is any problem in that combination. Thanks and regards, Jorge Fernández LLama Gratis a cualquier PC del Mundo. Llamadas a fijos y móviles desde 1 céntimo por minuto. http
Re: Issue with ADB and parsing a response message (namespaces)
I had a look at the JIRA. 'll try to do it. Thanks Amila Suriarachchi [EMAIL PROTECTED] escribió: earlier I have tested the adb server with adb client. but for xmlbeans server with adb client problem still exits. see my comment on the https://issues.apache.org/jira/browse/AXIS2-2578 On 4/28/07, Jorge Fernandez [EMAIL PROTECTED] wrote: Hi again Amila, I've just downloaded and installed axis2 1.2. I built again the project from my wsdl and still get the same problem. Thanks and Regards, Jorge Fernández Jorge Fernandez [EMAIL PROTECTED] escribió:In my test I was using axiom 1.2.4 and I had the same problem as with 1.2.2 Amila Suriarachchi [EMAIL PROTECTED] escribió: I ran your code with the branch code and the axiom-SNAPSHOT and it works fine. So the problem is with the axiom 1.2.2 you have to use the 1.2.4 Please try with the next RC. On 4/24/07, Jorge Fernandez [EMAIL PROTECTED] wrote: Hi Amila, I tried again without the addressing module and I had the same exception I was having with axiom 1.2.2. Regards, Jorge Fernández Rodríguez Amila Suriarachchi [EMAIL PROTECTED] escribió: On 4/23/07, Jorge Fernandez [EMAIL PROTECTED] wrote: Sorry, I don't know what you mean. I think you use the Axis2-1.2-RC2 release. In that release you have a lib directory which contain axiom 1.2.3 jars. (i.e. axiom-api-1.2.3.jar, axiom-impl-1.2.3.jar ,axiom-dom-1.2.3.jar). Get the Axiom 1.2.4 release from here http://ws.apache.org/commons/axiom/download.cgi and replace the 1.2.3 jars with the 1.2.4 jars. It seems that now you are getting some addressing problem. So please check it without addressing. Regards, Jorge Fernández Martin Gainty [EMAIL PROTECTED] escribió: Jorge I cannot display the url for your first namespace http://external.communication_data_model.medici_link/xsd M-- This email message and any files transmitted with it contain confidential information intended only for the person(s) to whom this email message is addressed. If you have received this email message in error, please notify the sender immediately by telephone or email and destroy the original message without making a copy. Thank you. - Original Message - From: Jorge Fernandez To: axis-user@ws.apache.org ; [EMAIL PROTECTED] Sent: Sunday, April 22, 2007 8:40 PM Subject: Re: Issue with ADB and parsing a response message (namespaces) Hi, I couldn't reproduce the error again. If you want I can open a JIRA but I can't attach any code. I had found another problem related with ADB parsing when there is some hierarchy and I raised JIRA 2578. Regards, Jorge Fernández Anne Thomas Manes [EMAIL PROTECTED] escribió: Please file a JIRA. On 4/20/07, Jorge Fernandez wrote: Hi all, I'm having problems with the namespaces of a response message like this: xmlns:ns3= http://op_messages.medici_link/xsd; xmlns:ns0= http://external.communication_data_model.medici_link/xsd xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance xsi:type=ns0:extConfiguration .. xsi:type=ns0:extAbstractParameterDesc .. .. xsi:type=ns0:extPrimitiveParameterDesc . .. I have this exception when parsing the first element (ns0:abstractParameters): java.lang.RuntimeException: java.lang.RuntimeException : Unsupported type null extPrimitiveParameterDesc at client.Medici_LinkStub.fromOM(Medici_LinkStub.java:5210) at client.Medici_LinkStub.getDetailedMonitoringStages(Medici_LinkStub.java:1945) at client.ClientUtilities.getDetailedMonitoringStagesTest (ClientUtilities.java:244) at client.Client.main (Client.java:53) Caused by: java.lang.RuntimeException: Unsupported type null extPrimitiveParameterDesc at medici_link.op_messages.xsd.ExtensionMapper.getTypeObject(ExtensionMapperjava:181) at medici_link.communication_data_model.external.xsd.ExtParameterDesc$Factory.parse(ExtParameterDesc.java:1171) at medici_link.communication_data_model.external.xsd.ExtAbstractParameterDesc$Factory.parse( ExtAbstractParameterDesc.java:1311) at medici_link.communication_data_model.external.xsd.ExtConfiguration$Factory.parse( ExtConfiguration.java:923) at medici_link.communication_data_model.external.xsd.ExtStage$Factory.parse(ExtStage.java:650) at medici_link.op_messages.xsd.GetDetailedMonitoringStagesResponse$Factory.parse( GetDetailedMonitoringStagesResponse.java :424) at client.Medici_LinkStub.fromOM(Medici_LinkStub.java:4833) .. 3 more I have a hierachy of classes: ExtAbstractParameterDesc and ExtPrimitiveParameterDesc that extend ExtParameterDesc. I've been diving in my code that was created with WSDL2Java and ADB (Axis 1.1.1) and I could see that for that element, it enters the parse Method of ExtAbstractParameterDesc, then it reaches
Re: Help with SwA
I attach the response message
Thilina Gunarathne [EMAIL PROTECTED] escribió: Messsage traces please..:)
On 5/1/07, Jorge Fernandez wrote:
Hi Thilina,
You were right. The problem was in TCPMon. Without using TCPMon, I don't
even have the problem sending big files. Thanks a lot.
I have one more question now that this problem was fixed: Is there any
sample of MOTM or SwA where the attachment is not a file?? I have to send
large arrays, for example of short and sending them in xml increases the
size of the message as it has to generate the tags for each element. So I
would like to send them as attachments.
Could anyone tell me how can I do it?
I was given some advise and I'm trying to convert the array of short in a
byte array doing this. I would appreciate some help on this:
short[] data=new short[100];
for (short i=0;i
data[i]=i;
byte[] byte_data = new byte[data.length * 2];
for(int i=0; i data.length; i++){
byte_data[2*i] = (byte) ((data[i] 8) 0xFF);
byte_data[2*i + 1] = (byte) ((data[i] 0) 0xFF);
}
// Populating the code generated beans
GetAttachmentResponse response=new GetAttachmentResponse();
DataHandler dataHandler = new
DataHandler(byte_data,application/octet-stream);
BinaryData binaryData =new BinaryData();
binaryData.setBase64Binary(dataHandler);
binaryData.setContentType(dataHandler.getContentType());
response.setBinaryData(binaryData);
The problem is in the method toEnvelope setting the child for the body.
I'm getting the following exception:
java.lang.RuntimeException: org.apache.axiom.om.OMException: Referenced
Attachment not found in the MIME Message.
ContentID:1.urn:uuid:[EMAIL PROTECTED]
at
client.Medici_LinkSOAP12PortStub.fromOM(Medici_LinkSOAP12PortStub.java:5296)
at
client.Medici_LinkSOAP12PortStub.getAttachment(Medici_LinkSOAP12PortStub.java:4103)
at client.ClientUtilities.mtomTest(ClientUtilities.java:476)
at client.Client.main(Client.java:69)
Caused by: org.apache.axiom.om.OMException: Referenced Attachment not found
in the MIME Message.
ContentID:1.urn:uuid:[EMAIL PROTECTED]
at
org.apache.axiom.soap.impl.builder.MTOMStAXSOAPModelBuilder.getDataHandler(MTOMStAXSOAPModelBuilder.java:103)
at
medici_link.xmime.xsd.BinaryData$Factory.parse(BinaryData.java:429)
at
medici_link.op_messages.xsd.GetAttachmentResponse$Factory.parse(GetAttachmentResponse.java:342)
at
client.Medici_LinkSOAP12PortStub.fromOM(Medici_LinkSOAP12PortStub.java:5024)
... 3 more
And with TCPMon I can see the fault as an attachment.
Thanks and regards,
Jorge Fernández
--
Thilina Gunarathne - http://www.wso2.com - http://thilinag.blogspot.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
LLama Gratis a cualquier PC del Mundo.
Llamadas a fijos y móviles desde 1 céntimo por minuto.
http://es.voice.yahoo.comHTTP/1.1 200 OK
Server: Apache-Coyote/1.1
Content-Type: multipart/related;
boundary=MIMEBoundaryurn_uuid_3B82B5DA59C7F75D1E1178016055344;
type=application/xop+xml; start=0.urn:uuid:[EMAIL PROTECTED];
start-info=application/soap+xml;
action=urn:getAttachment;charset=UTF-8Transfer-Encoding: chunkedDate: Tue, 01
May 2007 10:40:54
GMT516--MIMEBoundaryurn_uuid_3B82B5DA59C7F75D1E1178016055344Content-Type:
application/xop+xml; charset=UTF-8;
type=application/soap+xmlContent-Transfer-Encoding: binaryContent-ID:
0.urn:uuid:[EMAIL PROTECTED]
?xml version='1.0' encoding='UTF-8'?
soapenv:Envelope xmlns:wsa=http://www.w3.org/2005/08/addressing;
xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope;
soapenv:Header
wsa:ReplyTo
wsa:Addresshttp://www.w3.org/2005/08/addressing/none/wsa:Address
wsa:ReferenceParameters
axis2:ServiceGroupId
xmlns:axis2=http://ws.apache.org/namespaces/axis2;urn:uuid:3B82B5DA59C7F75D1E1178016053150/axis2:ServiceGroupId
/wsa:ReferenceParameters
/wsa:ReplyTo
wsa:MessageIDurn:uuid:3B82B5DA59C7F75D1E1178016055296/wsa:MessageID
wsa:Actionurn:getAttachment/wsa:Action
wsa:RelatesTourn:uuid:B5AEE5ABDE83138F781178016055102/wsa:RelatesTo
/soapenv:Header
soapenv:Body
ns3:getAttachmentResponse
xmlns:ns3=http://op_messages.medici_link/xsd;
ns3:binaryData xmlns:s1=http://www.w3.org/2005/05/xmlmime;
s1:contentType=application/octet-stream
xop:Include href=cid:1.urn:uuid:[EMAIL PROTECTED]
xmlns:xop=http://www.w3.org/2004/08/xop/include; /
/ns3:binaryData
/ns3:getAttachmentResponse
/soapenv:Body
RE: issue when sending big arrays
Hi,
I found the problem. TCPMon had an exception when trying to resend the
message. It shall have a limitation on the size of messages.
Thanks and Regards,
Jorge Fernández
Jorge Fernandez [EMAIL PROTECTED] escribió: Hi Valerie,
Thanks for your help but my problem is in the service because the response
message seems to be built correctly but at certain moment, there is an
exception and this message is not sent to the client. I use TCPMon and what the
service sends to the client is only the HTTP Header:
HTTP/1.1 200 OK
Server: Apache-Coyote/1.1
Content-Type: application/soap+xml;charset=UTF-8
Transfer-Encoding: chunked
Date: Fri,20 Apr 2007 14:50:37 GMT
102d
Maybe If I resolve this problem I'll need that sentence in my client. So thank
you again.
Regards,
Jorge Fernández
Masin, Valerie [EMAIL PROTECTED] escribió: I have no idea if this helps
but we had trouble with large docs using Sun Webserver and the solution was to
set this on the client:
stub._getServiceClient().getOptions().setProperty(HTTPConstants.CHUNKED,
Constants.VALUE_FALSE);
-
From: Jorge Fernandez [mailto:[EMAIL PROTECTED]
Sent: Monday, April 16, 2007 6:23 PM
To: axis-user
Subject: issue when sending big arrays
Hi all,
I'm having problems when I have to return big arrays. I have an operation in
the web service I'm building for my Career Final Project which returns the
xml code for a class that contains two arrays and an int. One of the arrays is
an short array and usually is very big. The other one has no components in the
tests I did at the moment. I get the following exception in my client:
Exception in thread main java.lang.RuntimeException: Data binding error
at client.Medici_LinkStub.fromOM(Medici_LinkStub.java:5792)
at client.Medici_LinkStub.getPrimitiveData(Medici_LinkStub.java:2678)
at client.ClientUtilities.getPrimitiveDataTest(ClientUtilities.java:336)
at client.Client.main(Client.java:64)
Caused by: org.apache.xmlbeans.XmlException: Unexpected end of input block in
end tag
at [row,col {unknown-source}]: [1,4095]
at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:847)
at
org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:826)
at
org.apache.xmlbeans.impl.schema.SchemaTypeLoaderBase.parse(SchemaTypeLoaderBase.java:231)
at
medici_link.op_messages.xsd.GetPrimitiveDataResponseDocument$Factory.parse(GetPrimitiveDataResponseDocument.java:163)
at client.Medici_LinkStub.fromOM(Medici_LinkStub.java:5313)
... 3 more
Caused by: com.ctc.wstx.exc.WstxEOFException: Unexpected end of input block in
end tag
at [row,col {unknown-source}]: [1,4095]
at com.ctc.wstx.sr.StreamScanner.throwUnexpectedEOB(StreamScanner.java:675)
at
com.ctc.wstx.sr.StreamScanner.loadMoreFromCurrent(StreamScanner.java:1029)
at
com.ctc.wstx.sr.StreamScanner.getNextCharFromCurrent(StreamScanner.java:786)
at
com.ctc.wstx.sr.BasicStreamReader.readEndElem(BasicStreamReader.java:3204)
at
com.ctc.wstx.sr.BasicStreamReader.nextFromTree(BasicStreamReader.java:2830)
at com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1019)
at
org.apache.axiom.om.impl.llom.OMStAXWrapper.next(OMStAXWrapper.java:917)
at
org.apache.xmlbeans.impl.store.Locale.loadXMLStreamReader(Locale.java:1098)
at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:843)
... 7 more
I tried to find out what was the problem in my web service so I used the
debugger and compared executions with diferent sizes for the array and
everything seems to be alright (the return message appears to be built
correctly) until I reach axisServlet.
In my log file I see:
in axisServlet catch exception: 2007-04-16 22:36:05 ERROR
org.apache.axis2.transport.http.AxisServlet -
java.lang.IllegalStateException: Can't overwrite cause
I think that the method that throws the exception is req.getInputStream() that
is a parameter of HTTPTransportUtils.processHTTPPostRequest.
I started having problems when the array is about 220 components. I would like
to know if there is any limitation on array's sizes.
Thanks and regards,
Jorge Fernández
-
LLama Gratis a cualquier PC del Mundo.
Llamadas a fijos y móviles desde 1 céntimo por minuto.
http://es.voice.yahoo.com
-
LLama Gratis a cualquier PC del Mundo.
Llamadas a fijos y móviles desde 1 céntimo por minuto.
http://es.voice.yahoo.com
-
LLama Gratis a cualquier PC del Mundo.
Llamadas a fijos y móviles desde 1 céntimo por minuto.
http://es.voice.yahoo.com
Re: Help with SwA
Hi Thilina, I didn't have that problem in axis2 1.1.1 but now I'm using the last 1.2 release and I'm having that problem. Regards, Jorge Fernández Thilina Gunarathne [EMAIL PROTECTED] escribió: There was a known bug in Axis2 1.1.1 which prevented the last boundary being written to the wire in the case of running Axis2 in Tomcat ... This was fixed in the latest 1.2 release.. If possible please try the latest or try replacing the Axiom jars.. Thanks, Thilina On 4/30/07, Dennis Sosnoski wrote: int values are a minimum of 32 bits in Java, not 16 bits. They have a range from roughly -2 billion to +2 billion. There may well be a problem in the code, but it's not because ints are limited to +/- 64k. - Dennis Dennis M. Sosnoski SOA and Web Services in Java Training and Consulting http://www.sosnoski.com - http://www.sosnoski.co.nz Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117 Martin Gainty wrote: Jorge Appears you may have discovered a bug as the BoundaryPushbackInputStream.java as there appears to not be ability to deal with any buffer over 64k (the native datatypes appear to be all integer instead of long) Looking at the source http://svn.apache.org/viewvc/webservices/commons/trunk/modules/axiom/modules/axiom-api/src/main/java/org/apache/axiom/attachments/BoundaryPushbackInputStream.java?revision=528680pathrev=528680 I find length assignments of variables to int (max +- 64k) but no mention of lengths to long or unsigned long datatypes Do you know if there a JIRA ??? Saludos Cordiales! Martin-- This email message and any files transmitted with it contain confidential information intended only for the person(s) to whom this email message is addressed. If you have received this email message in error, please notify the sender immediately by telephone or email and destroy the original message without making a copy. Thank you. - Original Message - *From:* Jorge Fernandez *To:* axis-user@ws.apache.org ; [EMAIL PROTECTED] *Sent:* Sunday, April 29, 2007 11:23 AM *Subject:* Re: Help with SwA Hi Thilina, With the new release that seems to work fine. But sadly :( , now I'm getting the following exception when trying to access the attachments with both MTOM or SwA at the client: org.apache.axiom.om.OMException: javax.mail.MessagingException: Error reading input stream; nested exception is: java.io.IOException: End of Stream, but boundary not found at org.apache.axiom.attachments.Attachments.getPart(Attachments.java:517) at org.apache.axiom.attachments.Attachments.getNextPartDataHandler(Attachments.java:414) at org.apache.axiom.attachments.Attachments.getContentIDSet(Attachments.java:386) at org.apache.axiom.attachments.Attachments.getAllContentIDs(Attachments.java:379) at client.Medici_LinkSOAP12PortStub.getAttachment(Medici_LinkSOAP12PortStub.java:4102) at client.ClientUtilities.mtomTest(ClientUtilities.java:531) at client.Client.main(Client.java:69) Caused by: javax.mail.MessagingException: Error reading input stream; nested exception is: java.io.IOException: End of Stream, but boundary not found at javax.mail.internet.MimeBodyPart.(MimeBodyPart.java:177) at org.apache.axiom.attachments.PartOnMemory.(PartOnMemory.java:31) at org.apache.axiom.attachments.Attachments.getPart(Attachments.java:513) ... 6 more Caused by: java.io.IOException: End of Stream, but boundary not found at org.apache.axiom.attachments.BoundaryPushbackInputStream.read(BoundaryPushbackInputStream.java:230) at org.apache.axiom.attachments.MIMEBodyPartInputStream.read(MIMEBodyPartInputStream.java:84) at java.io.BufferedInputStream.fill(Unknown Source) at java.io.BufferedInputStream.read1(Unknown Source) at java.io.BufferedInputStream.read(Unknown Source) at com.sun.mail.util.ASCIIUtility.getBytes(ASCIIUtility.java:246) at javax.mail.internet.MimeBodyPart.(MimeBodyPart.java:175) ... 8 more I can see with TCPMon this: HTTP/1.1 200 OK Server: Apache-Coyote/1.1 Content-Type: multipart/related; boundary=MIMEBoundaryurn_uuid_2B201ECB17F697F7391177859246638; type=application/soap+xml; start=0.urn:uuid:[EMAIL PROTECTED]; action=urn:validateUser;charset=UTF-8Transfer-Encoding: chunkedDate: Sun, 29 Apr 2007 15:07:26 GMT423--MIMEBoundaryurn_uuid_2B201ECB17F697F7391177859246638Content-Type: application/soap+xml; charset=UTF-8Content-Transfer-Encoding: 8bitContent-ID: 0.urn:uuid:[EMAIL PROTECTED] xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope; http://www.w3.org/2005/08/addressing/none xmlns:axis2=http://ws.apache.org/namespaces
Re: Help with SwA
without making a copy. Thank you. - Original Message - *From:* Jorge Fernandez *To:* axis-user@ws.apache.org ; [EMAIL PROTECTED] *Sent:* Sunday, April 29, 2007 11:23 AM *Subject:* Re: Help with SwA Hi Thilina, With the new release that seems to work fine. But sadly :( , now I'm getting the following exception when trying to access the attachments with both MTOM or SwA at the client: org.apache.axiom.om.OMException: javax.mail.MessagingException: Error reading input stream; nested exception is: java.io.IOException: End of Stream, but boundary not found at org.apache.axiom.attachments.Attachments.getPart(Attachments.java:517) at org.apache.axiom.attachments.Attachments.getNextPartDataHandler(Attachments.java:414) at org.apache.axiom.attachments.Attachments.getContentIDSet(Attachments.java:386) at org.apache.axiom.attachments.Attachments.getAllContentIDs(Attachments.java:379) at client.Medici_LinkSOAP12PortStub.getAttachment(Medici_LinkSOAP12PortStub.java:4102) at client.ClientUtilities.mtomTest(ClientUtilities.java:531) at client.Client.main(Client.java:69) Caused by: javax.mail.MessagingException: Error reading input stream; nested exception is: java.io.IOException: End of Stream, but boundary not found at javax.mail.internet.MimeBodyPart.(MimeBodyPart.java:177) at org.apache.axiom.attachments.PartOnMemory.(PartOnMemory.java:31) at org.apache.axiom.attachments.Attachments.getPart(Attachments.java:513) ... 6 more Caused by: java.io.IOException: End of Stream, but boundary not found at org.apache.axiom.attachments.BoundaryPushbackInputStream.read(BoundaryPushbackInputStream.java:230) at org.apache.axiom.attachments.MIMEBodyPartInputStream.read(MIMEBodyPartInputStream.java:84) at java.io.BufferedInputStream.fill(Unknown Source) at java.io.BufferedInputStream.read1(Unknown Source) at java.io.BufferedInputStream.read(Unknown Source) at com.sun.mail.util.ASCIIUtility.getBytes(ASCIIUtility.java:246) at javax.mail.internet.MimeBodyPart.(MimeBodyPart.java:175) ... 8 more I can see with TCPMon this: HTTP/1.1 200 OK Server: Apache-Coyote/1.1 Content-Type: multipart/related; boundary=MIMEBoundaryurn_uuid_2B201ECB17F697F7391177859246638; type=application/soap+xml; start=0.urn:uuid:[EMAIL PROTECTED]; action=urn:validateUser;charset=UTF-8Transfer-Encoding: chunkedDate: Sun, 29 Apr 2007 15:07:26 GMT423--MIMEBoundaryurn_uuid_2B201ECB17F697F7391177859246638Content-Type: application/soap+xml; charset=UTF-8Content-Transfer-Encoding: 8bitContent-ID: 0.urn:uuid:[EMAIL PROTECTED] xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope; http://www.w3.org/2005/08/addressing/none xmlns:axis2=http://ws.apache.org/namespaces/axis2;urn:uuid:2B201ECB17F697F7391177859246088 urn:uuid:2B201ECB17F697F7391177859246104 urn:validateUser urn:uuid:7C37DED94C81AED4F81177859244163 xmlns:ns3=http://op_messages.medici_link/xsd; sim588929623218 38 --MIMEBoundaryurn_uuid_2B201ECB17F697F7391177859246638 2000 Content-Type: application/octet-stream Content-Transfer-Encoding: binary Content-ID: BM:/ data And this is the last line I can see with TCPMon ¥b;¤a:£_:¡]8]7Z4Y3W1U/T I'm sending a 11'8KB picture. With axis2 1.1.1 I had no problem with sending a picture that was about 24 KB. If I sent a larger one, I received it with errors and I couldn't see it correctly in the client but the response message seemed to be well formed. Could you tell me, please if I have to do something else to send attachments in the service?? */Thilina Gunarathne /* escribió: org.apache.axis2.AxisFault: Invalid Application type. Support available for MTOM SwA/SOAP 1.l only.; nested exception is: org.apache.axiom.om.OMException: Invalid Application type. Support available for MTOM SwA/SOAP 1.l only. You seem to be usign a old version of the axis2.. Please try the latest 1.2 release.. But I don't know if this is right. Do I have to specify something in the wsdl like I do when I use MTOM so the client could expect any attachment when parsing the response message. MTOM is much better than SwA.. You can specify the type of the element containing the binary data as base64Binary... Seems like you already have it in your WSDL, since you seem
Re: [ANN][Axis2]Axis2 1.2 Released
JIRA 2603 created. Thanks and regards, Jorge Fernández Davanum Srinivas [EMAIL PROTECTED] escribió: Jorge, JIRA Please...with your code sample so that we can recreate the problem. thanks, dims On 4/28/07, Jorge Fernandez wrote: Hi, I would like to say thanks to all the developers for the great job they did with the new release, fixing the issues and for all the supporting work; but I'm not going to let you rest ;). Sorry for that: I've just installed the new release and some of the bugs were fixed and with these corrections I discover other. I reopened JIRA AXIS2-2325 with those now issues. Also I could see that the problem with hierarchy generation in the wsdl was almost fixed except in cases described in that JIRA. One problem I'm having now is that when I have a hierarchy, for the children, it generates them correctly but it doesn't generate the father. In my case I supose that this is because I haven't used them in the API from which I generate the WSDL. For example, I define the method: public boolean validateAdmin(Administrator admin); where Administrator class extends User. Java2WSDL would generate: .. but not: .. since I don't use User class in my API. (If I'm not wrong, name=User type=ax23:User/ wouldn't need to be generated) Regards, Jorge Fernández Davanum Srinivas escribió: Till we fix the execute permission on the cgi :) please use http://www.apache.org/dyn/closer.cgi/ws/axis2/1_2/ (mirrors) http://www.apache.org/dist/ws/axis2/1_2/ (direct) thanks, dims On 4/27/07, Hickman, Craig wrote: Seems to be a problem with the download.cgi ? -Original Message- From: Deepal Jayasinghe [mailto:[EMAIL PROTECTED] Sent: Friday, April 27, 2007 10:30 AM To: axis-user@ws.apache.org Subject: [ANN][Axis2]Axis2 1.2 Released -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Just over 4 months since the original 1.1.1 release, we are very proud to announce the release of Apache Axis2 version 1.2 Downloads are available at: http://ws.apache.org/axis2/download.cgi Apache Axis2 is a complete re-design and re-write of the widely used Apache Axis engine and is a more efficient, more scalable, more modular and more XML-oriented Web services framework. It is carefully designed to support the easy addition of plug-in modules that extend its functionality for features such as security and reliability. Modules supporting WS-Security/Secure-Conversation (Apache Rampart), WS-Trust (Apache Rahas), WS-Reliable Messaging (Apache Sandesha) and WS-Eventing (Apache Savan) will be available after the Apache Axis2 1.2 release. Please see these projects' own sites for further information. Major Changes Since 1.1: - - WSDL 2.0 fully support (reading, writing, and codegen) - - POJO annotation (JSR 181) - - JAX-WS integration - - JAX-WS -annotation - - Un-wrapping (Response) - - ADB - support for union and list - - Maven2 support - - JSON support - - Binary serialization (Fast infoste) - - Codegen support for WSDL with Multiple services - - HTTP code generation (both WSDL 1.1 and 2.0) - - Custom deployer support - - Message formatters - - Message Builders - - EJB Provider support Known Issues and Limitations in 1.2 Release: - - Xml-beans databinding does not support response uwwrapping - - ADB databinding does not support minOccurs and maxOccures attributes in sequence and choice elements Apache Axis2 1.2 is a major new release compared to Axis2 1.1. We are striving for a simple and happy first time user experience as well as a satisfying experienced user experience with this release. We welcome any and all feedback at: axis-user@ws.apache.org (please include [axis2] in the subject) [EMAIL PROTECTED] (please include [axis2] in the subject) http://issues.apache.org/jira/browse/AXIS2 Thank you for your interest in Apache Axis2! The Axis2 Development Team http://ws.apache.org/axis2/ - Features of Apache Axis2: Programming Model - Improved XML-centric client API with full WSDL and policy support - Support for POJO and Spring services and clients - Support for any message exchange pattern (MEP) - Synchronous and asynchronous programming model - Archived service deployment model supporting full service encapsulation with versioning support - Archived module deployment model supporting controlled extensibility with versioning support - Hot deployment - WS-Policy driven code generation extensions - Flexible service life cycle model - Automatic
Re: Help with SwA
Hola Martin, Thank you for the information. I don't know if there is a JIRA. But I think it's strange this bug when in the previous release there weren't any problems. Saludos, Jorge Fernández Martin Gainty [EMAIL PROTECTED] escribió: Jorge Appears you may have discovered a bug as the BoundaryPushbackInputStream.java as there appears to not be ability to deal with any buffer over 64k (the native datatypes appear to be all integer instead of long) Looking at the source http://svn.apache.org/viewvc/webservices/commons/trunk/modules/axiom/modules/axiom-api/src/main/java/org/apache/axiom/attachments/BoundaryPushbackInputStream.java?revision=528680pathrev=528680 I find length assignments of variables to int (max +- 64k) but no mention of lengths to long or unsigned long datatypes Do you know if there a JIRA ??? Saludos Cordiales! Martin-- This email message and any files transmitted with it contain confidential information intended only for the person(s) to whom this email message is addressed. If you have received this email message in error, please notify the sender immediately by telephone or email and destroy the original message without making a copy. Thank you. - Original Message - From:Jorge Fernandez To: axis-user@ws.apache.org ; [EMAIL PROTECTED] Sent: Sunday, April 29, 2007 11:23AM Subject: Re: Help with SwA Hi Thilina, With the new release that seems to workfine. But sadly :( , now I'm getting the following exception when trying toaccess the attachments with both MTOM or SwA at theclient: org.apache.axiom.om.OMException: javax.mail.MessagingException:Error reading input stream; nested exceptionis: java.io.IOException: End of Stream, but boundary notfound atorg.apache.axiom.attachments.Attachments.getPart(Attachments.java:517) at org.apache.axiom.attachments.Attachments.getNextPartDataHandler(Attachments.java:414) at org.apache.axiom.attachments.Attachments.getContentIDSet(Attachments.java:386) at org.apache.axiom.attachments.Attachments.getAllContentIDs(Attachments.java:379) at client.Medici_LinkSOAP12PortStub.getAttachment(Medici_LinkSOAP12PortStub.java:4102) atclient.ClientUtilities.mtomTest(ClientUtilities.java:531) at client.Client.main(Client.java:69) Caused by:javax.mail.MessagingException: Error reading input stream; nestedexception is: java.io.IOException: End of Stream, butboundary not found atjavax.mail.internet.MimeBodyPart.init(MimeBodyPart.java:177) at org.apache.axiom.attachments.PartOnMemory.init(PartOnMemory.java:31) at org.apache.axiom.attachments.Attachments.getPart(Attachments.java:513) ... 6 more Caused by: java.io.IOException: End of Stream, but boundary notfound at org.apache.axiom.attachments.BoundaryPushbackInputStream.read(BoundaryPushbackInputStream.java:230) at org.apache.axiom.attachments.MIMEBodyPartInputStream.read(MIMEBodyPartInputStream.java:84) at java.io.BufferedInputStream.fill(Unknown Source) atjava.io.BufferedInputStream.read1(Unknown Source) atjava.io.BufferedInputStream.read(Unknown Source) atcom.sun.mail.util.ASCIIUtility.getBytes(ASCIIUtility.java:246) atjavax.mail.internet.MimeBodyPart.init(MimeBodyPart.java:175) ... 8 more I can see with TCPMon this: HTTP/1.1 200OK Server: Apache-Coyote/1.1 Content-Type: multipart/related; boundary=MIMEBoundaryurn_uuid_2B201ECB17F697F7391177859246638; type=application/soap+xml;start=0.urn:uuid:[EMAIL PROTECTED]; action=urn:validateUser;charset=UTF-8Transfer-Encoding: chunkedDate: Sun, 29 Apr 2007 15:07:26 GMT423--MIMEBoundaryurn_uuid_2B201ECB17F697F7391177859246638Content-Type: application/soap+xml; charset=UTF-8Content-Transfer-Encoding: 8bitContent-ID: 0.urn:uuid:[EMAIL PROTECTED] ?xml version='1.0'encoding='UTF-8'? soapenv:Envelope xmlns:wsa=http://www.w3.org/2005/08/addressing; xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope; soapenv:Header wsa:ReplyTo wsa:Addresshttp://www.w3.org/2005/08/addressing/none/wsa:Address wsa:ReferenceParameters axis2:ServiceGroupId xmlns:axis2=http://ws.apache.org/namespaces/axis2;urn:uuid:2B201ECB17F697F7391177859246088/axis2:ServiceGroupId /wsa:ReferenceParameters /wsa:ReplyTo wsa:MessageIDurn:uuid:2B201ECB17F697F7391177859246104/wsa:MessageID wsa:Actionurn:validateUser/wsa:Action wsa:RelatesTourn:uuid:7C37DED94C81AED4F81177859244163/wsa:RelatesTo /soapenv:Header soapenv:Body ns3:validateUserResponse xmlns:ns3=http://op_messages.medici_link/xsd
Re: Issue with ADB and parsing a response message (namespaces)
Hi again Amila, I've just downloaded and installed axis2 1.2. I built again the project from my wsdl and still get the same problem. Thanks and Regards, Jorge Fernández Jorge Fernandez [EMAIL PROTECTED] escribió: In my test I was using axiom 1.2.4 and I had the same problem as with 1.2.2 Amila Suriarachchi [EMAIL PROTECTED] escribió: I ran your code with the branch code and the axiom-SNAPSHOT and it works fine. So the problem is with the axiom 1.2.2 you have to use the 1.2.4 Please try with the next RC. On 4/24/07, Jorge Fernandez [EMAIL PROTECTED] wrote: Hi Amila, I tried again without the addressing module and I had the same exception I was having with axiom 1.2.2. Regards, Jorge Fernández Rodríguez Amila Suriarachchi [EMAIL PROTECTED] escribió: On 4/23/07, Jorge Fernandez [EMAIL PROTECTED] wrote: Sorry, I don't know what you mean. I think you use the Axis2-1.2-RC2 release. In that release you have a lib directory which contain axiom 1.2.3 jars. (i.e. axiom-api-1.2.3.jar, axiom-impl-1.2.3.jar ,axiom-dom-1.2.3.jar). Get the Axiom 1.2.4 release from here http://ws.apache.org/commons/axiom/download.cgi and replace the 1.2.3 jars with the 1.2.4 jars. It seems that now you are getting some addressing problem. So please check it without addressing. Regards, Jorge Fernández Martin Gainty [EMAIL PROTECTED] escribió: Jorge I cannot display the url for your first namespace http://external.communication_data_model.medici_link/xsd M-- This email message and any files transmitted with it contain confidential information intended only for the person(s) to whom this email message is addressed. If you have received this email message in error, please notify the sender immediately by telephone or email and destroy the original message without making a copy. Thank you. - Original Message - From:Jorge Fernandez To: axis-user@ws.apache.org ; [EMAIL PROTECTED] Sent: Sunday, April 22, 2007 8:40 PM Subject: Re: Issue with ADB and parsing aresponse message (namespaces) Hi, I couldn't reproduce the error again. If you want Ican open a JIRA but I can't attach any code. I had found anotherproblem related with ADB parsing when there is some hierarchy and I raisedJIRA 2578. Regards, Jorge Fernández Anne ThomasManes [EMAIL PROTECTED]escribió:Please file a JIRA. On 4/20/07, Jorge Fernandez wrote: Hi all, I'm having problems with the namespaces of a response message like this: xmlns:ns3= http://op_messages.medici_link/xsd; xmlns:ns0= http://external.communication_data_model.medici_link/xsd; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance xsi:type=ns0:extConfiguration .. xsi:type=ns0:extAbstractParameterDesc .. .. xsi:type=ns0:extPrimitiveParameterDesc . .. I have this exception when parsing the first element (ns0:abstractParameters): java.lang.RuntimeException: java.lang.RuntimeException : Unsupported type null extPrimitiveParameterDesc atclient.Medici_LinkStub.fromOM(Medici_LinkStub.java:5210) at client.Medici_LinkStub.getDetailedMonitoringStages(Medici_LinkStub.java:1945) at client.ClientUtilities.getDetailedMonitoringStagesTest (ClientUtilities.java:244) at client.Client.main (Client.java:53) Caused by: java.lang.RuntimeException: Unsupported type null extPrimitiveParameterDesc at medici_link.op_messages.xsd.ExtensionMapper.getTypeObject(ExtensionMapperjava:181) at medici_link.communication_data_model.external.xsd.ExtParameterDesc$Factory.parse(ExtParameterDesc.java:1171) at medici_link.communication_data_model.external.xsd.ExtAbstractParameterDesc$Factory.parse( ExtAbstractParameterDesc.java:1311) at medici_link.communication_data_model.external.xsd.ExtConfiguration$Factory.parse(ExtConfiguration.java:923) at medici_link.communication_data_model.external.xsd.ExtStage$Factory.parse(ExtStage.java:650) at medici_link.op_messages.xsd.GetDetailedMonitoringStagesResponse$Factory.parse(GetDetailedMonitoringStagesResponse.java :424) at client.Medici_LinkStub.fromOM(Medici_LinkStub.java:4833) .. 3 more I have a hierachy of classes: ExtAbstractParameterDesc and ExtPrimitiveParameterDesc that extend ExtParameterDesc. I've been diving in my code that was created with WSDL2Java and ADB (Axis 1.1.1) and I could see that for that element, it enters the parse Method of ExtAbstractParameterDesc, then it reaches this: if (true.equals
Re: [ANN][Axis2]Axis2 1.2 Released
Hi, I would like to say thanks to all the developers for the great job they did with the new release, fixing the issues and for all the supporting work; but I'm not going to let you rest ;). Sorry for that: I've just installed the new release and some of the bugs were fixed and with these corrections I discover other. I reopened JIRA AXIS2-2325 with those now issues. Also I could see that the problem with hierarchy generation in the wsdl was almost fixed except in cases described in that JIRA. One problem I'm having now is that when I have a hierarchy, for the children, it generates them correctly but it doesn't generate the father. In my case I supose that this is because I haven't used them in the API from which I generate the WSDL. For example, I define the method: public boolean validateAdmin(Administrator admin); where Administrator class extends User. Java2WSDL would generate: xs:element name=Administrator type=ax23:Administrator/ xs:complexType name=Administrator xs:complexContent xs:extension base=ax23:User xs:sequence .. /xs:sequence /xs:extension /xs:complexContent /xs:complexType but not: xs:element name=User type=ax23:User/ xs:complexType name=User xs:sequence .. /xs:sequence /xs:complexType since I don't use User class in my API. (If I'm not wrong, xs:element name=User type=ax23:User/ wouldn't need to be generated) Regards, Jorge Fernández Davanum Srinivas [EMAIL PROTECTED] escribió: Till we fix the execute permission on the cgi :) please use http://www.apache.org/dyn/closer.cgi/ws/axis2/1_2/ (mirrors) http://www.apache.org/dist/ws/axis2/1_2/ (direct) thanks, dims On 4/27/07, Hickman, Craig wrote: Seems to be a problem with the download.cgi ? -Original Message- From: Deepal Jayasinghe [mailto:[EMAIL PROTECTED] Sent: Friday, April 27, 2007 10:30 AM To: axis-user@ws.apache.org Subject: [ANN][Axis2]Axis2 1.2 Released -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Just over 4 months since the original 1.1.1 release, we are very proud to announce the release of Apache Axis2 version 1.2 Downloads are available at: http://ws.apache.org/axis2/download.cgi Apache Axis2 is a complete re-design and re-write of the widely used Apache Axis engine and is a more efficient, more scalable, more modular and more XML-oriented Web services framework. It is carefully designed to support the easy addition of plug-in modules that extend its functionality for features such as security and reliability. Modules supporting WS-Security/Secure-Conversation (Apache Rampart), WS-Trust (Apache Rahas), WS-Reliable Messaging (Apache Sandesha) and WS-Eventing (Apache Savan) will be available after the Apache Axis2 1.2 release. Please see these projects' own sites for further information. Major Changes Since 1.1: - - WSDL 2.0 fully support (reading, writing, and codegen) - - POJO annotation (JSR 181) - - JAX-WS integration - - JAX-WS -annotation - - Un-wrapping (Response) - - ADB - support for union and list - - Maven2 support - - JSON support - - Binary serialization (Fast infoste) - - Codegen support for WSDL with Multiple services - - HTTP code generation (both WSDL 1.1 and 2.0) - - Custom deployer support - - Message formatters - - Message Builders - - EJB Provider support Known Issues and Limitations in 1.2 Release: - - Xml-beans databinding does not support response uwwrapping - - ADB databinding does not support minOccurs and maxOccures attributes in sequence and choice elements Apache Axis2 1.2 is a major new release compared to Axis2 1.1. We are striving for a simple and happy first time user experience as well as a satisfying experienced user experience with this release. We welcome any and all feedback at: axis-user@ws.apache.org (please include [axis2] in the subject) [EMAIL PROTECTED] (please include [axis2] in the subject) http://issues.apache.org/jira/browse/AXIS2 Thank you for your interest in Apache Axis2! The Axis2 Development Team http://ws.apache.org/axis2/ - Features of Apache Axis2: Programming Model - Improved XML-centric client API with full WSDL and policy support - Support for POJO and Spring services and clients - Support for any message exchange pattern (MEP) - Synchronous and asynchronous programming model - Archived service deployment model supporting full service encapsulation with versioning support - Archived module deployment model supporting controlled extensibility with versioning support - Hot deployment - WS-Policy driven code generation extensions -
Help with SwA
Hi,
I'm trying to send a file with SwA from the service to the client and I'm not
sure how to do it. When I set enableSwA parameter to true in the operation in
the service.xml I get the exception:
org.apache.axis2.AxisFault: Invalid Application type. Support available for
MTOM SwA/SOAP 1.l only.; nested exception is:
org.apache.axiom.om.OMException: Invalid Application type. Support
available for MTOM SwA/SOAP 1.l only.
at
org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:126)
at
org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:67)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:252)
at
org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:202)
at client.Medici_LinkStub.validateUser(Medici_LinkStub.java:1753)
at client.ClientUtilities.validateUserTest(ClientUtilities.java:100)
at client.Client.main(Client.java:44)
Caused by: org.apache.axiom.om.OMException: Invalid Application type. Support
available for MTOM SwA/SOAP 1.l only.
at
org.apache.axiom.attachments.Attachments.getAttachmentSpecType(Attachments.java:216)
at
org.apache.axis2.transport.TransportUtils.selectBuilderForMIME(TransportUtils.java:264)
at
org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:98)
... 6 more
Then I was trying to do something like:
File file = new
File(System.getenv(CATALINA_HOME)+/webapps/axis2/WEB-INF/services/Medici_Link/Wallpaper1.bmp);
if (!file.exists()){
throw new Exception(File not found exception);
}
MTOMResponse response=new MTOMResponse();
MessageContext msgCtx = MessageContext.getCurrentMessageContext();
// Populating the code generated beans
FileDataSource fileDataSource = new FileDataSource(file);
DataHandler dataHandler = new DataHandler(fileDataSource);
msgCtx.setDoingSwA(true);
String attachmentID=msgCtx.addAttachment(dataHandler);
But I don't know if this is right. Do I have to specify something in the wsdl
like I do when I use MTOM so the client could expect any attachment when
parsing the response message.
With MTOM I have no problem. I'm doing this and in my services.xml I set the
enableMTOM parameter without any error:
public MTOMResponse mtom(MTOM param0)throws Exception{
File file = new
File(System.getenv(CATALINA_HOME)+/webapps/axis2/WEB-INF/services/Medici_Link/+param0.getParam0());
if (!file.exists()){
throw new FileNotFoundException();
}
// Populating the code generated beans
MTOMResponse response=new MTOMResponse();
FileDataSource fileDataSource = new FileDataSource(file);
DataHandler dataHandler = new DataHandler(fileDataSource);
Base64Binary binaryData =new Base64Binary();
binaryData.setBase64Binary(dataHandler);
binaryData.setContentType(dataHandler.getContentType());
response.setFileName(ejemplo.txt);
response.setBinaryData(binaryData);
return response;
}
Thanks in advance,
Jorge Fernández
-
LLama Gratis a cualquier PC del Mundo.
Llamadas a fijos y móviles desde 1 céntimo por minuto.
http://es.voice.yahoo.com
Re: Issue with ADB and parsing a response message (namespaces)
In my test I was using axiom 1.2.4 and I had the same problem as with 1.2.2
Amila Suriarachchi [EMAIL PROTECTED] escribió: I ran your code with the
branch code and the axiom-SNAPSHOT and it works fine.
So the problem is with the axiom 1.2.2 you have to use the 1.2.4
Please try with the next RC.
On 4/24/07, Jorge Fernandez [EMAIL PROTECTED] wrote: Hi Amila,
I tried again without the addressing module and I had the same exception I was
having with axiom 1.2.2.
Regards,
Jorge Fernández Rodríguez
Amila Suriarachchi [EMAIL PROTECTED] escribió:
On 4/23/07, Jorge Fernandez [EMAIL PROTECTED] wrote: Sorry, I don't know
what you mean.
I think you use the Axis2-1.2-RC2 release. In that release you have a lib
directory which contain axiom 1.2.3 jars. (i.e. axiom-api-1.2.3.jar,
axiom-impl-1.2.3.jar ,axiom-dom-1.2.3.jar). Get the Axiom 1.2.4 release from
here
http://ws.apache.org/commons/axiom/download.cgi and replace the 1.2.3 jars with
the 1.2.4 jars.
It seems that now you are getting some addressing problem. So please check it
without addressing.
Regards,
Jorge Fernández
Martin Gainty [EMAIL PROTECTED] escribió: Jorge
I cannot display the url for your first namespace
http://external.communication_data_model.medici_link/xsd
M--
This email message and any files transmitted with it contain confidential
information intended only for the person(s) to whom this email message is
addressed. If you have received this email message in error, please notify
the sender immediately by telephone or email and destroy the original
message without making a copy. Thank you.
- Original Message -
From:Jorge Fernandez
To: axis-user@ws.apache.org ; [EMAIL PROTECTED]
Sent: Sunday, April 22, 2007 8:40 PM
Subject: Re: Issue with ADB and parsing aresponse message (namespaces)
Hi,
I couldn't reproduce the error again. If you want Ican open a JIRA but I
can't attach any code.
I had found anotherproblem related with ADB parsing when there is some
hierarchy and I raisedJIRA 2578.
Regards,
Jorge Fernández
Anne ThomasManes [EMAIL PROTECTED]escribió:Please file a
JIRA.
On 4/20/07, Jorge Fernandez wrote:
Hi all,
I'm having problems with the namespaces of a response message like
this:
xmlns:ns3= http://op_messages.medici_link/xsd;
xmlns:ns0= http://external.communication_data_model.medici_link/xsd;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance
xsi:type=ns0:extConfiguration
..
xsi:type=ns0:extAbstractParameterDesc
..
..
xsi:type=ns0:extPrimitiveParameterDesc
.
..
I have this exception when parsing the first element
(ns0:abstractParameters):
java.lang.RuntimeException: java.lang.RuntimeException : Unsupported
type
null extPrimitiveParameterDesc
at client.Medici_LinkStub.fromOM(Medici_LinkStub.java:5210)
at
client.Medici_LinkStub.getDetailedMonitoringStages(Medici_LinkStub.java:1945)
at
client.ClientUtilities.getDetailedMonitoringStagesTest
(ClientUtilities.java:244)
at client.Client.main (Client.java:53)
Caused by: java.lang.RuntimeException: Unsupported type null
extPrimitiveParameterDesc
at
medici_link.op_messages.xsd.ExtensionMapper.getTypeObject(ExtensionMapperjava:181)
at
medici_link.communication_data_model.external.xsd.ExtParameterDesc$Factory.parse(ExtParameterDesc.java:1171)
at
medici_link.communication_data_model.external.xsd.ExtAbstractParameterDesc$Factory.parse(
ExtAbstractParameterDesc.java:1311)
at
medici_link.communication_data_model.external.xsd.ExtConfiguration$Factory.parse(ExtConfiguration.java:923)
at
medici_link.communication_data_model.external.xsd.ExtStage$Factory.parse(ExtStage.java:650)
at
medici_link.op_messages.xsd.GetDetailedMonitoringStagesResponse$Factory.parse(GetDetailedMonitoringStagesResponse.java
:424)
at client.Medici_LinkStub.fromOM(Medici_LinkStub.java:4833)
.. 3 more
I have a hierachy of classes:
ExtAbstractParameterDesc and ExtPrimitiveParameterDesc that extend
ExtParameterDesc.
I've been diving in my code that was created with WSDL2Java and ADB (Axis
1.1.1) and I could see that for that element, it enters
the parse Method of ExtAbstractParameterDesc, then it reaches this:
if
(true.equals(reader.getAttributeValue(http://www.w3.org/2001/XMLSchema-instance
,nil))){
list9.add(null);
reader.next();
} else {
list9.add(medici_link.communication_data_model.external.xsd.ExtParameterDesc.Factory.parse(reader
Re: Issue with ADB and parsing a response message (namespaces)
Sorry, I don't know what you mean.
Regards,
Jorge Fernández
Martin Gainty [EMAIL PROTECTED] escribió: Jorge
I cannot display the url for your first namespace
http://external.communication_data_model.medici_link/xsd
M--
This email message and any files transmitted with it contain confidential
information intended only for the person(s) to whom this email message is
addressed. If you have received this email message in error, please notify
the sender immediately by telephone or email and destroy the original
message without making a copy. Thank you.
- Original Message -
From:Jorge Fernandez
To: axis-user@ws.apache.org ; [EMAIL PROTECTED]
Sent: Sunday, April 22, 2007 8:40 PM
Subject: Re: Issue with ADB and parsing aresponse message (namespaces)
Hi,
I couldn't reproduce the error again. If you want Ican open a JIRA but I
can't attach any code.
I had found anotherproblem related with ADB parsing when there is some
hierarchy and I raisedJIRA 2578.
Regards,
Jorge Fernández
Anne ThomasManes [EMAIL PROTECTED]escribió: Please file a JIRA.
On 4/20/07, Jorge Fernandez wrote:
Hi all,
I'm having problems with the namespaces of a response message like
this:
xmlns:ns3=http://op_messages.medici_link/xsd;
xmlns:ns0=http://external.communication_data_model.medici_link/xsd;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:type=ns0:extConfiguration
..
xsi:type=ns0:extAbstractParameterDesc
..
..
xsi:type=ns0:extPrimitiveParameterDesc
.
..
I have this exception when parsing the first element
(ns0:abstractParameters):
java.lang.RuntimeException: java.lang.RuntimeException: Unsupported type
null extPrimitiveParameterDesc
at client.Medici_LinkStub.fromOM(Medici_LinkStub.java:5210)
at
client.Medici_LinkStub.getDetailedMonitoringStages(Medici_LinkStub.java:1945)
at
client.ClientUtilities.getDetailedMonitoringStagesTest(ClientUtilities.java:244)
at client.Client.main(Client.java:53)
Caused by: java.lang.RuntimeException: Unsupported type null
extPrimitiveParameterDesc
at
medici_link.op_messages.xsd.ExtensionMapper.getTypeObject(ExtensionMapperjava:181)
at
medici_link.communication_data_model.external.xsd.ExtParameterDesc$Factory.parse(ExtParameterDesc.java:1171)
at
medici_link.communication_data_model.external.xsd.ExtAbstractParameterDesc$Factory.parse(ExtAbstractParameterDesc.java:1311)
at
medici_link.communication_data_model.external.xsd.ExtConfiguration$Factory.parse(ExtConfiguration.java:923)
at
medici_link.communication_data_model.external.xsd.ExtStage$Factory.parse(ExtStage.java:650)
at
medici_link.op_messages.xsd.GetDetailedMonitoringStagesResponse$Factory.parse(GetDetailedMonitoringStagesResponse.java:424)
at client.Medici_LinkStub.fromOM(Medici_LinkStub.java:4833)
.. 3 more
I have a hierachy of classes:
ExtAbstractParameterDesc and ExtPrimitiveParameterDesc that extend
ExtParameterDesc.
I've been diving in my code that was created with WSDL2Java and ADB (Axis
1.1.1) and I could see that for that element, it enters
the parse Method of ExtAbstractParameterDesc, then it reaches this:
if
(true.equals(reader.getAttributeValue(http://www.w3.org/2001/XMLSchema-instance,nil;))){
list9.add(null);
reader.next();
} else {
list9.add(medici_link.communication_data_model.external.xsd.ExtParameterDesc.Factory.parse(reader));
}
And goes to the else statement. So it enters the parse method of
ExtParameterDesc (it's father class).
When it's inside that method, variable type gets the value
ExtPrimitiveParameterDesc (I don't know if it should be
ExtAbstractParameterDesc but I made that change and it threw an
exception in
other place) and finally it tries to get the namespace uri of prefix ns0
and
it gets null.
this is the snippet:
java.lang.String type =
fullTypeName.substring(fullTypeName.indexOf(:)+1);
if (!extParameterDesc.equals(type)){
//find namespace for the prefix
java.lang.String nsUri =
reader.getNamespaceContext().getNamespaceURI(ns0);
nsUri=http://external.communication_data_model.medici_link/xsd;;
return
(ExtParameterDesc)medici_link.op_messages.xsd.ExtensionMapper.getTypeObject(nsUri,type,reader);
}
As you can see in the message, it is
http://external.communication_data_model.medici_link/xsd;.
So the exception is thrown because it can't get de typeObject.
I added the line
nsUri=http
Re: Issue with ADB and parsing a response message (namespaces)
Hi,
I couldn't reproduce the error again. If you want I can open a JIRA but I can't
attach any code.
I had found another problem related with ADB parsing when there is some
hierarchy and I raised JIRA 2578.
Regards,
Jorge Fernández
Anne Thomas Manes [EMAIL PROTECTED] escribió: Please file a JIRA.
On 4/20/07, Jorge Fernandez wrote:
Hi all,
I'm having problems with the namespaces of a response message like this:
xmlns:ns3=http://op_messages.medici_link/xsd;
xmlns:ns0=http://external.communication_data_model.medici_link/xsd;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:type=ns0:extConfiguration
..
xsi:type=ns0:extAbstractParameterDesc
..
..
xsi:type=ns0:extPrimitiveParameterDesc
.
..
I have this exception when parsing the first element
(ns0:abstractParameters):
java.lang.RuntimeException: java.lang.RuntimeException: Unsupported type
null extPrimitiveParameterDesc
at client.Medici_LinkStub.fromOM(Medici_LinkStub.java:5210)
at
client.Medici_LinkStub.getDetailedMonitoringStages(Medici_LinkStub.java:1945)
at
client.ClientUtilities.getDetailedMonitoringStagesTest(ClientUtilities.java:244)
at client.Client.main(Client.java:53)
Caused by: java.lang.RuntimeException: Unsupported type null
extPrimitiveParameterDesc
at
medici_link.op_messages.xsd.ExtensionMapper.getTypeObject(ExtensionMapper.java:181)
at
medici_link.communication_data_model.external.xsd.ExtParameterDesc$Factory.parse(ExtParameterDesc.java:1171)
at
medici_link.communication_data_model.external.xsd.ExtAbstractParameterDesc$Factory.parse(ExtAbstractParameterDesc.java:1311)
at
medici_link.communication_data_model.external.xsd.ExtConfiguration$Factory.parse(ExtConfiguration.java:923)
at
medici_link.communication_data_model.external.xsd.ExtStage$Factory.parse(ExtStage.java:650)
at
medici_link.op_messages.xsd.GetDetailedMonitoringStagesResponse$Factory.parse(GetDetailedMonitoringStagesResponse.java:424)
at client.Medici_LinkStub.fromOM(Medici_LinkStub.java:4833)
... 3 more
I have a hierachy of classes:
ExtAbstractParameterDesc and ExtPrimitiveParameterDesc that extend
ExtParameterDesc.
I've been diving in my code that was created with WSDL2Java and ADB (Axis
1.1.1) and I could see that for that element, it enters
the parse Method of ExtAbstractParameterDesc, then it reaches this:
if
(true.equals(reader.getAttributeValue(http://www.w3.org/2001/XMLSchema-instance,nil;))){
list9.add(null);
reader.next();
} else {
list9.add(medici_link.communication_data_model.external.xsd.ExtParameterDesc.Factory.parse(reader));
}
And goes to the else statement. So it enters the parse method of
ExtParameterDesc (it's father class).
When it's inside that method, variable type gets the value
ExtPrimitiveParameterDesc (I don't know if it should be
ExtAbstractParameterDesc but I made that change and it threw an exception in
other place) and finally it tries to get the namespace uri of prefix ns0 and
it gets null.
this is the snippet:
java.lang.String type = fullTypeName.substring(fullTypeName.indexOf(:)+1);
if (!extParameterDesc.equals(type)){
//find namespace for the prefix
java.lang.String nsUri =
reader.getNamespaceContext().getNamespaceURI(ns0);
nsUri=http://external.communication_data_model.medici_link/xsd;;
return
(ExtParameterDesc)medici_link.op_messages.xsd.ExtensionMapper.getTypeObject(nsUri,type,reader);
}
As you can see in the message, it is
http://external.communication_data_model.medici_link/xsd;.
So the exception is thrown because it can't get de typeObject.
I added the line
nsUri=http://external.communication_data_model.medici_link/xsd;;
just before getTypeObject is called and it works.
With XMLBeans, it works perfectly.
Regards,
Jorge Fernández
LLama Gratis a cualquier PC del Mundo.
Llamadas a fijos y móviles desde 1 céntimo por minuto.
http://es.voice.yahoo.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
LLama Gratis a cualquier PC del Mundo.
Llamadas a fijos y móviles desde 1 céntimo por minuto.
http://es.voice.yahoo.com
RE: issue when sending big arrays
Hi Valerie,
Thanks for your help but my problem is in the service because the response
message seems to be built correctly but at certain moment, there is an
exception and this message is not sent to the client. I use TCPMon and what the
service sends to the client is only the HTTP Header:
HTTP/1.1 200 OK
Server: Apache-Coyote/1.1
Content-Type: application/soap+xml;charset=UTF-8
Transfer-Encoding: chunked
Date: Fri,20 Apr 2007 14:50:37 GMT
102d
Maybe If I resolve this problem I'll need that sentence in my client. So thank
you again.
Regards,
Jorge Fernández
Masin, Valerie [EMAIL PROTECTED] escribió: I have no idea if this helps
but we had trouble with large docs using Sun Webserver and the solution was to
set this on the client:
stub._getServiceClient().getOptions().setProperty(HTTPConstants.CHUNKED,
Constants.VALUE_FALSE);
-
From: Jorge Fernandez [mailto:[EMAIL PROTECTED]
Sent: Monday, April 16, 2007 6:23 PM
To: axis-user
Subject: issue when sending big arrays
Hi all,
I'm having problems when I have to return big arrays. I have an operation in
the web service I'm building for my Career Final Project which returns the xml
code for a class that contains two arrays and an int. One of the arrays is an
short array and usually is very big. The other one has no components in the
tests I did at the moment. I get the following exception in my client:
Exception in thread main java.lang.RuntimeException: Data binding error
at client.Medici_LinkStub.fromOM(Medici_LinkStub.java:5792)
at client.Medici_LinkStub.getPrimitiveData(Medici_LinkStub.java:2678)
at client.ClientUtilities.getPrimitiveDataTest(ClientUtilities.java:336)
at client.Client.main(Client.java:64)
Caused by: org.apache.xmlbeans.XmlException: Unexpected end of input block in
end tag
at [row,col {unknown-source}]: [1,4095]
at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:847)
at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:826)
at
org.apache.xmlbeans.impl.schema.SchemaTypeLoaderBase.parse(SchemaTypeLoaderBase.java:231)
at
medici_link.op_messages.xsd.GetPrimitiveDataResponseDocument$Factory.parse(GetPrimitiveDataResponseDocument.java:163)
at client.Medici_LinkStub.fromOM(Medici_LinkStub.java:5313)
... 3 more
Caused by: com.ctc.wstx.exc.WstxEOFException: Unexpected end of input block in
end tag
at [row,col {unknown-source}]: [1,4095]
at com.ctc.wstx.sr.StreamScanner.throwUnexpectedEOB(StreamScanner.java:675)
at
com.ctc.wstx.sr.StreamScanner.loadMoreFromCurrent(StreamScanner.java:1029)
at
com.ctc.wstx.sr.StreamScanner.getNextCharFromCurrent(StreamScanner.java:786)
at
com.ctc.wstx.sr.BasicStreamReader.readEndElem(BasicStreamReader.java:3204)
at
com.ctc.wstx.sr.BasicStreamReader.nextFromTree(BasicStreamReader.java:2830)
at com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1019)
at
org.apache.axiom.om.impl.llom.OMStAXWrapper.next(OMStAXWrapper.java:917)
at
org.apache.xmlbeans.impl.store.Locale.loadXMLStreamReader(Locale.java:1098)
at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:843)
... 7 more
I tried to find out what was the problem in my web service so I used the
debugger and compared executions with diferent sizes for the array and
everything seems to be alright (the return message appears to be built
correctly) until I reach axisServlet.
In my log file I see:
in axisServlet catch exception: 2007-04-16 22:36:05 ERROR
org.apache.axis2.transport.http.AxisServlet -
java.lang.IllegalStateException: Can't overwrite cause
I think that the method that throws the exception is req.getInputStream() that
is a parameter of HTTPTransportUtils.processHTTPPostRequest.
I started having problems when the array is about 220 components. I would like
to know if there is any limitation on array's sizes.
Thanks and regards,
Jorge Fernández
-
LLama Gratis a cualquier PC del Mundo.
Llamadas a fijos y móviles desde 1 céntimo por minuto.
http://es.voice.yahoo.com
-
LLama Gratis a cualquier PC del Mundo.
Llamadas a fijos y móviles desde 1 céntimo por minuto.
http://es.voice.yahoo.com
Issue with ADB and parsing a response message (namespaces)
Hi all,
I'm having problems with the namespaces of a response message like this:
ns3:getDetailedMonitoringStagesResponse
xmlns:ns3=http://op_messages.medici_link/xsd;
ns3:return
xmlns:ns0=http://external.communication_data_model.medici_link/xsd;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:type=ns0:extConfiguration
..
ns0:abstractParameters xsi:type=ns0:extAbstractParameterDesc
..
/ns0:abstractParameters
..
ns0:primitiveParameters
xsi:type=ns0:extPrimitiveParameterDesc
.
/ns0:primitiveParameters
..
/ns3:return
/ns3:getDetailedMonitoringStagesResponse
/soapenv:Body
/soapenv:Envelope
I have this exception when parsing the first element (ns0:abstractParameters):
java.lang.RuntimeException: java.lang.RuntimeException: Unsupported type null
extPrimitiveParameterDesc
at client.Medici_LinkStub.fromOM(Medici_LinkStub.java:5210)
at
client.Medici_LinkStub.getDetailedMonitoringStages(Medici_LinkStub.java:1945)
at
client.ClientUtilities.getDetailedMonitoringStagesTest(ClientUtilities.java:244)
at client.Client.main(Client.java:53)
Caused by: java.lang.RuntimeException: Unsupported type null
extPrimitiveParameterDesc
at
medici_link.op_messages.xsd.ExtensionMapper.getTypeObject(ExtensionMapper.java:181)
at
medici_link.communication_data_model.external.xsd.ExtParameterDesc$Factory.parse(ExtParameterDesc.java:1171)
at
medici_link.communication_data_model.external.xsd.ExtAbstractParameterDesc$Factory.parse(ExtAbstractParameterDesc.java:1311)
at
medici_link.communication_data_model.external.xsd.ExtConfiguration$Factory.parse(ExtConfiguration.java:923)
at
medici_link.communication_data_model.external.xsd.ExtStage$Factory.parse(ExtStage.java:650)
at
medici_link.op_messages.xsd.GetDetailedMonitoringStagesResponse$Factory.parse(GetDetailedMonitoringStagesResponse.java:424)
at client.Medici_LinkStub.fromOM(Medici_LinkStub.java:4833)
... 3 more
I have a hierachy of classes:
ExtAbstractParameterDesc and ExtPrimitiveParameterDesc that extend
ExtParameterDesc.
I've been diving in my code that was created with WSDL2Java and ADB (Axis
1.1.1) and I could see that for that element, it enters
the parse Method of ExtAbstractParameterDesc, then it reaches this:
if
(true.equals(reader.getAttributeValue(http://www.w3.org/2001/XMLSchema-instance,nil;))){
list9.add(null);
reader.next();
} else {
list9.add(medici_link.communication_data_model.external.xsd.ExtParameterDesc.Factory.parse(reader));
}
And goes to the else statement. So it enters the parse method of
ExtParameterDesc (it's father class).
When it's inside that method, variable type gets the value
ExtPrimitiveParameterDesc (I don't know if it should be
ExtAbstractParameterDesc but I made that change and it threw an exception in
other place) and finally it tries to get the namespace uri of prefix ns0 and it
gets null.
this is the snippet:
java.lang.String type = fullTypeName.substring(fullTypeName.indexOf(:)+1);
if (!extParameterDesc.equals(type)){
//find namespace for the prefix
java.lang.String nsUri =
reader.getNamespaceContext().getNamespaceURI(ns0);
nsUri=http://external.communication_data_model.medici_link/xsd;;
return
(ExtParameterDesc)medici_link.op_messages.xsd.ExtensionMapper.getTypeObject(nsUri,type,reader);
}
As you can see in the message, it is
http://external.communication_data_model.medici_link/xsd;. So the exception is
thrown because it can't get de typeObject.
I added the line
nsUri=http://external.communication_data_model.medici_link/xsd;; just before
getTypeObject is called and it works.
With XMLBeans, it works perfectly.
Regards,
Jorge Fernández
-
LLama Gratis a cualquier PC del Mundo.
Llamadas a fijos y móviles desde 1 céntimo por minuto.
http://es.voice.yahoo.com
XMLBeans, Attachments and Rampart
Hi all, I would like to know if it's possible to use XMLBeans and Rampart with attachtments cos I heard that XMLBeans doesn't support MTOM and I doubt if Rampart supports SwA or there is any problem in that combination. Thanks and regards, Jorge Fernández - LLama Gratis a cualquier PC del Mundo. Llamadas a fijos y móviles desde 1 céntimo por minuto. http://es.voice.yahoo.com
issue when sending big arrays
Hi all,
I'm having problems when I have to return big arrays. I have an operation in
the web service I'm building for my Career Final Project which returns the xml
code for a class that contains two arrays and an int. One of the arrays is an
short array and usually is very big. The other one has no components in the
tests I did at the moment. I get the following exception in my client:
Exception in thread main java.lang.RuntimeException: Data binding error
at client.Medici_LinkStub.fromOM(Medici_LinkStub.java:5792)
at client.Medici_LinkStub.getPrimitiveData(Medici_LinkStub.java:2678)
at client.ClientUtilities.getPrimitiveDataTest(ClientUtilities.java:336)
at client.Client.main(Client.java:64)
Caused by: org.apache.xmlbeans.XmlException: Unexpected end of input block in
end tag
at [row,col {unknown-source}]: [1,4095]
at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:847)
at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:826)
at
org.apache.xmlbeans.impl.schema.SchemaTypeLoaderBase.parse(SchemaTypeLoaderBase.java:231)
at
medici_link.op_messages.xsd.GetPrimitiveDataResponseDocument$Factory.parse(GetPrimitiveDataResponseDocument.java:163)
at client.Medici_LinkStub.fromOM(Medici_LinkStub.java:5313)
... 3 more
Caused by: com.ctc.wstx.exc.WstxEOFException: Unexpected end of input block in
end tag
at [row,col {unknown-source}]: [1,4095]
at com.ctc.wstx.sr.StreamScanner.throwUnexpectedEOB(StreamScanner.java:675)
at
com.ctc.wstx.sr.StreamScanner.loadMoreFromCurrent(StreamScanner.java:1029)
at
com.ctc.wstx.sr.StreamScanner.getNextCharFromCurrent(StreamScanner.java:786)
at
com.ctc.wstx.sr.BasicStreamReader.readEndElem(BasicStreamReader.java:3204)
at
com.ctc.wstx.sr.BasicStreamReader.nextFromTree(BasicStreamReader.java:2830)
at com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1019)
at org.apache.axiom.om.impl.llom.OMStAXWrapper.next(OMStAXWrapper.java:917)
at
org.apache.xmlbeans.impl.store.Locale.loadXMLStreamReader(Locale.java:1098)
at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:843)
... 7 more
I tried to find out what was the problem in my web service so I used the
debugger and compared executions with diferent sizes for the array and
everything seems to be alright (the return message appears to be built
correctly) until I reach axisServlet.
In my log file I see:
in axisServlet catch exception: 2007-04-16 22:36:05 ERROR
org.apache.axis2.transport.http.AxisServlet - java.lang.IllegalStateException:
Can't overwrite cause
I think that the method that throws the exception is req.getInputStream() that
is a parameter of HTTPTransportUtils.processHTTPPostRequest.
I started having problems when the array is about 220 components. I would like
to know if there is any limitation on array's sizes.
Thanks and regards,
Jorge Fernández
-
LLama Gratis a cualquier PC del Mundo.
Llamadas a fijos y móviles desde 1 céntimo por minuto.
http://es.voice.yahoo.com
Re: Problems with inheritance
Hi all, I'm using axis2 1.1.1 and Ihave a problem when generating the wsdl from my Java classes. I use a class PrimitiveParameter that extends from Parameter and in the wsdl they appear as if they were independent. PrimitiveParameter has its own fields and the fields inherited from Parameter but it has no reference to the relationship betwen them. I think there should be something like a restriction base referencing Parameter from PrimitiveParameter. Am I right?? xs:element name=PrimitiveParameter type=ax23:PrimitiveParameter/ xs:complexType name=PrimitiveParameter xs:sequence ... /xs:sequence /xs:complexType xs:element name=Parameter type=ax23:Parameter/ xs:complexType name=Parameter xs:sequence ... /xs:sequence /xs:complexType It's that a known issue??? Thanks in advance, Jorge Fernández - LLama Gratis a cualquier PC del Mundo. Llamadas a fijos y móviles desde 1 céntimo por minuto. http://es.voice.yahoo.com
RE: Null pointer exception in xmlbeans setArray
Update for my previous email. I have the same problem when I build the response message if I have to return null array. When I do responseElement.setReturnArray(array), and the array is null, it Throws a NPE. With other objects I can use a setNil method but arrays only have a method for setting null a component and not the hole array. Can anybody tell me what I'm doing wrong and how should I set a null array?? Thanks and regards, Jorge Fernández Jorge Fernandez [EMAIL PROTECTED] escribió: Hi, I'm using xmlbeans as databinding. In some classes I have Array fields and when I call the setter for those with a null value, I get a null pointer exception but I tried the same with a String field and it works perfectly. Is not possible to set an array to null in xmlbeans classes?? Thanks and regards, Jorge Fernández - LLama Gratis a cualquier PC del Mundo. Llamadas a fijos y móviles desde 1 céntimo por minuto. http://es.voice.yahoo.com - LLama Gratis a cualquier PC del Mundo. Llamadas a fijos y móviles desde 1 céntimo por minuto. http://es.voice.yahoo.com
Null pointer exception in xmlbeans setArray
Hi, I'm using xmlbeans as databinding. In some classes I have Array fields and when I call the setter for those with a null value, I get a null pointer exception but I tried the same with a String field and it works perfectly. Is not possible to set an array to null in xmlbeans classes?? Thanks and regards, Jorge Fernández - LLama Gratis a cualquier PC del Mundo. Llamadas a fijos y móviles desde 1 céntimo por minuto. http://es.voice.yahoo.com
java char mapping for xml
Hi all, When I'd generated my wsdl from my java class I had a char field and I realized that there's no mapping for that in xml so I went to google to find out a way of doing that and I found http://publib.boulder.ibm.com/infocenter/dmndhelp/v6rxmx/index.jsp?topic=/com.ibm.wbit.help.wiring.ui.doc/topics/rref_javatowsdltypemap.html And I tried to modify my wsdl with that code like this: xs:simpleType name=char xs:restriction base=xsd:string xs:length value=1/ /xs:restriction /xs:simpleType xs:element name=extPatient type=ax23:user/ xs:complexType name=user xs:sequence xs:element name=birthDate type=xs:long/ xs:element name=name nillable=true type=xs:string/ xs:element name=patientCode nillable=true type=xs:string/ xs:element name=sex type=ax23:char/ xs:element name=state nillable=true type=xs:string/ xs:element name=surname nillable=true type=xs:string/ /xs:sequence /xs:complexType Where I had: xs:element name=extPatient type=ax23:user/ xs:complexType name=user xs:sequence xs:element name=birthDate type=xs:long/ xs:element name=name nillable=true type=xs:string/ xs:element name=patientCode nillable=true type=xs:string/ xs:element name=sex type=xs:anyType/ xs:element name=state nillable=true type=xs:string/ xs:element name=surname nillable=true type=xs:string/ /xs:sequence /xs:complexType And when I try to generate java code from that wsdl with eclipse plugin 1.2.1 and xmlbeans as databinding I get the following exception: An error ocurred while completing the process -java.lang.InterruptedException: java.lang.RuntimeException java.lang.reflect.InvocationTargetException (I'm using axis2 1.1.1) I'm not an xml expert, so could anybody tell me what I'm doing wrong??, and any other way to do that mapping?? Thanks in advance and regards: Jorge Fernández - LLama Gratis a cualquier PC del Mundo. Llamadas a fijos y móviles desde 1 céntimo por minuto. http://es.voice.yahoo.com
RE: An unsupported token was provided (Problem with SKI information: Support for RSA key only)
Hi Luis,
I'm unsure but maybe the problem is the algorithm with which you generate the
keystore. Default algorithm is DSA and as your error seems to say: Support for
RSA key only as it is really. So I think if you add -keyalg RSA option to the
command to generate the keystore, this problem will dissapear.
This is a tutorial about how keytool works:
http://publib.boulder.ibm.com/html/as400/v5r1/ic2931/index.htm?info/rzaha/keytool.htm
Regards,
Jorge Fernández
Diaz, Luis (GE Comm Fin, non-ge) [EMAIL PROTECTED] escribió: An
unsupported token was provided (Problem with SKI information: Support for RSA
key only) Hello, As you can see I'm new to Axis2, with rampart to Encrypt
a Service.
I'm trying to use the Axis2, with rampart Im getting the following error:
WSHandler: Signature: error during message
procesingorg.apache.ws.security.WSSecurityException: An unsupported token was
provided (Problem with SKI information: Support for RSA key only) , does any
one has a clue on it or a better way to generate a key and/or Encrypt a Service?
This is a link to a sample im doing sample to Encrypt
(http://www-128.ibm.com/developerworks/edu/ws-dw-ws-understand-web-services4.html?S_TACT=105AGX52S_CMP=cn-t-ws)
My key was generated as follows
keytool -genkey -keystore mykeys.jks -alias gene
--
C:\signkeytool -genkey -keystore mykeys.jks -alias gene
Enter keystore password: password
What is your first and last name?
[Unknown]: Gene Telluride
What is the name of your organizational unit?
[Unknown]: Information technologies
What is the name of your organization?
[Unknown]: The Daily Moon
What is the name of your City or Locality?
[Unknown]: NY
What is the name of your State or Province?
[Unknown]: US
What is the two-letter country code for this unit?
[Unknown]: US
Is CN=Gene Telluride, OU=Information technologies, O=The Daily Moon, L=NY,
ST=US, C=US correct?
[no]: yes
Enter key password for gene
(RETURN if same as keystore password):password
--
The following is my security properties file:
org.apache.ws.security.crypto.provider=org.apache.ws.security.components.crypto.Merlin
org.apache.ws.security.crypto.merlin.keystore.type=jks
org.apache.ws.security.crypto.merlin.keystore.password=password
org.apache.ws.security.crypto.merlin.file=mykeys.jks
This is part of my axis code Client code: (Axis2.xml)
module ref=rampart/
parameter name=OutflowSecurity
action
itemsTimestamp Signature/items
usergene/user
passwordCallbackClassPWCallback/passwordCallbackClass
signaturePropFilesecurity.properties/signaturePropFile
signatureKeyIdentifierSKIKeyIdentifier/signatureKeyIdentifier
signatureParts{Element}{http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd}Timestamp/signatureParts
/action
/parameter
parameter name=InflowSecurity
action
itemsTimestamp Signature Encrypt/items
usergene/user
passwordCallbackClassPWCallback/passwordCallbackClass
signaturePropFilesecurity.properties/signaturePropFile
signatureKeyIdentifierSKIKeyIdentifier/signatureKeyIdentifier
encryptionKeyIdentifierSKIKeyIdentifier/encryptionKeyIdentifier
encryptionUsergene/encryptionUser
signatureParts{Element}{http://schemas.xmlsoap.org/soap/envelope/}Body/signatureParts
optimizeParts//xenc:EncryptedData/xenc:CipherValue/xenc:CipherData/optimizeParts
/action
/parameter
Server: (Services.xml)
parameter name=InflowSecurity
action
itemsTimestamp Signature/items
passwordCallbackClassPWCallback/passwordCallbackClass
signaturePropFilesecurity.properties/signaturePropFile
/action
/parameter
parameter name=OutflowSecurity
action
itemsTimestamp Signature Encrypt/items
usergene/user
passwordCallbackClassPWCallback/passwordCallbackClass
signaturePropFilesecurity.properties/signaturePropFile
signatureKeyIdentifierSKIKeyIdentifier/signatureKeyIdentifier
encryptionKeyIdentifierSKIKeyIdentifier/encryptionKeyIdentifier
encryptionUserbob/encryptionUser
signatureParts{Element}{http://schemas.xmlsoap.org/soap/envelope/}Body/signatureParts
optimizeParts//xenc:EncryptedData/xenc:CipherValue/xenc:CipherData/optimizeParts
/action
/parameter
-
LLama Gratis a cualquier PC del Mundo.
Llamadas a fijos y móviles desde 1 céntimo por minuto.
http://es.voice.yahoo.com
RE: Skeleton class not being loaded from the services/MyService.aar file
Hi Nilesh, I'm a newbie and I had the same problem once. I have some questions you can try. Have you tried to deploy it in exploded format??? Maybe this question is obvious: did you look if at the services.xml parameter locked=false name=ServiceClasspackage.class_name/parameter is the same as your package.class_name, with the same folder structure on the service directory?? or even I had some problems when I dropped a class with no package in the service folder so I had to put it on a package and then drop the package in the service folder. Regards, Jorge Fernández Nilesh Ghorpade [EMAIL PROTECTED] escribió: Hi Gurus, I am getting this error. When ever my client tries to execute a web service operation I get the error saying that the Skeleton class was not found. I have verified my aar file and the skeleton class is present in it. The way I am deploying my service is in accordance with the steps suggested by AXIS 2. I have a web application. In this web application I have created a services folder under the WEB-INF directory and placed my Aar file in this directory. I am not using any AXIS.xml configuration file. My AAR file has the WSDL as well as the services.xml configuration file placed in the META-INF directory inside the AAR file. Thanks in advance. Regards Niles - 8:00? 8:25? 8:40? Find a flick in no time with theYahoo! Search movie showtime shortcut. - LLama Gratis a cualquier PC del Mundo. Llamadas a fijos y móviles desde 1 céntimo por minuto. http://es.voice.yahoo.com
Problems with WSDL2Java and Faults
Hi all, I'm having a little problem with generating WSDL from a java class when I throw any fault. The first problem is that in the WSDL generated my fault name is ignored and instead it's compound from the operation name and Fault. The second is that even if I throw two exceptions from one operation, in the WSDL only one appears and with the name compound as I said before. The third question is: I'm using Axis2 1.2.1 eclipse plugin and when I start the wizard I'm asked the name an the path of the class from which I want to build my WSDL. When I extend my fault from AxisFault, I have to specify the library where it's defined but when I extend from Exception I don't need anything. I have an userLibrary Defined in eclipse for Axis2 jar files and that's why I wonder why I need to specify the library manually. I attach the API from where I build the WSDL, the Faults classes and the WSDL generated. Thanks and Regards, Jorge Fernández - LLama Gratis a cualquier PC del Mundo. Llamadas a fijos y móviles desde 1 céntimo por minuto. http://es.voice.yahoo.com API.java Description: 2141036048-API.java IncorrectPasswordFault.java Description: 3066544042-IncorrectPasswordFault.java IncorrectUserFault.java Description: 2315852456-IncorrectUserFault.java API.wsdl Description: 38239204-API.wsdl - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: static final java attributes
Hi Glen,
Thanks for your help. This tutorial is very interesting and I learned many
things about wsdl but it didn't help in my case (or I didn't find the
relationship) because my problem is that I have static final attributes in my
data types like (maybe the sintax is wrong and it makes nosense the code but is
something similar):
public class CodeOperations{
static final int getUserID=1;
static final int getUserName=2;
}
And in my service I have an operation like:
public String operationExample(int codeOperation) throws Exception{
if(codeOperation==CodeOperations.getUserID){
String response=getUserID();
} else if(codeOperation==CodeOperations.getUserName){
String response=getUserName();
}else{
throw new Exception(wrong operation);
}
}
I would like to know how my client can have access to my CodeOperations values
so he knows what are the operations permitted and which values are permitted. I
don't know if this is possible from the wsdl.
thanks and regards
Jorge Fernandez
Glen Mazza [EMAIL PROTECTED] escribió: I'm unsure how much this will help
you, but this tutorial[1], on page 6,
listings 36 and 37, has auxiliary classes which are somehow linked to
allow usage by java2wsdl. It may be similar to what you need--you can
download the tutorial source code to find out.
Glen
[1]
http://www-128.ibm.com/developerworks/edu/ws-dw-ws-understand-web-services2.html
Am Mittwoch, den 07.03.2007, 15:04 +0100 schrieb Jorge Fernandez:
Hi,
I would appreciate a lot if someone can give a hint on this:
I'm building a web service with axis2 1.1.1 and I have some java
classes from which I generate a wsdl but I have some static or final
fields that I use like operation codes and I need the client could
know those specific values so he can send them to my web service. Is
there anyway for doing this??
thanks and regards
Jorge Fernandez
__
LLama Gratis a cualquier PC del Mundo.
Llamadas a fijos y móviles desde 1 céntimo por minuto.
http://es.voice.yahoo.com
-
LLama Gratis a cualquier PC del Mundo.
Llamadas a fijos y móviles desde 1 céntimo por minuto.
http://es.voice.yahoo.com
Re: static final java attributes
Thanks again,
I'll try to modify the wsdl adding enumeration elements,
Regards,
Jorge Fernández
Glen Mazza [EMAIL PROTECTED] escribió: I'm still a web services newbie, but
that doesn't seem standard--having
client code rely on programmatic constructs present in the server code.
The client should not need to be aware of the internal architecture (or
even programming language) of the server.
I wonder if you could use an XML Schema enumeration facet in your
wsdl:types section to declare and limit the acceptable range of
commands. I have not done this before, however.
As for, I would like to know how my client can have access to my
CodeOperations values so he knows what are the operations permitted and
which values are permitted. that seems like a need for UDDI in general,
although it may be overkill for your situation.
Glen
Am Donnerstag, den 08.03.2007, 12:45 +0100 schrieb Jorge Fernandez:
Hi Glen,
Thanks for your help. This tutorial is very interesting and I learned
many things about wsdl but it didn't help in my case (or I didn't find
the relationship) because my problem is that I have static final
attributes in my data types like (maybe the sintax is wrong and it
makes nosense the code but is something similar):
public class CodeOperations{
static final int getUserID=1;
static final int getUserName=2;
}
And in my service I have an operation like:
public String operationExample(int codeOperation) throws Exception{
if(codeOperation==CodeOperations.getUserID){
String response=getUserID();
} else if(codeOperation==CodeOperations.getUserName){
String response=getUserName();
}else{
throw new Exception(wrong operation);
}
}
I would like to know how my client can have access to my
CodeOperations values so he knows what are the operations permitted
and which values are permitted. I don't know if this is possible from
the wsdl.
thanks and regards
Jorge Fernandez
Glen Mazza escribió:
I'm unsure how much this will help you, but this tutorial[1],
on page 6,
listings 36 and 37, has auxiliary classes which are somehow
linked to
allow usage by java2wsdl. It may be similar to what you
need--you can
download the tutorial source code to find out.
Glen
[1]
http://www-128.ibm.com/developerworks/edu/ws-dw-ws-understand-web-services2.html
Am Mittwoch, den 07.03.2007, 15:04 +0100 schrieb Jorge
Fernandez:
Hi,
I would appreciate a lot if someone can give a hint on this:
I'm building a web service with axis2 1.1.1 and I have some
java
classes from which I generate a wsdl but I have some static
or final
fields that I use like operation codes and I need the client
could
know those specific values so he can send them to my web
service. Is
there anyway for doing this??
thanks and regards
Jorge Fernandez
__
LLama Gratis a cualquier PC del Mundo.
Llamadas a fijos y móviles desde 1 céntimo por minuto.
http://es.voice.yahoo.com
__
LLama Gratis a cualquier PC del Mundo.
Llamadas a fijos y móviles desde 1 céntimo por minuto.
http://es.voice.yahoo.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
LLama Gratis a cualquier PC del Mundo.
Llamadas a fijos y móviles desde 1 céntimo por minuto.
http://es.voice.yahoo.com
static final java attributes
Hi, I would appreciate a lot if someone can give a hint on this: I'm building a web service with axis2 1.1.1 and I have some java classes from which I generate a wsdl but I have some static or final fields that I use like operation codes and I need the client could know those specific values so he can send them to my web service. Is there anyway for doing this?? thanks and regards Jorge Fernandez - LLama Gratis a cualquier PC del Mundo. Llamadas a fijos y móviles desde 1 céntimo por minuto. http://es.voice.yahoo.com
RE: TimeZone Not Handled Properly In java.util.Date Conversions
Hi Larry,
I had the same problem. And I was asked to open a JIRA few days ago: AXIS2-2239
regards,
Jorge Fernandez
Johnson, Larry D (LJOHNSON) [EMAIL PROTECTED] escribió:v\:*
{behavior:url(#default#VML);} o\:* {behavior:url(#default#VML);} w\:*
{behavior:url(#default#VML);} .shape {behavior:url(#default#VML);}
st1\:*{behavior:url(#default#ieooui) } Amila,
I finally got some time to test the java.util.Data issue. The SNAPSHOT that
I downloaded seems to take care of the TimeZone issue I originally reported;
however, I have found one additional issue. The generated WSDL for the Date
object is as follows:
xs:element name=flightTime type=xs:dateTime/
Notice there is no nillable attribute on this definition. There are times
when this value may be null and the SOAP message sent has that value set to
null. Here is a snippet from the SOAP message returned:
flightTime xmlns:nil=http://www.w3.org/2001/XMLSchema-instance;
nil:nil=true /
As stated earlier, we are deploying POJOs and generate the stubs using the
Axis2 supplied WSDL2Java processor.
Any thoughts on why the auto-generated WSDL is not including the
nillable=true attribute for this element?
Regards,
Larry Johnson
-
From: Johnson, Larry D (LJOHNSON) [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 22, 2007 11:50 AM
To: axis-user@ws.apache.org
Subject: RE: TimeZone Not Handled Properly In java.util.Date Conversions
Amiila,
We are deploying our service via POJOs. I copied a version of saaj into the
axis2 lib directory and the problem was corrected. I just wanted to let you
know that the SNAPSHOT was not a complete distribution since the team moved to
providing the SOAPEnvelope impl class.
I am still trying to get some time to test the Date issue and hopefully will
get that time today. I will let you know the results.
Regards,
Larry Johnson
-
From: Amila Suriarachchi [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 21, 2007 10:54 PM
To: axis-user@ws.apache.org
Subject: Re: TimeZone Not Handled Properly In java.util.Date Conversions
On 2/21/07, Johnson, Larry D (LJOHNSON) [EMAIL PROTECTED] wrote:
Amila,
I downloaded the axis2-SNAPSHOT.zip distribution and tried to rerun the test.
When the server tries to return the SOAP message, I now receive the following
exception:
Caused by: java.lang.NoClassDefFoundError: javax/xml/soap/SOAPEnvelope
at
com.arinc.afd.clfengine.processor.CommandProcessor.sendCommandToJAGS(Unknown
Source)
at
com.arinc.afd.clfengine.processor.jl.GetSeatAvailabilityProcessorJL.processHostRequest
(Unknown Source)
Digging into a little shows that in this SNAPSHOT, the
axis2-saaj-SNAPSHOT.jar file no longer contains a SOAPEvelope class; however,
it does contain a SOAPEnvelopeImpl class. This impl class references the
javax.xml.soap.SOAPEvelope class from the standard saaj distribution; however,
saaj was not provided within the distribution.
I deployed the SNAPSHOT by downloading the archive and then exploding it.
Once expanded, I build the WAR file by going into the
{path.to.axis2}/axis2-SNAPSHOT/webapp and issuing the following command: 'ant'.
The resulting axis2.war was built without error and was found residing in the
'dist' directory. The WAR file was then moved into the Tomcat 'webapps'
directory (after removing the prior distribution).
Can you explain how you create your service as well. I hope you creating it
with a POJO class. Then that
Caused by: java.lang.NoClassDefFoundError: javax/xml/soap/SOAPEnvelope is not
most probably relates to saaj. but it may be an OM problem. Can you please send
your wsdl or POJO then I can have a try.
--
Amila Suriarachchi,
WSO2 Inc.
-
LLama Gratis a cualquier PC del Mundo.
Llamadas a fijos y móviles desde 1 céntimo por minuto.
http://es.voice.yahoo.com
Re: [AXIS2] Error when executing Java2WSDL
Hi,
I had the same problem and apparently was because I had operations
with the same name but different number or type of parameters as
allowed in Java.
I have a question: When I extend a class, shouldn't the wsdl use the extension
base
or restriction base characteristic from xml, should it?
It's because I have few classes that extend from another and
I have a huge document because those attributes appear again and again.
And other little problem I get is that the wsdl omits java attributes if they
don't
have a get...() or is..() method and also if I have a method started with get,
it extracts
the name of the method for creating an attribute.
The last thing is that xml nillable attribute doesn't appear sometimes for
java attributes even if I initialize that attribute in the declaration with a
null value.
Like this
public class configuration {
private Date end =null;
public Date getEnd(){
return end;
}
public void setEnd(Date _end){
end = new Date(_end.getTime());
}
}
xs:element name=configuration type=ax29:configuration/
xs:complexType name=configuration
xs:sequence
xs:element name=end type=xs:dateTime/
/xs:sequence
/xs:complexType
Thanks
Jorge Fernández
Hi Wen,
http://ws.apache.org/axis2/tools/1_1/eclipse/wsdl2java-plugin.html#operation2
Please make sure that you have included all the dependent classes/jars in
the page2 of the wizards.
Thanks
Lahiru Sandakith.
On 1/31/07, W.Y. Ho [EMAIL PROTECTED] wrote:
It's a Java2WSDL, Not WSDL2Java, it supposed to generate a WSDL file. It
starts from service implementation class.
BTW, I downloaded 1.1.1 already and still got the same error.
Thanks,
wen
*Anne Thomas Manes [EMAIL PROTECTED]* wrote:
Are you certain that the WSDL is valid?
Keep in mind that Axis2 does not support rpc/encoded.
Also, please make sure you are using Axis2 1.1.1.
Anne
On 1/30/07, Ho, Wen Yue wrote:
Hi,
I've got the following error when executing Java2WSDL using AXIS2
CodeGen wizard (eclipse plugin):
an error occurred while completing process
-java.lang.reflect.InvocationTargetException
Please kindly assist.
Thanks in advance,
wen
NOTICE OF CONFIDENTIALITY
This communication including any information transmitted with it is
intended only for the use of the addressees and is confidential.
If you are not an intended recipient or responsible for delivering
the message to an intended recipient, any review, disclosure,
conversion to hard copy, dissemination, reproduction or other use
of any part of this communication is strictly prohibited, as is the
taking or omitting of any action in reliance upon this communication.
If you receive this communication in error or without authorization
please notify us immediately by return e-mail or otherwise and
permanently delete the entire communication from any computer,
disk drive, or other storage medium.
If the above disclaimer is not properly readable, it can be found at
www.td.com/legal
AVERTISSEMENT DE CONFIDENTIALITE
Ce courriel, ainsi que tout renseignement ci-inclus, destiné uniquement
aux destinataires susmentionnés, est confidentiel. Si vous
n'êtes pas le destinataire prévu ou un agent responsable de la
livraison de ce courriel, tout examen, divulgation, copie, impression,
reproduction, distribution, ou autre utilisation d'une partie de ce
courriel est strictement interdit de même que toute intervention ou
abstraction à cet égard. Si vous avez reçu ce message par erreur ou
sans autorisation, veuillez en aviser immédiatement l'expéditeur par
retour de courriel ou par un autre moyen et supprimer immédiatement
cette communication entière de tout système électronique.
Si l'avis de non-responsabilité ci-dessus n'est pas lisible, vous
pouvez le consulter à www.td.com/francais/legale
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Now you can have a huge leap forward in email:* get the new Yahoo! \
Mail.*http://us.rd.yahoo.com/evt=40705/*http://mrd.mail.yahoo.com/try_beta?.intl=ca
\
-
LLama Gratis a cualquier PC del Mundo.
Llamadas a fijos y móviles desde 1 céntimo por minuto.
http://es.voice.yahoo.com
