Re: [axis2] question about return objects]
Hi ...
Im new in web services, im installing axis2c v0.96 in apache2 v2.2.0 and suse
linux
v10.1; compilling the distribution source and have a error :
/var/log/apache2/error_log
apache/2.2.0 (linux/suse) configured -- resuming normal operation
child 5894 returned a fatal error ... apache is exiting
starting log with log level 4
internal error: [axis2 ] error creating mod_axis2 apache2 worker
you have any idea this error ???
SALU2.
Javier A. Casasola Sánchez
El estudio es el camino del triunfo
On Mie Ene 17 17:34 , Nicholas Hart [EMAIL PROTECTED] sent:
I'm building a C client using axis2's wsdl2java and have some questions
about the code it generates (the flags I'm using are: -l c -a -u -d adb
-uri myfile.wsdl).
first, it looks like there are no classes generated for the return
objects. is that expected? it appears to create a class for a request
and a response. although the response class has a get_FooReturn()
function, it looks like it merely returns an axiom_node_t*, not an
object with various getters/setters for the return value's data members.
So it looks like I need to write a bunch of code to parse the
return--and I had hoped axis2 would handle that.
second, I get a ton of warnings like this:
Jan 16, 2007 11:46:27 AM org.apache.axis2.schema.SchemaCompiler
findClassName
WARNING: Type {http://my.namespace.com}ArrayOf_xsd_string missing!
and:
Jan 16, 2007 11:19:20 AM org.apache.axis2.schema.SchemaCompiler
findClassName
WARNING: Type {urn:mynamespace}MyFooBarList missing!
So I'm wondering if there's a problem with the WSDL that is preventing
the code generator from creating the return objects (eg: maybe it skips
generating any objects that contain types that aren't properly definied?).
Anyhow, I'd really appreciate some feedback on this.
Thanks!
(PS: I would love to attach the WSDL, but unfortunately it contains info
I can't release to the public. I'm trying to create a trivial example
WSDL that exhibits these problems and will post it if I'm successful).
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
FLAGS (\Seen))
__
Visita http://www.tutopia.com y comienza a navegar más rápido en Internet.
Tutopia es Internet para todos.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[Axis2c] Build Error
hi, I get this error when I try to`make` in the source directory. The env var AXIS2C_HOME is also set. make[2]: Leaving directory `/home/vijesh/Axis2C/axis2c-src-0.96/ides' make[2]: Entering directory `/home/vijesh/Axis2C/axis2c-src-0.96' /bin/sh ./libtool --tag=CC --mode=link gcc -g -O2 -D_LARGEFILE64_SOURCE -ansi -Wall -Wno-implicit-function-declaration -DAXIS2_SVR_MULTI_THREADED -lpthread -o output-lz -ldl mkdir .libs gcc -g -O2 -D_LARGEFILE64_SOURCE -ansi -Wall -Wno-implicit-function-declaration -DAXIS2_SVR_MULTI_THREADED -o output -lpthread -lz -ldl /usr/lib/gcc/i586-suse-linux/4.1.0/../../../crt1.o: In function `_start': init.c:(.text+0x18): undefined reference to `main' collect2: ld returned 1 exit status make[2]: *** [output] Error 1 make[2]: Leaving directory `/home/vijesh/Axis2C/axis2c-src-0.96' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/vijesh/Axis2C/axis2c-src-0.96' make: *** [all] Error 2 Any help on this regard. Thanks Vijesh
Re: SOAP11, SCHEMA_1999
hi
i thought this should be simple to solve for someone working with axis some
longer time as i just started using axis this week. anyway i've solved it
myself:
1. i needed no GenericHandler overriding (no custom handler)
2. i needed to register the type:
QName xmlType = new
QName(http://schemas.xmlsoap.org/soap/encoding/;, base64);
mapping.register(byte[].class,
new QName(http://schemas.xmlsoap.org/soap/encoding/;, base64),
new Base64SerializerFactory(byte[].class, xmlType),
new Base64DeserializerFactory(byte[].class, xmlType));
registry.register(http://schemas.xmlsoap.org/soap/encoding/;, mapping);
anyway, i think this is a bit weird solution. or?
:-)
On Wednesday 17 January 2007 18:56, M.Zdila/EpiSoftware Ltd. wrote:
Hello
I've googled, but found nothing :-(
I need to communicate with client's web service that supports SOAP 1.1,
schema version 1999. What I need to achieve is to serialize base64 data as
xsi:type=SOAP-ENC:base64 but unfortunately the request still contains
xsi:type=soapenc:base64Binary.
I am using spring remoting with following handler with no help:
import javax.xml.namespace.QName;
import javax.xml.rpc.handler.GenericHandler;
import javax.xml.rpc.handler.MessageContext;
import org.apache.axis.Constants;
import org.apache.axis.schema.SchemaVersion;
public class MyHandler extends GenericHandler {
@Override
public QName[] getHeaders() {
return null;
}
@Override
public boolean handleRequest(MessageContext context) {
((org.apache.axis.MessageContext)
context).setSchemaVersion(SchemaVersion.SCHEMA_1999);
((org.apache.axis.MessageContext)
context).setEncodingStyle(Constants.URI_SOAP11_ENC);
return true;
// return super.handleRequest(context);
}
}
Thanks in advance!
--
Martin Zdila
Analyst/Developer
EpiSoftware Slovakia Ltd.
Letna 27, 043 14 Kosice
tel:+421-908-363-848
tel:+421-55-6770-420
mailto:[EMAIL PROTECTED]
http://www.episoftware.com
xmpp:[EMAIL PROTECTED]
callto://m.zdila/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: wsa:To and wsa:From, etc.. are missing in the SOAP header
Gul, have you engaged the addressing module on the client side? Michele On 17 Jan 2007, at 22:16, Gul Onural wrote: I am using ServiceClient's addHeader method to add header to my SOAP messages on my client. But I don't see the following block of elements (wsa:MessageID, wsa:To, wsa:Action, wsa:From, Address,...) in the header. I thought they would be automatically added by the ws addressing. What else I need to do to get them in the header ? soapenv:Header wsa:MessageID soapenv:mustUnderstand=0 urn:uuid:920C5190-0B8F-11D9-8CED-F22EDEEBF7E5/ wsa:MessageID wsa:To soapenv:mustUnderstand=0http://localhost:8081/ axis/services/BankPort/wsa:To wsa:Actionurn:DummyWSAAction/wsa:Action wsa:From soapenv:mustUnderstand=0 Addresshttp://schemas.xmlsoap.org/ws/2004/03/ addressing/role/anonymous/Address /wsa:From /soapenv:Header
[Axis2] Kandula2
Hello, I am interested to know what is the current status of Kandula2 ? Is there a buildable module which is ready to use, and to what extent does it cover the specs (Atomic Transaction and WS Coordination? Thank you very much in advance. Best Regards, Tobias
Re: [Axis2] [rampart] Problems using rampart
Hi Dimuthu, Thanks for the hint... The SOAP messages I use are really simple. There is nothing special I think. It is something like that: ?xml version='1.0' encoding='utf-8'? soapenv:Envelope xmlns:wsa=http://www.w3.org/2005/08/addressing; xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Header wsa:Tohttp://localhost:3003/axis2/services/MessagingClientService/wsa:To wsa:ReplyTo wsa:Addresshttp://www.w3.org/2005/08/addressing/anonymous/wsa:Address /wsa:ReplyTo wsa:MessageIDurn:uuid:8655FCF2CBB79A97C711691163447531/wsa:MessageID wsa:Actionurn:addClient/wsa:Action /soapenv:Header soapenv:Body ns2:addClient xmlns:ns2=http://www.hpi.uni-potsdam.de/skid.common/wsmessaging/types; ns2:agentNametest/ns2:agentName ns2:classNameskid.agent.test.TestAgent/ns2:className ns2:configPathmessaging_test.config/ns2:configPath ns2:messageFactoryClassName / /ns2:addClient /soapenv:Body /soapenv:Envelope Maybe you have any ideas. Please write when you have suggestions... Regards, Sebastian Dimuthu Leelaratne schrieb: Hi Sebastian, This is not a rampart problem. The pointed out JIRA shows the bug. I walked through the stack trace. This happens for specific SOAP messages, when they are converted to DOOM as mentioned. I have never experienced the problem. Maybe because the SOAP messages that I use wouldn't re-create the problem. Regards, Dimuthu On 1/17/07, Sebastian Roschke [EMAIL PROTECTED] wrote: Hi everybody, I have a problem using rampart in axis2. I just have configured the axis2-client.xml this way, that it should use rampart. At the moment I have no configuration for the rampart module at all. While using the client api to invoke a soap request, I get the following exceptions: org.apache.axis2.AxisFault: Error in extracting message properties; nested exception is: org.apache.rampart.RampartException: Error in extracting message properties at org.apache.rampart.handler.RampartSender.invoke(RampartSender.java:65) at org.apache.axis2.engine.Phase.invoke(Phase.java:381) at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:518) at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:651) at org.apache.axis2.description.OutOnlyAxisOperationClient.execute(OutOnlyAxisOperation.java:353) at skid.messaging.ws.client.client.MessagingClientServiceStub.addClient(MessagingClientServiceStub.java:126) at skid.messaging.client.ClientControl.main(ClientControl.java:55) Caused by: org.apache.rampart.RampartException: Error in extracting message properties at org.apache.rampart.RampartMessageData.init(RampartMessageData.java:294) at org.apache.rampart.MessageBuilder.build(MessageBuilder.java:56) at org.apache.rampart.handler.RampartSender.invoke(RampartSender.java:59) ... 6 more Caused by: org.apache.ws.security.WSSecurityException: Error in converting SOAP Envelope to Document; nested exception is: org.apache.axiom.om.OMException: javax.xml.stream.XMLStreamException at org.apache.rampart.util.Axis2Util.getDocumentFromSOAPEnvelope(Axis2Util.java:121) at org.apache.rampart.RampartMessageData.init(RampartMessageData.java:146) ... 8 more Caused by: org.apache.axiom.om.OMException: javax.xml.stream.XMLStreamException at org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:199) at org.apache.axiom.om.impl.dom.NodeImpl.build(NodeImpl.java:469) at org.apache.axiom.om.impl.dom.DocumentImpl.build(DocumentImpl.java:476) at org.apache.rampart.util.Axis2Util.getDocumentFromSOAPEnvelope(Axis2Util.java:107) ... 9 more Caused by: javax.xml.stream.XMLStreamException at org.apache.axiom.om.impl.llom.OMStAXWrapper.updateLastNode(OMStAXWrapper.java:952) at org.apache.axiom.om.impl.llom.OMStAXWrapper.next(OMStAXWrapper.java:913) at org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:116) ... 12 more This exception is thrown when invoking the first request on the stub. I can find the following link concerning that problem: http://www.mail-archive.com/axis-dev@ws.apache.org/msg25582.html As proposed in this post I should check wether the soap message includes MIME parts. I used MIME parts in former times, but at the moment I disabled all MTOM related things. Do you have any suggestions concernings this problem? Is it a known problem or a bug? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] signature.asc Description: OpenPGP digital signature
Re: [Axis2] Session Management and WS-Addressing
Hello, Please open a jira and post the service that you are trying to use there. Cheers Brian DePradine Web Services Development IBM Hursley External +44 (0) 1962 816319 Internal 246319 If you can't find the time to do it right the first time, where will you find the time to do it again? Tim, Jane and Chelsea Johnson [EMAIL PROTECTED] wrote on 17/01/2007 22:41:01: Thanks for replying. Yes, I read that article. That is why I am stumped as to why my service doesn't response with the correct headers when the client calls it the first time with the correct WS- Addressing headers. Do I have to build the WS-Addressing headers by hand or should Axis2 build them for me automatically? When you deploy a service in SOAP session and when a client tries to access the service in the first time, Axis2 will generate serviceGroupId and send that to the client as a reference parameter in wsa:ReplyTo, as shown below: wsa:ReplyTo wsa:Address http://www.w3.org/2005/08/addressing/anonymous /wsa:Address wsa:ReferenceParameters axis2:ServiceGroupId xmlns:axis2= http://ws.apache.org/namespaces/axis2; urn:uuid:65E9C56F702A398A8B11513011677354 /axis2:ServiceGroupId /wsa:ReferenceParameters /wsa:ReplyTo If the client wants to live in the same session, he has to copy that reference parameter and send it back to the server when he invokes the service the second time. As long as a client sends the valid serviceGroupId, he can use the same session, and the service can maintain the session-related data. Unlike a request session, a SOAP session has a default timeout period, so if the client does not touch the service for 30 seconds, the session will expire, and if the client sends the old serviceGroupId, he will get an AxisFault too. - Original Message - From: Brian De Pradine To: axis-user@ws.apache.org Sent: Wednesday, January 17, 2007 7:52 AM Subject: Re: [Axis2] Session Management and WS-Addressing Hello, You may find the following link useful, [1] [1] http://www.developer.com/java/web/article.php/3620661 Cheers Brian DePradine Web Services Development IBM Hursley External +44 (0) 1962 816319 Internal 246319 If you can't find the time to do it right the first time, where will you find the time to do it again? Tim, Jane and Chelsea Johnson [EMAIL PROTECTED] wrote on 17/01/2007 00:54:12: I am running the latest version of axis2 - 1.1.1. I am trying to use session management via WS-Addressing. In soapmonitor I can see the WS-Addressing headers going out on the request to the server. But my service's response doesn't have any of the WS-Addressing headers (specifically the groupID header). Addressing is enabled globally via the entry in Axis2.xml. In service.xml I set scope for the service to be soapsession. This is what the client is sending. Is there something I need to add or change to get the service to re-act with WS-Addressing headers. ?xml version='1.0' encoding='utf-8'? soapenv:Envelope xmlns:wsa=http://www.w3.org/2005/08/addressing; xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Header wsa:Tohttp://localhost:8080/axis2/services/AiMessageServices/wsa:To wsa:ReplyTo wsa:Addresshttp://www.w3. org/2005/08/addressing/anonymous/wsa:Address /wsa:ReplyTo wsa:MessageIDurn:uuid:F18B205BFF468A597911689950656872/wsa:MessageID wsa:Actionurn:login/wsa:Action /soapenv:Header soapenv:Body Reqx HID124/HID CID2567/CID ReqNoSJPC120.y/ReqNo CRYR2003/CRYR /Reqx /soapenv:Body /soapenv:Envelope - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: error in generated classes in axis2 1.1.1
is it alright if I copy my wsdl here?
Seems the schema is valid:
---
Schema validating with XSV 2.10-1 of 2005/04/22 13:10:49
* Target: http://server.com/services/SapidSetting.asmx?WSDL
(Real name: http://server.com/services/SapidSetting.asmx?WSDL
Length: 4483 bytes
Server: Microsoft-IIS/6.0)
* docElt: {http://schemas.xmlsoap.org/wsdl/}definitions
* Validation was strict, starting with type
{http://schemas.xmlsoap.org/wsdl/}:tDefinitions
* The schema(s) used for schema-validation had
no errors
* No schema-validity problems were found in the target
---
and here is the schema:
---
?xml version=1.0 encoding=utf-8?
wsdl:definitions xmlns:http=http://schemas.xmlsoap.org/wsdl/http/;
xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/;
xmlns:s=http://www.w3.org/2001/XMLSchema;
xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/;
xmlns:tns=https://y.mirago.com/Services/SapIdSetting;
xmlns:tm=http://microsoft.com/wsdl/mime/textMatching/;
xmlns:mime=http://schemas.xmlsoap.org/wsdl/mime/;
targetNamespace=https://y.mirago.com/Services/SapIdSetting;
xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/;
wsdl:types
s:schema elementFormDefault=qualified
targetNamespace=https://y.mirago.com/Services/SapIdSetting;
s:element name=UpdateSapId
s:complexType
s:sequence
s:element minOccurs=1 maxOccurs=1 name=Input
type=tns:SetSapIdRequest /
/s:sequence
/s:complexType
/s:element
s:complexType name=SetSapIdRequest
s:sequence
s:element minOccurs=0 maxOccurs=1 form=unqualified
name=username type=s:string /
s:element minOccurs=0 maxOccurs=1 form=unqualified
name=SapId type=s:string /
/s:sequence
/s:complexType
s:element name=UpdateSapIdResponse
s:complexType
s:sequence
s:element minOccurs=1 maxOccurs=1
name=UpdateSapIdResult type=tns:simpleSuccessResponse /
/s:sequence
/s:complexType
/s:element
s:complexType name=simpleSuccessResponse
s:sequence
s:choice minOccurs=1 maxOccurs=1
s:element minOccurs=0 maxOccurs=1
name=simpleSuccessResponse /
s:element minOccurs=1 maxOccurs=1 form=unqualified
name=success type=s:boolean /
s:element minOccurs=1 maxOccurs=1 form=unqualified
name=error type=tns:errorResponseType /
/s:choice
/s:sequence
/s:complexType
s:complexType name=errorResponseType
s:sequence
s:element minOccurs=0 maxOccurs=1 form=unqualified
name=code type=s:string /
s:element minOccurs=0 maxOccurs=1 form=unqualified
name=description type=s:string /
s:element minOccurs=0 maxOccurs=1 form=unqualified
name=message type=s:string /
/s:sequence
/s:complexType
s:element name=authentication type=tns:authentication /
s:complexType name=authentication
s:sequence
s:element minOccurs=0 maxOccurs=1 form=unqualified
name=userName type=s:string /
s:element minOccurs=1 maxOccurs=1 form=unqualified
name=Password nillable=true type=s:string /
/s:sequence
/s:complexType
/s:schema
/wsdl:types
wsdl:message name=UpdateSapIdSoapIn
wsdl:part name=parameters element=tns:UpdateSapId /
/wsdl:message
wsdl:message name=UpdateSapIdSoapOut
wsdl:part name=parameters element=tns:UpdateSapIdResponse /
/wsdl:message
wsdl:message name=UpdateSapIdauthentication
wsdl:part name=authentication element=tns:authentication /
/wsdl:message
wsdl:portType name=SapIdSettingSoap
wsdl:operation name=UpdateSapId
wsdl:input message=tns:UpdateSapIdSoapIn /
wsdl:output message=tns:UpdateSapIdSoapOut /
/wsdl:operation
/wsdl:portType
wsdl:binding name=SapIdSettingSoap type=tns:SapIdSettingSoap
soap:binding transport=http://schemas.xmlsoap.org/soap/http;
style=document /
wsdl:operation name=UpdateSapId
soap:operation
soapAction=https://y.mirago.com/Services/SapIdSetting/UpdateSapId;
style=document /
wsdl:input
soap:body use=literal /
soap:header message=tns:UpdateSapIdauthentication
part=authentication use=literal /
/wsdl:input
wsdl:output
soap:body use=literal /
soap:header message=tns:UpdateSapIdauthentication
part=authentication use=literal /
/wsdl:output
/wsdl:operation
/wsdl:binding
wsdl:service name=SapIdSetting
wsdl:port name=SapIdSettingSoap binding=tns:SapIdSettingSoap
soap:address
location=http://keywords.yelldirect.com/services/SapidSetting.asmx;
/
/wsdl:port
/wsdl:service
/wsdl:definitions
Re: [Axis2] wsdl2java / Axis2 : Is namespace / prefix handling in SOAP messages configurable?
Rainer, .Net has no problem dealing with explicit versus default namespace declarations. My guess is that the problem is caused by the fact that .NET doesn't support RPC/Literal. Rather than using RPC style, you should use the wrapped document/literal style. You just have to wrap your parameters with a wrapper element. See my blog post on the topic: http://atmanes.blogspot.com/2005/03/wrapped-documentliteral-convention.html Anne On 1/18/07, Rainer Menzner [EMAIL PROTECTED] wrote: Hi, up to now I had a web-service implemented in Axis2 along with a client written in .Net 2 C# up and running successfully. I use wsdl2java and wsdl.exe in order to create the server and client stubs. The WSDL used Document/literal SOAP. Now I had to extend some messages to multiple parts, which enforced using RPC/literal SOAP. And now, I run into a problem: Axis2 generates SOAP-messages that use a namespace prefix e.g., ?xml version='1.0' encoding='utf-8'? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Header / soapenv:Body ns1:ReRegisterResponse xmlns:ns1=http://www.company.com/Communication/1/0/; ReRegisterResult ns1:ClientGuid12EA746B95AE57CEFFB11D6FA22D9400/ns1:ClientGuid /ReRegisterResult /ns1:ReRegisterResponse /soapenv:Body /soapenv:Envelope By contrast, WSDL.exe-stub generates messages that define the namespace within an attribute, e.g. ?xml version='1.0' encoding='utf-8'? soap:Envelope xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xmlns:xsd=http://www.w3.org/2001/XMLSchema; soap:Body ReRegister xmlns=http://www.company.com/Communication/1/0/api/; ReRegisterParam xmlns= ClientIdentifier xmlns=http://www.identix.com/Communication/1/0/;testclient/ClientIdentifier ClientSign xmlns=http://www.company.com/Communication/1/0/; / RetainClaimedData xmlns=http://www.company.com/Communication/1/0/;true/RetainClaimedData /ReRegisterParam /ReRegister /soap:Body /soap:Envelope Now, Axis2 obviously can handle both formats correctly, messages arrive and are processed properly. But the .Net stub is not able to decode the message that uses the namespace-prefix format. As a result I receive a null pointer message. Hence my question, can Axis2 be configured how to layout the newly created messages? I don't know which format is the best or if one is not allowed at all. Axis2 format using namespace-prefix is more compact. Thanks and best regards, -Rainer - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: error in generated classes in axis2 1.1.1
Im getting some ewrror messages when it tries to interpret the
response from the server:
Caused by: java.lang.RuntimeException: Unexpected subelement error
at
com.mirago.y.services.sapidsetting.SimpleSuccessResponse$Factory.parse(SimpleSuccessResponse.java:243)
I had this classes generated before using an older version which work
with this response from the webservice.
I think the problem is because i had to change the classes that
refered to the parentQName that is present also as a property of the
inner classe's parent. I generated directly using axis 1.1.1 with a
valid wsdl, and got the error i had below (in the previous email).
Could anyone give me a hin ton this?
On 18/01/07, emerson cargnin [EMAIL PROTECTED] wrote:
is it alright if I copy my wsdl here?
Seems the schema is valid:
---
Schema validating with XSV 2.10-1 of 2005/04/22 13:10:49
* Target: http://server.com/services/SapidSetting.asmx?WSDL
(Real name: http://server.com/services/SapidSetting.asmx?WSDL
Length: 4483 bytes
Server: Microsoft-IIS/6.0)
* docElt: {http://schemas.xmlsoap.org/wsdl/}definitions
* Validation was strict, starting with type
{http://schemas.xmlsoap.org/wsdl/}:tDefinitions
* The schema(s) used for schema-validation had
no errors
* No schema-validity problems were found in the target
---
and here is the schema:
---
?xml version=1.0 encoding=utf-8?
wsdl:definitions xmlns:http=http://schemas.xmlsoap.org/wsdl/http/;
xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/;
xmlns:s=http://www.w3.org/2001/XMLSchema;
xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/;
xmlns:tns=https://y.mirago.com/Services/SapIdSetting;
xmlns:tm=http://microsoft.com/wsdl/mime/textMatching/;
xmlns:mime=http://schemas.xmlsoap.org/wsdl/mime/;
targetNamespace=https://y.mirago.com/Services/SapIdSetting;
xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/;
wsdl:types
s:schema elementFormDefault=qualified
targetNamespace=https://y.mirago.com/Services/SapIdSetting;
s:element name=UpdateSapId
s:complexType
s:sequence
s:element minOccurs=1 maxOccurs=1 name=Input
type=tns:SetSapIdRequest /
/s:sequence
/s:complexType
/s:element
s:complexType name=SetSapIdRequest
s:sequence
s:element minOccurs=0 maxOccurs=1 form=unqualified
name=username type=s:string /
s:element minOccurs=0 maxOccurs=1 form=unqualified
name=SapId type=s:string /
/s:sequence
/s:complexType
s:element name=UpdateSapIdResponse
s:complexType
s:sequence
s:element minOccurs=1 maxOccurs=1
name=UpdateSapIdResult type=tns:simpleSuccessResponse /
/s:sequence
/s:complexType
/s:element
s:complexType name=simpleSuccessResponse
s:sequence
s:choice minOccurs=1 maxOccurs=1
s:element minOccurs=0 maxOccurs=1
name=simpleSuccessResponse /
s:element minOccurs=1 maxOccurs=1 form=unqualified
name=success type=s:boolean /
s:element minOccurs=1 maxOccurs=1 form=unqualified
name=error type=tns:errorResponseType /
/s:choice
/s:sequence
/s:complexType
s:complexType name=errorResponseType
s:sequence
s:element minOccurs=0 maxOccurs=1 form=unqualified
name=code type=s:string /
s:element minOccurs=0 maxOccurs=1 form=unqualified
name=description type=s:string /
s:element minOccurs=0 maxOccurs=1 form=unqualified
name=message type=s:string /
/s:sequence
/s:complexType
s:element name=authentication type=tns:authentication /
s:complexType name=authentication
s:sequence
s:element minOccurs=0 maxOccurs=1 form=unqualified
name=userName type=s:string /
s:element minOccurs=1 maxOccurs=1 form=unqualified
name=Password nillable=true type=s:string /
/s:sequence
/s:complexType
/s:schema
/wsdl:types
wsdl:message name=UpdateSapIdSoapIn
wsdl:part name=parameters element=tns:UpdateSapId /
/wsdl:message
wsdl:message name=UpdateSapIdSoapOut
wsdl:part name=parameters element=tns:UpdateSapIdResponse /
/wsdl:message
wsdl:message name=UpdateSapIdauthentication
wsdl:part name=authentication element=tns:authentication /
/wsdl:message
wsdl:portType name=SapIdSettingSoap
wsdl:operation name=UpdateSapId
wsdl:input message=tns:UpdateSapIdSoapIn /
wsdl:output message=tns:UpdateSapIdSoapOut /
/wsdl:operation
/wsdl:portType
wsdl:binding name=SapIdSettingSoap type=tns:SapIdSettingSoap
soap:binding transport=http://schemas.xmlsoap.org/soap/http;
style=document /
wsdl:operation name=UpdateSapId
Re: error in generated classes in axis2 1.1.1
The SimpleSuccessResponse element has no type definition, therefore it
defaults to type=xsd:anyType. I recommend that you define a type for
it. If your intent is to have no content in this element, then define
it a xsd:complexType/.
Anne
On 1/18/07, emerson cargnin [EMAIL PROTECTED] wrote:
Im getting some ewrror messages when it tries to interpret the
response from the server:
Caused by: java.lang.RuntimeException: Unexpected subelement error
at
com.mirago.y.services.sapidsetting.SimpleSuccessResponse$Factory.parse(SimpleSuccessResponse.java:243)
I had this classes generated before using an older version which work
with this response from the webservice.
I think the problem is because i had to change the classes that
refered to the parentQName that is present also as a property of the
inner classe's parent. I generated directly using axis 1.1.1 with a
valid wsdl, and got the error i had below (in the previous email).
Could anyone give me a hin ton this?
On 18/01/07, emerson cargnin [EMAIL PROTECTED] wrote:
is it alright if I copy my wsdl here?
Seems the schema is valid:
---
Schema validating with XSV 2.10-1 of 2005/04/22 13:10:49
* Target: http://server.com/services/SapidSetting.asmx?WSDL
(Real name: http://server.com/services/SapidSetting.asmx?WSDL
Length: 4483 bytes
Server: Microsoft-IIS/6.0)
* docElt: {http://schemas.xmlsoap.org/wsdl/}definitions
* Validation was strict, starting with type
{http://schemas.xmlsoap.org/wsdl/}:tDefinitions
* The schema(s) used for schema-validation had
no errors
* No schema-validity problems were found in the target
---
and here is the schema:
---
?xml version=1.0 encoding=utf-8?
wsdl:definitions xmlns:http=http://schemas.xmlsoap.org/wsdl/http/;
xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/;
xmlns:s=http://www.w3.org/2001/XMLSchema;
xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/;
xmlns:tns=https://y.mirago.com/Services/SapIdSetting;
xmlns:tm=http://microsoft.com/wsdl/mime/textMatching/;
xmlns:mime=http://schemas.xmlsoap.org/wsdl/mime/;
targetNamespace=https://y.mirago.com/Services/SapIdSetting;
xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/;
wsdl:types
s:schema elementFormDefault=qualified
targetNamespace=https://y.mirago.com/Services/SapIdSetting;
s:element name=UpdateSapId
s:complexType
s:sequence
s:element minOccurs=1 maxOccurs=1 name=Input
type=tns:SetSapIdRequest /
/s:sequence
/s:complexType
/s:element
s:complexType name=SetSapIdRequest
s:sequence
s:element minOccurs=0 maxOccurs=1 form=unqualified
name=username type=s:string /
s:element minOccurs=0 maxOccurs=1 form=unqualified
name=SapId type=s:string /
/s:sequence
/s:complexType
s:element name=UpdateSapIdResponse
s:complexType
s:sequence
s:element minOccurs=1 maxOccurs=1
name=UpdateSapIdResult type=tns:simpleSuccessResponse /
/s:sequence
/s:complexType
/s:element
s:complexType name=simpleSuccessResponse
s:sequence
s:choice minOccurs=1 maxOccurs=1
s:element minOccurs=0 maxOccurs=1
name=simpleSuccessResponse /
s:element minOccurs=1 maxOccurs=1 form=unqualified
name=success type=s:boolean /
s:element minOccurs=1 maxOccurs=1 form=unqualified
name=error type=tns:errorResponseType /
/s:choice
/s:sequence
/s:complexType
s:complexType name=errorResponseType
s:sequence
s:element minOccurs=0 maxOccurs=1 form=unqualified
name=code type=s:string /
s:element minOccurs=0 maxOccurs=1 form=unqualified
name=description type=s:string /
s:element minOccurs=0 maxOccurs=1 form=unqualified
name=message type=s:string /
/s:sequence
/s:complexType
s:element name=authentication type=tns:authentication /
s:complexType name=authentication
s:sequence
s:element minOccurs=0 maxOccurs=1 form=unqualified
name=userName type=s:string /
s:element minOccurs=1 maxOccurs=1 form=unqualified
name=Password nillable=true type=s:string /
/s:sequence
/s:complexType
/s:schema
/wsdl:types
wsdl:message name=UpdateSapIdSoapIn
wsdl:part name=parameters element=tns:UpdateSapId /
/wsdl:message
wsdl:message name=UpdateSapIdSoapOut
wsdl:part name=parameters element=tns:UpdateSapIdResponse /
/wsdl:message
wsdl:message name=UpdateSapIdauthentication
wsdl:part name=authentication element=tns:authentication /
/wsdl:message
[Axis2] RE:RE: RE: Axis2 1.2 release plan
Hi, One thought is that since when geronimo starts up loading the activemq broker, the class org.activemq.jndi.ActiveMQInitialContextFactory is already loaded, so when axis2 service that trys to start up jmslistener using the same class org.activemq.jndi.ActiveMQInitialContextFactory as the initial jms context, so that is probably the reason for the attached exception. But i have no idea how to go around this, someone has any clue on this? falom falom [EMAIL PROTECTED] wrote： Hi Paul, BTW, I've also tried to change the jms axis2.xml config to use geronimo's org.activemq.jndi.ActiveMQInitialContextFactory instead of org.apache.activemq.jndi.ActiveMQInitialContextFactory, i got same noclassfound exception. falom falom [EMAIL PROTECTED] wrote： Hi Paul, I installed axis2 war in both tomcat and geronimo. First I managed to test axis2 jms transport in tomcat connecting to standalone activemq broker by deploying one service using servicelifecycle to start up the jmslistener. BUT when i deploy the same service in geronimo, while trying connect to the activemq broker within geronimo, i got following exception attached, seems like problem related to classloader, or something else which i am really stuck with(BTW, i have put necessary activemq jars in every possible folders i can think of under geronimo and axis2 war, same exception all the time), please help! Also I'd very much like to look more into Synapse and related jms soap samples, which i know is a more robust pattern to bridge jms and web services. But i need to first solve this problem in geronimo first. falom 22:46:30,709 INFO [JMSActiveEchoServiceLifeCycle] JMSActiveEchoServiceLifeCycle startUp called. 22:46:30,719 ERROR [JMSListener] Error connecting to JMS connection factory : TopicConnectionFactory javax.naming.NoInitialContextException: Cannot instantiate class: org.apache.activemq.jndi.ActiveMQInitialContextFactory [Root exception is java.lang.ClassNotFoundException: org.apache.activemq.jndi.ActiveMQInitialContextFactory in classloader default/axis211/1164548268298/war] at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:657) at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247) at javax.naming.InitialContext.init(InitialContext.java:223) at javax.naming.InitialContext.init(InitialContext.java:197) at org.apache.axis2.transport.jms.JMSConnectionFactory.createInitialContext(JMSConnectionFactory.java:133) at org.apache.axis2.transport.jms.JMSConnectionFactory.connect(JMSConnectionFactory.java:122) at org.apache.axis2.transport.jms.JMSListener.initializeConnectionFactories(JMSListener.java:244) at org.apache.axis2.transport.jms.JMSListener.init(JMSListener.java:104) at org.apache.axis2.jms2.JMSActiveEchoServiceLifeCycle.startUp(JMSActiveEchoServiceLifeCycle.java:56) at org.apache.axis2.deployment.ServiceBuilder.loadServiceLifeCycleClass(ServiceBuilder.java:354) at org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:136) at org.apache.axis2.deployment.repository.util.ArchiveReader.buildServiceGroup(ArchiveReader.java:91) at org.apache.axis2.deployment.repository.util.ArchiveReader.processServiceGroup(ArchiveReader.java:133) at org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:528) at org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:196) at org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:227) at org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:174) at org.apache.axis2.deployment.DeploymentEngine.loadServices(DeploymentEngine.java:88) at org.apache.axis2.deployment.WarBasedAxisConfigurator.loadServices(WarBasedAxisConfigurator.java:252) at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:72) at org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:373) at org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:317) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1105) at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:932) at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3915) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4176) at org.apache.geronimo.tomcat.GeronimoStandardContext.access$201(GeronimoStandardContext.java:67) at org.apache.geronimo.tomcat.GeronimoStandardContext$SystemMethodValve.invoke(GeronimoStandardContext.java:337) at org.apache.geronimo.tomcat.valve.GeronimoBeforeAfterValve.invoke(GeronimoBeforeAfterValve.java:31) at org.apache.geronimo.tomcat.GeronimoStandardContext.start(GeronimoStandardContext.java:192) at
Re: Could AXIS2 used together with jUDDI?
Neither. It looks to me as if you haven't configured your database properly in jUDDI. It can't find your JDBC data source. I suggest you consult the jUDDI discussion list for help setting up jUDDI. Anne On 1/17/07, Jiang Liu [EMAIL PROTECTED] wrote: Hi all I am having a project that require to retrieve service from private UDDI registry. Currently i am using Geronimo server + AXIS2 + jUDDI v09rc4. From the jUDDI's configuration page, there are errors: jUDDI Dependencies: Resource Properties Files Looking for: log4j.xml -Not Found jUDDI DataSource Validation + Got a JNDI Context! - No 'java:comp/env/jdbc/juddiDB' DataSource Located(jdbc/juddiDB) - DB connection was not aquired. (null) - SELECT COUNT(*) FROM PUBLISHER failed (null) Also with my simple UDDI registry client, errors are: - Unable to find required classes (javax.activation.DataHandler and javax.mail.internet.MimeMultipart). Attachment support is disabled. at org.uddi4j.UDDIElement.init(UDDIElement.java:40) at org.uddi4j.response.AuthToken.init(AuthToken.java:85) at org.uddi4j.client.UDDIProxy.get_authToken(UDDIProxy.java:1626) at Client.main(Client.java:25) Is that the problem with my jUDDI and geronimo or the problem with jUDDI and AXIS2? cheers!! - Jiang Liu Student Number: 3075163 CS/Yallara Name: ljiang - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
1.1.1 modules not downloadable from mirrors
The new Addressing and SoapMonitor modules from version 1.1.1 downloads point to apache mirror sites, but the mirrors dont have the files for download. I tried a bunch of mirrors with no success. The files probably have not yet been uploaded. Can someone verify this and have them available for download? Thanks, Sathija. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Consuming Web Service that returns object - blank object problem
Please post the WSDL for the service.
On 1/15/07, Shyamal Shah [EMAIL PROTECTED] wrote:
Hi,
I am consuming a web service in a client. I have two methods one that
returns back an xml string and another one that returns the object. When I
call the method that returns xml back it works fine as expected. In case of
calling method that returns object, it returns blank object. Is there
anything I am doing wrong in the client code? Could anyone please advise if
I am missing something obvious? Below is my client code :
Service service = new Service();
Call call = (Call) service.createCall();
call.setTargetEndpointAddress(new java.net.URL(
http://localhost:8080/axis2/services/CustomerInformationWS?wsdl;));
String custId = 999;
String maSrNo = 555;
call.setOperationName(new QName(
http://businessobject.o2c.adt.com/xsd;, getCustomerTO));
call.addParameter (custId, org.apache.axis.encoding
.XMLType.XSD_INT, javax.xml.rpc.ParameterMode.IN);
call.addParameter(maSrNo,
org.apache.axis.encoding.XMLType.XSD_INT,
javax.xml.rpc.ParameterMode.IN);
QName qnm = new QName(
http://transferobject.o2c.adt.com/xsd), getCustomerTO);
call.registerTypeMapping (CustInfoTO.class, qnm, new
org.apache.axis.encoding.ser.BeanSerializerFactory
(CustInfoTO.class, qnm), new
org.apache.axis.encoding.ser.BeanDeserializerFactory(CustInfoTO.class,
qnm));
call.setReturnType(new QName(
http://transferobject.o2c.adt.com/xsd) ,
getCustomerTO));
CustInfoTO result = (CustInfoTO) call.invoke(new Object[] { custId,
maSrNo });
System.out.println(Result is + result.getCCVL_CU_NO());
//all the attributes in the object are set to null or 0 and not what
I expect in the object.
I will appreciate any help/suggestion on this.
Thanks,
Shyam
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: can some one please help me about attachments in jax-ws?
Try Sun's discussion list. Axis/Axis2 don't support JAX-WS. On 1/15/07, legolas [EMAIL PROTECTED] wrote: Hi Thank you for reading my post. Its some days that i try to create a pair of client and a web service that could handle attachments (I must use Jax-WS ) but i can not find any document that show how to create the service itself. All Sun tutorials and samples just show the clinet side and not the server side of the problem. can some one please help me about this? whether by giving some links, sample code or hint that tell me what should i do in service side. Thanks -- View this message in context: http://www.nabble.com/can-some-one-please-help-me-about-attachments-in-jax-ws--tf3017980.html#a8381591 Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Do you know a tool to easily visualize a wsdl file ?
Ok thank you everyone for your proposals. In the end I will probably end writing that small app myself. Everything your proposed are fine tools but none outputs the results with the simplicity I aim. What I want is when you look at an operation you have a direct insight of what are the inputs and what are the ouputs (in term of primitives) What I don't want is when you look at an operation you have the name of input/output messages then you have to search those messages which may be complex types and then you have to naviguate to those types and go back the messages for the name of the next complexType you wanted to look and then go back to the types definition (when it's not in another file) etc. Since I don't mean to use it on huge wsdls, I will write a small program doing what I want. Thank you again for taking the time to answer. regards, Samy MECHIRI - Software Engineer KXEN - 92158 Suresnes CEDEX FRANCE From: Cox, Brian (GE Infra, Energy) [mailto:[EMAIL PROTECTED] Sent: mercredi 17 janvier 2007 19:40 To: axis-user@ws.apache.org Subject: RE: Do you know a tool to easily visualize a wsdl file ? Although it is not necessarily small application, you might try NetBeans 5.5 with the Enterprise pack. I have attached a screen capture. The Port Types section displays the information you are interested in, however, no text/html dump that I am aware of. -Original Message- From: Samy Mechiri [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 17, 2007 8:53 AM To: axis-user@ws.apache.org Subject: Do you know a tool to easily visualize a wsdl file ? Hi everyone, do you know any small, easily usable tool to visualize what operations (and their arguments) are available on a wsd file ? There seem to be nusoap having such a tool (i've read about it on http://www.xml.com/lpt/a/1388) but I could not find any reference to it on nusoap's web page. Ideally it would output the results as a txt or html file Thank you for reading.
Re: [Axis2] [rampart] Problems using rampart
Hi Sebastian, Looks like I was wrong in the previos mail. Can you pls tell me the rampart version that you are using, so that I can look into it the matter? One more question, do you load Policy at the client side? Thank you, Dimuthu. On 1/18/07, Sebastian Roschke [EMAIL PROTECTED] wrote: Hi Dimuthu, Thanks for the hint... The SOAP messages I use are really simple. There is nothing special I think. It is something like that: ?xml version='1.0' encoding='utf-8'? soapenv:Envelope xmlns:wsa=http://www.w3.org/2005/08/addressing; xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Header wsa:Tohttp://localhost:3003/axis2/services/MessagingClientService/wsa:To wsa:ReplyTo wsa:Addresshttp://www.w3.org/2005/08/addressing/anonymous/wsa:Address /wsa:ReplyTo wsa:MessageIDurn:uuid:8655FCF2CBB79A97C711691163447531/wsa:MessageID wsa:Actionurn:addClient/wsa:Action /soapenv:Header soapenv:Body ns2:addClient xmlns:ns2=http://www.hpi.uni-potsdam.de/skid.common/wsmessaging/types; ns2:agentNametest/ns2:agentName ns2:classNameskid.agent.test.TestAgent/ns2:className ns2:configPathmessaging_test.config/ns2:configPath ns2:messageFactoryClassName / /ns2:addClient /soapenv:Body /soapenv:Envelope Maybe you have any ideas. Please write when you have suggestions... Regards, Sebastian Dimuthu Leelaratne schrieb: Hi Sebastian, This is not a rampart problem. The pointed out JIRA shows the bug. I walked through the stack trace. This happens for specific SOAP messages, when they are converted to DOOM as mentioned. I have never experienced the problem. Maybe because the SOAP messages that I use wouldn't re-create the problem. Regards, Dimuthu On 1/17/07, Sebastian Roschke [EMAIL PROTECTED] wrote: Hi everybody, I have a problem using rampart in axis2. I just have configured the axis2-client.xml this way, that it should use rampart. At the moment I have no configuration for the rampart module at all. While using the client api to invoke a soap request, I get the following exceptions: org.apache.axis2.AxisFault: Error in extracting message properties; nested exception is: org.apache.rampart.RampartException: Error in extracting message properties at org.apache.rampart.handler.RampartSender.invoke(RampartSender.java:65) at org.apache.axis2.engine.Phase.invoke(Phase.java:381) at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:518) at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:651) at org.apache.axis2.description.OutOnlyAxisOperationClient.execute(OutOnlyAxisOperation.java:353) at skid.messaging.ws.client.client.MessagingClientServiceStub.addClient(MessagingClientServiceStub.java:126) at skid.messaging.client.ClientControl.main(ClientControl.java:55) Caused by: org.apache.rampart.RampartException: Error in extracting message properties at org.apache.rampart.RampartMessageData.init(RampartMessageData.java:294) at org.apache.rampart.MessageBuilder.build(MessageBuilder.java:56) at org.apache.rampart.handler.RampartSender.invoke(RampartSender.java:59) ... 6 more Caused by: org.apache.ws.security.WSSecurityException: Error in converting SOAP Envelope to Document; nested exception is: org.apache.axiom.om.OMException: javax.xml.stream.XMLStreamException at org.apache.rampart.util.Axis2Util.getDocumentFromSOAPEnvelope(Axis2Util.java:121) at org.apache.rampart.RampartMessageData.init(RampartMessageData.java:146) ... 8 more Caused by: org.apache.axiom.om.OMException: javax.xml.stream.XMLStreamException at org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:199) at org.apache.axiom.om.impl.dom.NodeImpl.build(NodeImpl.java:469) at org.apache.axiom.om.impl.dom.DocumentImpl.build(DocumentImpl.java:476) at org.apache.rampart.util.Axis2Util.getDocumentFromSOAPEnvelope(Axis2Util.java:107) ... 9 more Caused by: javax.xml.stream.XMLStreamException at org.apache.axiom.om.impl.llom.OMStAXWrapper.updateLastNode(OMStAXWrapper.java:952) at org.apache.axiom.om.impl.llom.OMStAXWrapper.next(OMStAXWrapper.java:913) at org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:116) ... 12 more This exception is thrown when invoking the first request on the stub. I can find the following link concerning that problem: http://www.mail-archive.com/axis-dev@ws.apache.org/msg25582.html As proposed in this post I should check wether the soap message includes MIME parts. I used MIME parts in former times, but at the moment I disabled all MTOM related things. Do you have any suggestions concernings this problem? Is it a known problem or a bug? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail:
Axis2 - soapwithattachments example
Hello, Using Axis 2 1.1.1, I was able to successfully run the soapwithattachments example. After this service was deployed, I was then trying to use the WSDL2Java tool on the deployed WSDL ( http://localhost:7010/axis2/services/SWASampleService?wsdl) and use ADB binding in creating another client to access this service. In the provided example client, it is following along the POJO route and must use the MessageContext to add the attachment. My question is how do I add the attachment using the resultant stub code from WSDL2Java? I have attached the client code I am trying to use. Thanks for the help. Jonathan Heh Engineer/Analyst, Northrop Grumman Integrated Systems Main: (843) 744-7520 Direct: (843) 377-0645 ext 153 FAX: (843) 744-7521 [EMAIL PROTECTED] SWAClient.java Description: SWAClient.java - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: wsdl2java generates incorrect/incomplete code
Anne, Thank you very much for taking the time to produce such a detailed answer. The details are a little depressing for someone with software that relies on being able to dynamically consume web services. For various reasons, we don't support all possible wsdl-described services at present, so it's not fatal that the lack of support for consistent policy attachment makes some additional service types unsupported, e.g. those that depend on policies you have to be told about out-of-band, We'll have to track both the various standardization and implementation efforts and see what develops. Jeff On 1/18/07, Anne Thomas Manes [EMAIL PROTECTED] wrote: See inline... On 1/17/07, Jeff Greif [EMAIL PROTECTED] wrote: Anne, As usual, you are a fount of useful information. Thanks for all you do to explain the various SOA standards to the world. Questions: 1. What schema is supposed to be provided by ?xsd. Keep in mind that the URL query is a non-standard convention. Most systems support the ?wsdl query, but very few support either ?xsd or ?policy. But, assuming that an endpoint does support the ?xsd query convention, then it should return a schema that defines the input and output messages supported by the endpoint. (This convention would be especially helpful for RESTful services that don't provide a WSDL definition.) a. Is it the schema containing the declarations of the types or elements used as message parts? It should define the complete body message structures, which ought to be defined as root elements. Types or message parts aren't sufficient. If you are using RPC style, then you would have to depend on the WSDL to provide the information required to define the message structure. (RPC style only defines types, not the root element of the message.) b. What if that information is contained in several schemas? A message contains a single element ( a root element); therefore, that element must be defined in a single schema (although it can certainly import or include other schemas). For this convention to work, though, all message structures supported by the endpoint must be defined in a single schema. For efficiency sake, you probably want to make sure that the ?xml query returns the actual schemas and doesn't return a bunch of imports that then requires a bunch more queries. c. Does this access schemas contained in the types section of the wsdl and/or imports from those schemas? The convention is that it returns a schema that describes the input and output messages. How it goes about getting that schema is an implementation feature of the system supporting the convention. If Axis2 chose to implement this convention, it might require the developer to provide the schema as a configuration parameter, or it might automatically generate the schema by extracting the appropriate info from the WSDL. 2. Starting from a correct and consistent wsdl descriptor, is there a deterministic algorithm that finds all the policy metadata? Only if the WSDL embeds all policy information via WS-PolicyAttachment. There is no requirement that the policies must be attached to the WSDL. The preferred method for retrieving all metadata is to use WS-MetadataExchange. a. If the policies are embedded in the wsdl and/or referenced in the wsdl, does extracting all the embedded ones and retrieving all the references (recursively if that's necessary), will that be all of the policies that apply? Again, only if the WSDL embeds all policy information. b. Will there be any policies that apply that are not referenced or embedded in the wsdl? It's possible. As a best practice, it's a good idea to attach all applicable policies to the WSDL. c. If policies must be retrieved from a UDDI repository, is that repository referenced in the wsdl or is there some out-of-band process that must be followed to determine its existence? I've never seen an extension to WSDL that provides a means to reference a UDDI bindingTemplate (the UDDI entry that represents a service endpoint). Keep in mind that typically, you're querying UDDI to find a service, its endpoints, and its metadata. If you already have the endpoint, then you should be able to query the endpoint to get its metadata using WS-MetedataExchange. I suppose we could define another query convention: append ?uddi to the access point URL, and it should return a link to the UDDI bindingTemplate that describes it. (FYI: UDDI is a registry, not a repository. It does not host the policies (or WSDLs or XSDs), it simply provides pointers to all the metadata that apply to the service. d. Similarly for access via ?policy. If the service endpoint follows this convention, then the ?policy query should return a WS-Policy file that contains all policies that apply to the service. 3. Do the queries service-endpoint?policy and service-endpoint?xsd produce exceptions when not implemented, or do they produce some empty result? If
Axis failing (with time out) but SOAPUI works
I have a web-service in two servers. One of then works fine from java/axis. The other service just gets a time-out. The problem is that both work well when I use SoapUI as the client. I then TCPMon'ed the calls and I found out that axis sent the request as chunked: So i presume one of the servers has its configuration to accept chunks and the other not. How can I configure axis to no send in chunks Call from Java Code (Axis) that doesn't work: POST /services/SapidSetting.asmx HTTP/1.1 SOAPAction: https://x.xxx.com/Services/SapIdSetting/UpdateSapId; User-Agent: Axis2 Host: xxx..com:1112 Transfer-Encoding: chunked Content-Type: text/xml; charset=UTF-8 203 ?xml version='1.0' encoding='UTF-8'?soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;soapenv:Headerns1:authentication xmlns:ns1=https://x.x.com/Services/SapIdSetting;userNamey123/userNamePasswordxxx/Password/ns1:authentication/soapenv:Headersoapenv:Bodyns1:UpdateSapId xmlns:ns1=https://x..com/Services/SapIdSetting;ns1:Inputusername[EMAIL PROTECTED]/usernameSapId1234/SapId/ns1:Input/ns1:UpdateSapId/soapenv:Body/soapenv:Envelope 0 For this request I get only this short answer: HTTP/1.1 100 Continue Transfer-Encoding: chunked header: Chunked Transfer Coding :The chunked encoding modifies the body of a message in order to transfer it as a series of chunks, each with its own size indicator, followed by an OPTIONAL trailer containing entity-header fields. This allows dynamically produced content to be transferred along with the information necessary for the recipient to verify that it has received the full message. 100 Continue: The client SHOULD continue with its request. This interim response is used to inform the client that the initial part of the request has been received and has not yet been rejected by the server. The client SHOULD continue by sending the remainder of the request or, if the request has already been completed, ignore this response. The server MUST send a final response after the request has been completed. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis failing (with time out) but SOAPUI works
I found out that the problem is the load balances in one of the servers, which doesn't accept HTTP 1.1. So, inside the stub i added: _operationClient.getOptions().setProperty(org.apache.axis2.context.MessageContextConstants.HTTP_PROTOCOL_VERSION,org.apache.axis2.transport.http.HTTPConstants.HEADER_PROTOCOL_10); which made its trick :) thanks emerson On 18/01/07, emerson cargnin [EMAIL PROTECTED] wrote: I have a web-service in two servers. One of then works fine from java/axis. The other service just gets a time-out. The problem is that both work well when I use SoapUI as the client. I then TCPMon'ed the calls and I found out that axis sent the request as chunked: So i presume one of the servers has its configuration to accept chunks and the other not. How can I configure axis to no send in chunks Call from Java Code (Axis) that doesn't work: POST /services/SapidSetting.asmx HTTP/1.1 SOAPAction: https://x.xxx.com/Services/SapIdSetting/UpdateSapId; User-Agent: Axis2 Host: xxx..com:1112 Transfer-Encoding: chunked Content-Type: text/xml; charset=UTF-8 203 ?xml version='1.0' encoding='UTF-8'?soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;soapenv:Headerns1:authentication xmlns:ns1=https://x.x.com/Services/SapIdSetting;userNamey123/userNamePasswordxxx/Password/ns1:authentication/soapenv:Headersoapenv:Bodyns1:UpdateSapId xmlns:ns1=https://x..com/Services/SapIdSetting;ns1:Inputusername[EMAIL PROTECTED]/usernameSapId1234/SapId/ns1:Input/ns1:UpdateSapId/soapenv:Body/soapenv:Envelope 0 For this request I get only this short answer: HTTP/1.1 100 Continue Transfer-Encoding: chunked header: Chunked Transfer Coding :The chunked encoding modifies the body of a message in order to transfer it as a series of chunks, each with its own size indicator, followed by an OPTIONAL trailer containing entity-header fields. This allows dynamically produced content to be transferred along with the information necessary for the recipient to verify that it has received the full message. 100 Continue: The client SHOULD continue with its request. This interim response is used to inform the client that the initial part of the request has been received and has not yet been rejected by the server. The client SHOULD continue by sending the remainder of the request or, if the request has already been completed, ignore this response. The server MUST send a final response after the request has been completed. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
engaging soapmonitor-1.1 in Axis2
I have a webservices written. It is running correctly as far as I can tell. I have a client that's calling the service and is receiving the correct responses. Next week, I plan to give a small demo to my management. I thought of using soapmonitor in the Axis2 Administrator webapp. I was able to engage a servicer and/or an operation with soapmonitor-1.1 module. What do I need to do next so that I can have a visual for webservices activities other than usiing the debug logs? Thanks. Danny
RE: engaging soapmonitor-1.1 in Axis2
copy axis2-soapmonitor-1.1.jar to a temp directory and do : jar -xf axis2-soapmonitor-1.1.jar This jar file is normally located under axis2-version\lib as part of the axis2 distro. Then remove axis2-soapmonitor-1.1.jar from the temp directory. List of files under the temp directory should look like : META-INF org SOAPMonitorApplet$ServiceFilterPanel.class SOAPMonitorApplet$SOAPMonitorData.class SOAPMonitorApplet$SOAPMonitorFilter.class SOAPMonitorApplet$SOAPMonitorPage.class SOAPMonitorApplet$SOAPMonitorTableModel.class SOAPMonitorApplet$SOAPMonitorTextArea.class SOAPMonitorApplet.class Copy everything under temp directory to axis2\ which is your axis2 installation directory (note that if you use tomcat to deploy axis2, the directory is apache-tomcat-version\webapps\axis2) Gul PS : Depending on what version of axis2 you are using the version part of the name of the axis2-soapmonitor.jar file might be different (i.e. it could be SNAPSHOT or 1.1.1) From: Danny Lin [mailto:[EMAIL PROTECTED] Sent: Thursday, January 18, 2007 4:37 PM To: axis-user@ws.apache.org Subject: engaging soapmonitor-1.1 in Axis2 I have a webservices written. It is running correctly as far as I can tell. I have a client that's calling the service and is receiving the correct responses. Next week, I plan to give a small demo to my management. I thought of using soapmonitor in the Axis2 Administrator webapp. I was able to engage a servicer and/or an operation with soapmonitor-1.1 module. What do I need to do next so that I can have a visual for webservices activities other than usiing the debug logs? Thanks. Danny
Re: engaging soapmonitor-1.1 in Axis2
You can use tcpmon as well to sniff axis request and response messages. I thought it was easier to setup and is quite easy to use. You just need to run the launch script from the download's bin and setup the port on which you want to sniff. Make sure your requests are sent to this port from where they will be forwarded onto where ever your services are deployed. http://ws.apache.org/commons/tcpmon/ HTH. Sathija. I have a webservices written. It is running correctly as far as I can tell. I have a client that's calling the service and is receiving the correct responses. Next week, I plan to give a small demo to my management. I thought of using soapmonitor in the Axis2 Administrator webapp. I was able to engage a servicer and/or an operation with soapmonitor-1.1 module. What do I need to do next so that I can have a visual for webservices activities other than usiing the debug logs? Thanks. Danny - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
JiBX binding file not found error
Hi, I've deployed a service successfully using JiBX databinding framework. The Jibx binding file (binding.xml) has been included in the service archive file (.aar). But when the client invokes the service operation, I see that the server throws the following exception: org.apache.axis2.AxisFault: java.lang.RuntimeException: Unable to access binding information for class com.comergent.bean.simple.UserContactBean [java] Make sure the binding has been compiled [java] at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:271) [java] at org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:202) I've tried adding the binding.xml to the META-INF directory and to the parent directory, but i still run into the same issue. Can someone help me resolve this problem. Thanks in advance. vedha - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Axis2] Jar files in /tmp
Hello, I have been running a server process for months now and it uses Axis2. I noticed that there are some files in the /tmp directory by the names like axis2XName.jar where X is a number and Name is the name of a jar file that Axis2 uses. Has anybody seen this earlier and how to control it ? Thanks a lot, Raghbir Singh - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
help. newbie error. cannot deploy
Hello,
I am an Axis newbie. Trying to deploy.
I receive an error. Nothing in the logs to show more
detail:
C:\Everest\WebDeployjava -classpath
C:\Everest\WebDeploy\axis\axis.jar;
C:\Everest\WebDeploy\axis\axis-ant.jar;C:\Everest\WebDeploy\axis\commons-discovery-0.2.jar;
C:\Everest\WebDeploy\axis\commons-logging-1.0.4.jar;C:\Everest\WebDeploy\axis\jaxrpc.jar;
C:\Everest\WebDeploy\axis\log4j-1.2.14.jar;C:\Everest\WebDeploy\axis\saaj.jar;
C:\Everest\WebDeploy\axis\wsdl4j-1.5.1.jar;C:\Everest\WebDeploy\axis\activation.jar;
C:\Everest\WebDeploy\axis\mail.jar;
org.apache.axis.client.AdminClient
C:\Everest\WebDeploy\deploy.wsdd
Processing file C:\Everest\WebDeploy\deploy.wsdd
Exception: AxisFault
faultCode:
{http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString:
java.lang.reflect.InvocationTargetException
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}hostname:ITDMWEB01
Any help appreciated.
Thanks,
Anil
P.S.
wsdd is
-
!-- Use this file to deploy some handlers/chains and
services --
!-- Two ways to do this:
--
!-- java org.apache.axis.client.AdminClient
deploy.wsdd --
!-- after the axis server is running
--
!-- or
--
!-- java org.apache.axis.utils.Admin client|server
deploy.wsdd --
!-- from the same directory that the Axis engine
runs --
deployment
xmlns=http://xml.apache.org/axis/wsdd/;
xmlns:java=http://xml.apache.org/axis/wsdd/providers/java;
!-- Services from DonkeyClockService WSDL service
--
service name=DonkeyClock provider=java:RPC
style=wrapped use=literal
parameter name=wsdlTargetNamespace
value=urn:donkeyclock.deploy/
parameter name=wsdlServiceElement
value=DonkeyClockService/
parameter name=schemaQualified
value=urn:donkeyclock.deploy/
parameter name=wsdlServicePort
value=DonkeyClock/
parameter name=className
value=deploy.donkeyclock.DonkeyClockSoapBindingSkeleton/
parameter name=wsdlPortType
value=DonkeyClock/
parameter name=typeMappingVersion
value=1.2/
parameter name=allowedMethods value=*/
parameter name=scope value=Session/
typeMapping
xmlns:ns=urn:donkeyclock.deploy
qname=ns:ATriggerDetail
type=java:deploy.donkeyclock.ATriggerDetail
serializer=org.apache.axis.encoding.ser.BeanSerializerFactory
deserializer=org.apache.axis.encoding.ser.BeanDeserializerFactory
encodingStyle=
/
typeMapping
xmlns:ns=urn:donkeyclock.deploy
qname=ns:AJobDetail
type=java:deploy.donkeyclock.AJobDetail
serializer=org.apache.axis.encoding.ser.BeanSerializerFactory
deserializer=org.apache.axis.encoding.ser.BeanDeserializerFactory
encodingStyle=
/
/service
/deployment
It's here! Your new message!
Get new email alerts with the free Yahoo! Toolbar.
http://tools.search.yahoo.com/toolbar/features/mail/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [axis2] WSDL2JAVA with XMLBean binding does not create instance of the derived type
Hi,
Regarding the instanceOf issue, I debugged and saw the following issue.
1. In the WSDL2JAVA generated GetAddressesDocumentImpl.getAddressArray, I
would expect the array element should be of type USAddressImpl if instance
is a US address. This is not the case. For example, all elements in
targetList filled by find_all_element_users() are instances of AddressImpl
not USAddressImpl when the XML element is as follows:
xml-fragment xsi:type=xsd:US-Address xmlns:xsi=
http://www.w3.org/2001/XMLSchema-instance; xmlns:xsd=
http://quickstart.samples/xsd; xmlns:soapenv=
http://schemas.xmlsoap.org/soap/envelope/;
city xmlns=http://quickstart.samples/xsd;Cupertino/city
name xmlns=http://quickstart.samples/xsd;XYZ/name
state xmlns=http://quickstart.samples/xsd;CA/state
zip xmlns=http://quickstart.samples/xsd;95014/zip
/xml-fragment
This kind of explained why the instanceof is not working properly in service
code. Any idea why it is done this way? Is it a bug?
public samples.quickstart.service.xmlbeans.xsd.Address[] getAddressesArray()
{
synchronized (monitor())
{
check_orphaned();
java.util.List targetList = new java.util.ArrayList();
get_store().find_all_element_users(ADDRESSES$2, targetList);
samples.quickstart.service.xmlbeans.xsd.Address[] result =
new samples.quickstart.service.xmlbeans.xsd.Address[targetList.size()];
targetList.toArray(result);
return result;
}
}
Thanks,
-Bo
On 1/17/07, Bo Xie [EMAIL PROTECTED] wrote:
Hi Ramesh,
Sorry to get back on this late.
I noticed that the same code behave differently when invoked
standalone(from main()), or from the service.
From standalone, the xsi:type are in the XML properly(same as your test).
While from service, the xsi:type attribute are missing. Please see attached
file test program. They are calling the same method(populateAddress().
I am just wondering if there is any setting on the service side that may
influence the generation of the xsi:type?
Below are the XML output from two cases and the populateAddress method.
Thanks,
-Bo
XML dump when running from main(). xsi:type is generated.
xsd:getAddressesResponse xmlns:xsd=http://quickstart.samples/xsd;
xsd:addresses xsi:type=xsd:US-Address xmlns:xsi=
http://www.w3.org/2001/XMLSchema-instance;
xsd:citySunnyvale/xsd:city
xsd:nameXYZ/xsd:name
xsd:stateCA/xsd:state
xsd:zip94087/xsd:zip
/xsd:addresses
xsd:addresses xsd:export-code=66553322 xsi:type=xsd:EU-Address
xmlns:xsi= http://www.w3.org/2001/XMLSchema-instance;
xsd:cityHongkong/xsd:city
xsd:nameXYZ/xsd:name
xsd:postcode2300331 E.C/xsd:postcode
/xsd:addresses
/xsd:getAddressesResponse
XML dump when running as service. xsi:type is missing.
xsd:getAddressesResponse xmlns:xsd=http://quickstart.samples/xsd
xsd:addresses
xsd:citySunnyvale/xsd:city
xsd:nameXYZ/xsd:name
xsd:stateCA/xsd:state
xsd:zip94087/xsd:zip
/xsd:addresses
xsd:addresses xsd:export-code=66553322
xsd:cityHongkong/xsd:city
xsd:nameXYZ/xsd:name
xsd:postcode2300331 E.C/xsd:postcode
/xsd:addresses
/xsd:getAddressesResponse
The populateAddress method.
private static void populateAddress(GetAddressesResponseDocument resDoc) {
// TODO Auto-generated method stub
GetAddressesResponseDocument.GetAddressesResponse res =
resDoc.addNewGetAddressesResponse();
samples.quickstart.service.xmlbeans.xsd.Address[] addArray = new
samples.quickstart.service.xmlbeans.xsd.Address [2];
samples.quickstart.service.xmlbeans.xsd.USAddress addr =
samples.quickstart.service.xmlbeans.xsd.USAddress.Factory.newInstance();
//samples.quickstart.service.xmlbeans.xsd.USAddress addr =
samples.quickstart.service.xmlbeans.xsd.USAddress.Factory.newInstance();
addr.setName(XYZ);
addr.setCity(Sunnyvale);
addr.setState(USState.CA);
addr.setZip (new BigInteger(94087));
//samples.quickstart.service.xmlbeans.xsd.EUAddress addr1 =
(EUAddress) res.addNewAddresses().changeType(EUAddress.type);
samples.quickstart.service.xmlbeans.xsd.EUAddress addr1 =
samples.quickstart.service.xmlbeans.xsd.EUAddress.Factory.newInstance();
addr1.setName(XYZ);
addr1.setCity(Hongkong);
addr1.setExportCode(new BigInteger(66553322));
addr1.setPostcode(2300331 E.C);
addArray[0] = addr;
addArray[1] = addr1;
res.setAddressesArray(addArray);
XmlOptions ops = new XmlOptions();
ops.setSavePrettyPrint();
ops.setSavePrettyPrintIndent(4);
//String xmlStr = res.xmlText(ops);
//System.out.println(Response Element String: \n + xmlStr);
String xmlStr1 = resDoc.xmlText(ops);
System.out.println(Response Document String: \n + xmlStr1);
}
On 1/8/07, Ramesh
[Axis2] Manual module deployment
Hello, Is it possible to tell axis to load only a specific module instead of going over modules directory? Our server receives and calls external web services. When it is in a mode to call external web service - axis2 goes over modules directory and deploys all .mar files it encounters. But we want it only pickup a certain module - rampart, and not waste time on processing the entire directory. One possible solution is to create a separate module folder that will have only rampart.mar, but we want to avoid duplication. Thanks for your help, Alex - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
How to get session cookie
Hi, I have set a service to transport session scope and the session context worked as expected. But when I try to get the session cookie id, it always returns null. MessageContext cxt = MessageContext.getCurrentMessageContext(); SessionContext session = cxt.getSessionContext(); String cookieId = session.getCookieID(); On the client side, I used the following code, it also always return null. stub._getServiceClient().getOptions().getProperty( org.apache.axis2.transport. http.HTTPConstants.COOKIE_STRING) Can someone shed some lights on how to get the cookie? Thanks, -Bo
RE: help. newbie error. cannot deploy
Anil,
I do not know what is the exact problem, but I have seen the same exception
many times. The server is mapping the original exception to
InvocationTargetException. Therefore, I would recommend looking into the
server logs to know the original Exception and proceed accordingly.
Hope that helps,
--Luis R.
From: Anil Philip [EMAIL PROTECTED]
Reply-To: axis-user@ws.apache.org
To: axis-user@ws.apache.org
Subject: help. newbie error. cannot deploy
Date: Thu, 18 Jan 2007 15:02:54 -0800 (PST)
Hello,
I am an Axis newbie. Trying to deploy.
I receive an error. Nothing in the logs to show more
detail:
C:\Everest\WebDeployjava -classpath
C:\Everest\WebDeploy\axis\axis.jar;
C:\Everest\WebDeploy\axis\axis-ant.jar;C:\Everest\WebDeploy\axis\commons-discovery-0.2.jar;
C:\Everest\WebDeploy\axis\commons-logging-1.0.4.jar;C:\Everest\WebDeploy\axis\jaxrpc.jar;
C:\Everest\WebDeploy\axis\log4j-1.2.14.jar;C:\Everest\WebDeploy\axis\saaj.jar;
C:\Everest\WebDeploy\axis\wsdl4j-1.5.1.jar;C:\Everest\WebDeploy\axis\activation.jar;
C:\Everest\WebDeploy\axis\mail.jar;
org.apache.axis.client.AdminClient
C:\Everest\WebDeploy\deploy.wsdd
Processing file C:\Everest\WebDeploy\deploy.wsdd
Exception: AxisFault
faultCode:
{http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString:
java.lang.reflect.InvocationTargetException
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}hostname:ITDMWEB01
Any help appreciated.
Thanks,
Anil
P.S.
wsdd is
-
!-- Use this file to deploy some handlers/chains and
services --
!-- Two ways to do this:
--
!-- java org.apache.axis.client.AdminClient
deploy.wsdd --
!-- after the axis server is running
--
!-- or
--
!-- java org.apache.axis.utils.Admin client|server
deploy.wsdd --
!-- from the same directory that the Axis engine
runs --
deployment
xmlns=http://xml.apache.org/axis/wsdd/;
xmlns:java=http://xml.apache.org/axis/wsdd/providers/java;
!-- Services from DonkeyClockService WSDL service
--
service name=DonkeyClock provider=java:RPC
style=wrapped use=literal
parameter name=wsdlTargetNamespace
value=urn:donkeyclock.deploy/
parameter name=wsdlServiceElement
value=DonkeyClockService/
parameter name=schemaQualified
value=urn:donkeyclock.deploy/
parameter name=wsdlServicePort
value=DonkeyClock/
parameter name=className
value=deploy.donkeyclock.DonkeyClockSoapBindingSkeleton/
parameter name=wsdlPortType
value=DonkeyClock/
parameter name=typeMappingVersion
value=1.2/
parameter name=allowedMethods value=*/
parameter name=scope value=Session/
typeMapping
xmlns:ns=urn:donkeyclock.deploy
qname=ns:ATriggerDetail
type=java:deploy.donkeyclock.ATriggerDetail
serializer=org.apache.axis.encoding.ser.BeanSerializerFactory
deserializer=org.apache.axis.encoding.ser.BeanDeserializerFactory
encodingStyle=
/
typeMapping
xmlns:ns=urn:donkeyclock.deploy
qname=ns:AJobDetail
type=java:deploy.donkeyclock.AJobDetail
serializer=org.apache.axis.encoding.ser.BeanSerializerFactory
deserializer=org.apache.axis.encoding.ser.BeanDeserializerFactory
encodingStyle=
/
/service
/deployment
It's here! Your new message!
Get new email alerts with the free Yahoo! Toolbar.
http://tools.search.yahoo.com/toolbar/features/mail/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
_
Valentines Day -- Shop for gifts that spell L-O-V-E at MSN Shopping
http://shopping.msn.com/content/shp/?ctId=8323,ptnrid=37,ptnrdata=24095tcode=wlmtagline
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] Manual module deployment
Hi Alexander ; Hello, Is it possible to tell axis to load only a specific module instead of going over modules directory? In the current implementation there is no way to control the behavior and it will load all the mar files in the modules directory. But loading module will not change and configurations or handler chains , configuration will be change only when you engage a module. Our server receives and calls external web services. When it is in a mode to call external web service - axis2 goes over modules directory and deploys all .mar files it encounters. But we want it only pickup a certain module - rampart, and not waste time on processing the entire directory. One possible solution is to create a separate module folder that will have only rampart.mar, but we want to avoid duplication. Thanks for your help, Alex - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Re: AXIS2 engages or supports any BPEL engine?
Thanks a lot Actually i did check ODE before but there is not enough info of how to use it, could you advise some links or doc that fully describe how to use it? cheers!! -Original Message- From: Davanum Srinivas [EMAIL PROTECTED] To: axis-user@ws.apache.org Date: Fri, 19 Jan 2007 02:14:53 -0500 Subject: Re: AXIS2 engages or supports any BPEL engine? Apache ODE uses Axis2 and supports BPEL. http://incubator.apache.org/ode/ On 1/19/07, Jiang Liu [EMAIL PROTECTED] wrote: Hi all Does AXIS2 support BPEL directly? i checked the specification says no but what about the future? And also, what BPEL engine does AXIS2 fully support? cheers!! - Jiang Liu Student Number: 3075163 CS/Yallara Name: ljiang - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Jiang Liu Student Number: 3075163 CS/Yallara Name: ljiang - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Re: AXIS2 engages or supports any BPEL engine?
Please ask on ode-dev@incubator.apache.org (subscribe first ode-dev-subscribe@) -- dims On 1/19/07, Jiang Liu [EMAIL PROTECTED] wrote: Thanks a lot Actually i did check ODE before but there is not enough info of how to use it, could you advise some links or doc that fully describe how to use it? cheers!! -Original Message- From: Davanum Srinivas [EMAIL PROTECTED] To: axis-user@ws.apache.org Date: Fri, 19 Jan 2007 02:14:53 -0500 Subject: Re: AXIS2 engages or supports any BPEL engine? Apache ODE uses Axis2 and supports BPEL. http://incubator.apache.org/ode/ On 1/19/07, Jiang Liu [EMAIL PROTECTED] wrote: Hi all Does AXIS2 support BPEL directly? i checked the specification says no but what about the future? And also, what BPEL engine does AXIS2 fully support? cheers!! - Jiang Liu Student Number: 3075163 CS/Yallara Name: ljiang - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Jiang Liu Student Number: 3075163 CS/Yallara Name: ljiang - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: can some one please help me about attachments in jax-ws?
Yet! :) On 1/18/07, Anne Thomas Manes [EMAIL PROTECTED] wrote: Try Sun's discussion list. Axis/Axis2 don't support JAX-WS. On 1/15/07, legolas [EMAIL PROTECTED] wrote: Hi Thank you for reading my post. Its some days that i try to create a pair of client and a web service that could handle attachments (I must use Jax-WS ) but i can not find any document that show how to create the service itself. All Sun tutorials and samples just show the clinet side and not the server side of the problem. can some one please help me about this? whether by giving some links, sample code or hint that tell me what should i do in service side. Thanks -- View this message in context: http://www.nabble.com/can-some-one-please-help-me-about-attachments-in-jax-ws--tf3017980.html#a8381591 Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
