Re: XSD2Java
Rich One of the aspects of WSDL is duck-typing. http://en.wikipedia.org/wiki/Duck_typing The result of this is that you can have two different WSDLs. The official WSDL and a pseudo WSDL. So one approach would be to take the official WSDL, edit it to include the XSDs and then generate a client from it. You end up with a client that has databinding, but still talks to the real service. Paul On 6/1/07, Rich Adili [EMAIL PROTECTED] wrote: Yep, tons of them. Since writing this I've done some puttering about with various bindings and not found a good solution. The code generated by XSD2Java doesn't like my XML. The XML conforms to the schema but does not reference the schema so the generated code doesn't recognize the namespace of any of its tags. -Original Message- From: Paul Fremantle [mailto:[EMAIL PROTECTED] Sent: Friday, June 01, 2007 7:49 AM To: axis-user@ws.apache.org Subject: Re: XSD2Java Rich Do you have schema somewhere (i.e. just not in the WSDL)? Paul On 5/31/07, Rich Adili [EMAIL PROTECTED] wrote: Hi, My services exchange a number of XML documents that aren't code generated from WSDL as the content is spec'ed as xs:any. Is XSD2Java my best choice for generating Java bindings for these documents? Any documentation or examples lying around? Thanks, Rich - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Paul Fremantle Co-Founder and VP of Technical Sales, WSO2 OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] Oxygenating the Web Service Platform, www.wso2.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] -- Paul Fremantle Co-Founder and VP of Technical Sales, WSO2 OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] Oxygenating the Web Service Platform, www.wso2.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis2/Java: Share HTTP connection between multiple client stubs ?
Hi Raimund The default http/s client transport of Axis2 is based on the commons HttpClient. Please see the following links for some direct solutions for your issue. http://wso2.org/library/87 http://wso2.org/library/230 You may also find more articles through a search on the OxygenTank library. I know that Asankha has been working on a non-blocking HTTP client for Axis2 that re-uses connections. As I understand it this code is only in the Synapse release so far ( http://ws.apache.org/synapse). But I know there is a plan to get it into the core of Axis2. It is just an Axis2 transport so the code will work under Axis2. Asankha - am I right? Yes, the transport we developed for Synapse is tuned for a high throughput environment where you would actually gain from a non-blocking client implementation. Thus, if you just want to send a message and read its response, this transport is not right for you; as it will create an IO Reactor, a thread pool to handle the requests, and prepare to send multiple messages out reusing connections where applicable. We have plans to move this transport into Axis2, but the client side should be used with care for the above reasons. asankha - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Axis2] NIO impl in Axis2 (Re: Axis2/Java: Share HTTP connection between multiple client stubs ?)
Asankha, Can we please move this transport to Axis2 in time for 1.3? thanks, dims On 6/2/07, Asankha C. Perera [EMAIL PROTECTED] wrote: Hi Raimund The default http/s client transport of Axis2 is based on the commons HttpClient. Please see the following links for some direct solutions for your issue. http://wso2.org/library/87 http://wso2.org/library/230 You may also find more articles through a search on the OxygenTank library. I know that Asankha has been working on a non-blocking HTTP client for Axis2 that re-uses connections. As I understand it this code is only in the Synapse release so far ( http://ws.apache.org/synapse). But I know there is a plan to get it into the core of Axis2. It is just an Axis2 transport so the code will work under Axis2. Asankha - am I right? Yes, the transport we developed for Synapse is tuned for a high throughput environment where you would actually gain from a non-blocking client implementation. Thus, if you just want to send a message and read its response, this transport is not right for you; as it will create an IO Reactor, a thread pool to handle the requests, and prepare to send multiple messages out reusing connections where applicable. We have plans to move this transport into Axis2, but the client side should be used with care for the above reasons. asankha - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Apache Rampart 1.2 Released
You can download the release artifacts from : http://www.apache.org/dyn/closer.cgi/ws/rampart/1_2 :-) Thanks, Ruchith On 6/2/07, Ruchith Fernando [EMAIL PROTECTED] wrote: This is the 1.2 release of Apache Rampart. Apache Rampart 1.2 is a toolkit that provides implementations of the WS-Sec* specifications for Apache Axis2 1.2, based on Apache WSS4J 1.5.2 and the Apache AXIOM-DOOM 1.2.4 implementations. There are two main Apache Axis2 modules provided with this release. * rampart-1.2.mar This provides support for WS-Security and WS-SecureConversation features. * rahas-1.2.mar This module provides the necessary components to enable SecurityTokenService functionality on a service. Apache Rampart 1.2 uses a configuration model based on WS-Policy and WS-Security Policy and it is important to note that Apache Rampart 1.0 style configuration is also available even though being marked as deprecated. Apache Rampart 1.2 can be successfully used with the next Apache Sandesha2 release targeted towards Apache Axis2 1.2 to configure WS-SecureConversation + WS-ReliableMessaging scenarios. The rampart module was successfully tested for interoperability with other WS-Security implementations. WS - Sec* specifications supported by Apache Rampart are as follows: * WS - Security 1.0 * WS - Secure Conversation - February 2005 * WS - Security Policy - 1.1 - July 2005 * WS - Trust - February 2005 * WS - Trust - WS-SX spec - EXPERIMENTAL Thank you for using Apache Rampart. Apache Rampart team -- www.ruchith.org www.wso2.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2 1.1.1] Unable to generate WSDL for this service
Switching to Axis2 1.2 is not really an option. Adding the RPCMessageReceiver to the list of MessageReceivers solves the problem, but there is a conflict with another MessageReceiver that has the same http://www.w3.org/2004/08/wsdl/in-out; mep as the RPCMessageReceiver. This MessageReceiver is automatically generated by the WSDL2Java tool. So, how can I display the WSDL linked with a Service when using the generated MessageReveiver instead of the RPCMessageReceiver ? Regards, Stefan Lecho. Davanum Srinivas wrote: Please switch to Axis2 1.2 and let us know if you still see this problem. thanks, dims On 5/29/07, Stefan Lecho [EMAIL PROTECTED] wrote: All, I would like to display the WSDL of a WebService generated with Axis2 v1.1.1 and deployed in Tomcat v5.5.17. When using http://localhost:9091/itpartners-axis2-0.0.1/services/ASFInterface?wsdl;, the following error message is generated: Unable to generate WSDL for this service. After a search in the mailing list of Axis2, I've noticed that there are solutions to this problem: -check that the name attribute of the service element in services.xml is the same as the name attribute of the wdsl:service element in the WSDL file = OK -use the useOriginalwsdl parameter = OK -use RPCMessageReceiver as messageReceiver = OK All the above checks are OK (files are included underneath), but I still do not get my WSDL file displayed correctly. Can anyone help me with this issue ? The messageReceivers and parameter section from the services.xml file: service name=ASFInterface class=be.credoc.service.SpringInit messageReceivers /messageReceivers parameter name=ServiceTCCL locked=falsecomposite/parameter parameter name=load-on-startuptrue/parameter parameter name=useOriginalwsdltrue/parameter The wsdl:service section from the WSDL file that has been deployed in the WEB-INF directory of the AAR file: wsdl:service name=ASFInterface Regards, Stefan Lecho. Building a website is a piece of cake. Yahoo! Small Business gives you all the tools to get online. -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/-Axis2-1.1.1--Unable-to-generate-WSDL-for-this-service-tf3832868.html#a10927645 Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
How to get return value..
Hi,
I want to fetch the return value from the response of the web service
method. Iam using asynchronous web service calls.
This is the SoapEnvelope which i get in AsynResult argument of onComplete
method.
?xml version='1.0' encoding='utf-8'?
soapenv:Envelope
xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;
soapenv:Header /
soapenv:Body
ns:notifySuccessResponse
xmlns:ns=http://superconnector.panoptica.com/xsd;
ns:return4009/ns:return
/ns:notifySuccessResponse
/soapenv:Body
/soapenv:Envelope
This is the implementation of onComplete method.
public void onComplete(AsyncResult result) {
Iterator itr =
result.getResponseEnvelope().getBody().getChildElements();
while (itr.hasNext()) {
Object temp = itr.next();
System.out.println(Attribute : + temp);
OMElement element = (OMElement) temp;
Iterator elementItr = element.getChildElements();
while (elementItr.hasNext()) {
OMElement returnElement = (OMElement)
elementItr.next();
System.out.println(Attributes of child : +
returnElement);
System.out.println(Attribute Value : +
returnElement.
getAttributeValue(returnElement.getQName()));
}
}
Its giving me null value. Iam pretty new to SOAP and Axis2. Please tell me
what mistake iam making here.
-Thanks,
Ajay
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
I can't read file from aar
I have a classes, when i'm seeing inside aar (webservice Axis'a) this file is inside as /ja/ja.xml, there are also another classes aat has been put into webservice inside unpacked axis2.war, which is in jboss URL object toString() in my code getClass().getResource(/com/ja/ja.xml); return jar:file:/C:/DOCUME~1/mkr/USTAWI~1/Temp/axis247457.aar!/com/ja/ja.xml file C:/DOCUME~1/mkr/USTAWI~1/Temp/axis247457.aar exists but, when i tryed load it into byte table or as DOM object i have null, or unmature end of file how can i load it? url.openStream(); should work, but doesn't DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance(); DocumentBuilder builder = factory.newDocumentBuilder(); URL url = getClass().getResource(/com/ja/ja.xml); factory.setValidating(true); InputStream inputStream = url.openStream(); byte [] tableofByte = new byte[1]; inputStream.read(tableofByte); document = builder.parse(inputStream); - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
schema imports in wsdl
Iam importing a schema in my wsdl,but when i deploy the same it fails with a message that it is not able to find the .xsd file(file not found exception) under the root location (domain root from where i start the weblogic). XSD file is available in the aar file,but its not picking the from there. Does axis2 (wsdl4j)support schema imports?. i am using axis2 1.1.1, also tried axis2 1.2. -- View this message in context: http://www.nabble.com/schema-imports-in-wsdl-tf3857566.html#a10928891 Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problem consuming POJO-based Webservice with Axis2-1.1.1
Hi again,
I've been experimenting using RPCServiceClient above and find that I can
successfully invoke the service from a Java application, but not from
within a Tomcat webapp.
It doesn't like that I pass a filled Object array containing the
webservice method arguments. Like so:
*
// Code
Object[] operationArguments = new Object[] { userName, userCode };
Object[] response = serviceClient.invokeBlocking( opTestService,
operationArguments, returnTypes );
// - End Code -- *
However I can pass an empty Object array without problem ( Object[]
operationArguments = new Object[] { };).
Are there any know issues invoking a service in this way?
Here is us the full error trace:
// Code
java.lang.NullPointerException
at
com.ctc.wstx.sw.BaseNsStreamWriter.doWriteDefaultNs(BaseNsStreamWriter.java:528)
at
com.ctc.wstx.sw.SimpleNsStreamWriter.writeDefaultNamespace(SimpleNsStreamWriter.java:111)
at
com.ctc.wstx.sw.SimpleNsStreamWriter.writeNamespace(SimpleNsStreamWriter.java:119)
at
org.apache.axiom.om.impl.MTOMXMLStreamWriter.writeNamespace(MTOMXMLStreamWriter.java:146)
at
org.apache.axiom.om.impl.util.OMSerializerUtil.serializeStartpart(OMSerializerUtil.java:329)
at
org.apache.axiom.om.impl.util.OMSerializerUtil.serializeStartpart(OMSerializerUtil.java:171)
at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:804)
at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerializeAndConsume(OMElementImpl.java:837)
at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:808)
at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerializeAndConsume(OMElementImpl.java:837)
at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:808)
at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerializeAndConsume(OMElementImpl.java:837)
at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:808)
at
org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.internalSerialize(SOAPEnvelopeImpl.java:179)
at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerializeAndConsume(OMElementImpl.java:837)
at
org.apache.axiom.om.impl.llom.OMNodeImpl.serializeAndConsume(OMNodeImpl.java:417)
at
org.apache.axis2.transport.http.SOAPOverHTTPSender$AxisSOAPRequestEntity.handleOMOutput(SOAPOverHTTPSender.java:190)
at
org.apache.axis2.transport.http.SOAPOverHTTPSender$AxisSOAPRequestEntity.writeRequest(SOAPOverHTTPSender.java:232)
at
org.apache.commons.httpclient.methods.EntityEnclosingMethod.writeRequestBody(EntityEnclosingMethod.java:495)
at
org.apache.commons.httpclient.HttpMethodBase.writeRequest(HttpMethodBase.java:1973)
at
org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:993)
at
org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:397)
at
org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:170)
at
org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:396)
at
org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:346)
at
org.apache.axis2.transport.http.AbstractHTTPSender.executeMethod(AbstractHTTPSender.java:541)
at
org.apache.axis2.transport.http.SOAPOverHTTPSender.send(SOAPOverHTTPSender.java:119)
at
org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:335)
at
org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:204)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:674)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:237)
at
org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:202)
at
org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:579)
at
org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:508)
at
org.apache.axis2.rpc.client.RPCServiceClient.invokeBlocking(RPCServiceClient.java:95)
// - End Code --
Regards,
Alan Sunley.
Deepal Jayasinghe wrote:
Hi Alan ,
I hope you will get a Rampart release soon.
Thanks
Deepal
Hi folks,
I was able to successfully deploy and consume a POJO-based webservice
by closely following the POJO guide on the Axis2-1.2 site. However I
need to include a username/password token in each message, therefore I
need to use Rampart. Unfortunately the current version of Rampart
(1.1) doesn't appear to be compatible with Axis2-1.2, so I have to
roll back to Axis2-1.1.1, and it is here that I have run into a host
of problems.
Firstly I don't seem to be able to access the service at all using the
same RPCServiceClient call (as I was able to with version 1.2):
