[jira] Assigned: (AXIS2C-548) Axis2C crashes when sending a content-type header without a '=' seperator for the charset
[ https://issues.apache.org/jira/browse/AXIS2C-548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe reassigned AXIS2C-548: Assignee: Samisa Abeysinghe Axis2C crashes when sending a content-type header without a '=' seperator for the charset - Key: AXIS2C-548 URL: https://issues.apache.org/jira/browse/AXIS2C-548 Project: Axis2-C Issue Type: Bug Components: transport/http Affects Versions: Current (Nightly) Environment: Linux / Windows Reporter: Supun Kamburugamuva Assigned To: Samisa Abeysinghe Fix For: 1.0.0 This is the content type that I have sent Content-Type:application/soap+xml;charset:UTF-8; Axis2C crashes in the axis2_http_transport_utils.c line 905. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2C-548) Axis2C crashes when sending a content-type header without a '=' seperator for the charset
[ https://issues.apache.org/jira/browse/AXIS2C-548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe resolved AXIS2C-548. -- Resolution: Fixed Fix Version/s: 1.0.0 Fixed the bug. Anyway the content type format you are using is buggy - however still the server should not crash Axis2C crashes when sending a content-type header without a '=' seperator for the charset - Key: AXIS2C-548 URL: https://issues.apache.org/jira/browse/AXIS2C-548 Project: Axis2-C Issue Type: Bug Components: transport/http Affects Versions: Current (Nightly) Environment: Linux / Windows Reporter: Supun Kamburugamuva Assigned To: Samisa Abeysinghe Fix For: 1.0.0 This is the content type that I have sent Content-Type:application/soap+xml;charset:UTF-8; Axis2C crashes in the axis2_http_transport_utils.c line 905. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Buy Developer Time?
Hi, I am curious as to whether it is possible to buy developer time to fix one open bug: https://issues.apache.org/jira/browse/AXISCPP-899 - and if so, how much would it cost? Thanks. Adrian -- DRM 'manages access' in the same way that jail 'manages freedom'.
axis2c malloc error
hi i am writing an application in axis2c.(VC++) , which requires additional dependancies,for which i generated following files: server.cpp server_skeleton.cpp server.h while allocating memory in server_skeleton file using AXIS2_MALLOC function, i required type casting(wich doesnt require in .c file). Bt after explicit conversion my application is not running properly. if any1 encountered such problem, plz help me. thank you. Urvashi. - Heres a new way to find what you're looking for - Yahoo! Answers
[AXIS2] Wrong parameter names for mail transport in axis2.xml
Hi axis2 devs, I have found out that the parameter names in the axis2.xml for configuring mail transport bear wrong names. here the relevant sections from the axis2.xml file: transportReceiver name=mail class= org.apache.axis2.transport.mail.SimpleMailListener parameter name=mail.store.protocol i think this parameter is needed as well (it is missing in the default axis2.xml) parameter name=transport.mail.pop3.host locked=false127.0.0.1/parameter = should read name=mail.pop3.host ... parameter name=transport.mail.pop3.user locked=falseaxis2/parameter= shuold read name=mail.pop3.user ... parameter name=transport.mail.pop3.password locked=falseaxis2/parameter parameter name=transport.mail.pop3.port locked=false110/parameter = should read name=mail.pop3.port /transportReceiver transportSender name=mailto class= org.apache.axis2.transport.mail.MailTransportSender parameter name=transport.mail.smtp.host locked=false127.0.0.1/parameter = should read name=mail.smtp.host ... parameter name=transport.mail.smtp.user locked=falseaxis2/parameter = shuold read name=mail.smtp.user ... parameter name=transport.mail.smtp.password locked=falseaxis2/parameter parameter name=transport.mail.smtp.port locked=false25/parameter should read name=mail.pop3.port /transportSender Regards Vasil -- Vasil Benov, Mobile: +359(0)889/202682 @-mail: benovv at gmail dot com ICQ: 140269988 GPG Fingerprint: 2CDC 5DA0 4C0A 7C06 5259 DE12 ACF3 177C 8906 0908 Public Key URL: *) http://random.sks.keyserver.penguin.de/
Abstract Complex Type [Our Ref:CPTA3324]
Hi All I've posted this message on the user mailing list, but unfortunately did not get any replies. I realize that the problem is not strictly related to the Axis development, although it does touch on how Axis handles a certain scenario / the behaviour that I'm experiencing. So please bear with me, and rest assured that your help would be greatly appreciated. On to the problem: I'm using Axis 1.3 to generate my client stubs etc. The problem that I'm experiencing is as follows: The web service that I'm connecting to has a abstract complex type (let's say: Favorite) defined as part of an argument for a call (let's say: favoritesAdd). The Favorite abstract type has additional implementing types defined, eg. FavoriteSimpleTracking, FavoriteAdvancedTracking etc. These implementing complex types have additional properties that can be set. When making a call to favoritesAdd, Axis only populates the properties defined by the Favorite interface and not the additional properties defined by an implementing class. My thoughts are: 1. Since the WSDL defines Favorite as the call's argument Axis quite rightly ignores the additional properties set by an implementing class. Can somebody please confirm this? 2. Alternatively, should Axis be clever enough to realize that I'm passing it an object type that contains additional properties and that they need to be set in the SOAP request as well? 3. If not, and if it is even legal to do something like this in a web service, how can I tell Axis to do this? Below the relevant WSDL snippets: (Looking at the snippets below, you'll notice that the Favorite object get's passed to a FavoriteAddRequestDO for the call - I did not want to expand on this too much above in order to keep the explanation simple...) operation name=favoritesAdd input message=tns:favoritesAdd / output message=tns:favoritesAddResponse / /operation message name=favoritesAdd part xmlns:partns=http://www.maerskline.com/eTrack30/2006/03/22/TrackingRegisteredService; name=wsrequest element=partns:favoritesAdd / /message xsd:element xmlns:tp=java:com.maerskline.etrack.service.type.request type=tp:FavoritesAddRequestDO name=favoritesAdd nillable=true / xsd:complexType name=FavoritesAddRequestDO xsd:sequence xsd:element xmlns:tp=java:com.maerskline.etrack.service.type type=tp:Favorite name=favorite minOccurs=1 maxOccurs=1 nillable=true / /xsd:sequence /xsd:complexType xsd:complexType name=Favorite abstract=true xsd:sequence xsd:element type=xsd:string name=SCACCode minOccurs=1 maxOccurs=1 nillable=true / xsd:element type=xsd:string name=certificateId minOccurs=1 maxOccurs=1 nillable=true / xsd:element type=xsd:string name=customerId minOccurs=1 maxOccurs=1 nillable=true / xsd:element type=xsd:string name=description minOccurs=1 maxOccurs=1 nillable=true / xsd:element type=xsd:integer name=favoriteId minOccurs=1 maxOccurs=1 nillable=true / xsd:element type=xsd:dateTime name=lastUsed minOccurs=1 maxOccurs=1 nillable=true / /xsd:sequence /xsd:complexType xsd:complexType name=FavoriteSimpleTracking xsd:complexContent xsd:extension base=stns:Favorite xsd:sequence xsd:element type=stns:ArrayOfFavoriteSimpleTrackingCriterion name=criteria minOccurs=1 maxOccurs=1 nillable=true / /xsd:sequence /xsd:extension /xsd:complexContent /xsd:complexType Many thanks! Fouche Du Preez Developer Information Technology Safmarine Computer Services (Pty) Ltd. Tel: +27 21 4463040 Fax: +27 21 4463162 Email: [EMAIL PROTECTED] Web: http://www.scs.co.za The information in this e-mail is confidential and is intended solely for the adressee(s). Access to this email by anyone else is unauthorized. If you are not an intended recipient, please notify the sender of this email immediately. You may not print, save or otherwise store the e-mail or any of the contents thereof in electronic or physical form, nor copy, use or disseminate the information contained in the email. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Soap body modifications just before my-service-class invocation
Hi all, I need to modify SOAP body at the very last point of the processing chain just before the invocation of the java class which implements my service. I'd like to know how can I find (where to read) the sequence of method call or any other ideas that let me know which classes are involved in this process and at which point can I inject modifications. Thanks in advance, Mauro Iorio.
[jira] Created: (AXIS2-2327) RPCMessageReceiver; response envelope dose not serialize properly
RPCMessageReceiver; response envelope dose not serialize properly -- Key: AXIS2-2327 URL: https://issues.apache.org/jira/browse/AXIS2-2327 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: adb Environment: Any Reporter: Saminda Wishwajith Abeyruwan Priority: Critical I've deployed Axis2 in Weblogic 9.2. For the service I used RPCMessageReceiver and part of response envelop is as follows, == ?xml version='1.0' encoding='utf-8'? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Body ns:getSystemLogResponse xmlns:ns=http://org.apache.axis2/xsd; return appenderData facility xmlns:nil=http://www.w3.org/2001/XMLSchema-instance; nil:nil=true/facility isFileAppenderfalse/isFileAppender isSysLogAppenderfalse/isSysLogAppender logFile nil:nil=true/logFile nameAXIS2_MEMORY/name pattern%5p [%d] %x %m%n/pattern sysLogHost nil:nil=true/sysLogHost thresholdDEBUG/threshold /appenderData ... /return /ns:getSystemLogResponse /soapenv:Body /soapenv:Envelope = As you can see, //apenderData/facility has declared xmlns:nil=http://www.w3.org/2001/XMLSchema-instance; but //apenderData/logFile element is unbounded for nil prefix. Is this problem due to their implementation. Should I report to AXIOM as well. Now Weblogic has its own stax implementation. Apparently, system load Weblogic stax impl by default. On the other hand, Should't it be cleaner, if the namespace http://www.w3.org/2001/XMLSchema-instance; bound to xsi prefix rather nil prefix. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
I: Attachments in the WSDL
I have wrote a web service with attachments. The service works fine but a can see anything about this attachments in the WSDL when a call ...AxisProxyServices?wsdl. Can you help me to understand how can i solve this problem?? Thanks Alfonso Ubaldini
[jira] Resolved: (AXIS2-2301) wsa 04 version problem - AxisFault Required MessageID in header in Response
[ https://issues.apache.org/jira/browse/AXIS2-2301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian DePradine resolved AXIS2-2301. Resolution: Fixed Fix Version/s: nightly wsa 04 version problem - AxisFault Required MessageID in header in Response --- Key: AXIS2-2301 URL: https://issues.apache.org/jira/browse/AXIS2-2301 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: Addressing Affects Versions: 1.1.1 Reporter: Gee Chia Assigned To: Brian DePradine Fix For: nightly A Web service request worked in wsa 1.0 but failed in wsa 04 with AxisFault: A required message information header, To, MessageID, or Action, is not present. Basically, message ID was not set in MessageContext for a Response was the cause of the AxisFault. The exception was thrown from the checkForMandatoryHeaders method in the org.apache.axis2.handlers.addressing.AddressingSubmissionInHandler. As I understood from the code inspection,AbstractInOutSyncMessageReceiver::receive() method invokes MessageContext outMsgContext = MessageContextBuilder.createOutMessageContext(msgContext); The messageID is conditionally set in the outMsgContext. Then later on, it failed with messageID not set fault. The same transaction/request worked in wsa 1.0. It worked because AddressingFinalInHandler::checkForMandatoryHeaders only checks for Action only. My code worked in Axis2 1.1, but failed in nightly build. I checked Axis2 1.1.1, I saw AddressingSubmissionInHandler change was introduced in 1.1.1. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-1597) WAR deployment on WLS results in incorrect service configuration
[ https://issues.apache.org/jira/browse/AXIS2-1597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12481112 ] James Shiell commented on AXIS2-1597: - This is a classloader problem. The setup of the second service AAR (version.aar) is failing as the load of /META-INF/services.xml is picking up the services.xml of the previous AAR (which has OrderManagementWS). This occurs in the called to populateService at ~line 150 of DeploymentEngine. WAR deployment on WLS results in incorrect service configuration Key: AXIS2-1597 URL: https://issues.apache.org/jira/browse/AXIS2-1597 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: kernel Affects Versions: 1.1 Environment: WLS 9.2 Reporter: James Shiell Assigned To: Deepal Jayasinghe When Axis is deployed as a WAR on WLS 9.2 the service configuration mappings in AxisConfiguration appear to be bollocksed. I have two services (declared in the following order) - version.aar, and a custom Muse service, containing four services in a single service group. However, the AxisConfiguration object describes all services as having a filename of the version.aar file (full path). This breaks Muse, which tries to lookup the muse.xml in the service AAR, only to be directed to the wrong one by the configuration. This does not occur in an exploded deployment. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Real Asynchronous WebServices with JMS
Gil, Gul
This only happens with the persistent implementation of Sandesha.
So - I think you are making a really good point here, and I think we
need to add another approach to the callback model.
Currently the callback only takes an instance. Now, one approach is
that we could try to serialize that instance class. However, I think
thats not necessarily a scalable model.
I would rather that for the truly async case we pass in a class
instead of an instance.
Then the question is whether to leave it up to the user to store their
own state, or whether to help them. If we help them, I would rather
explicitly pass a java.io.Serializable or even better an XML document
and then inject it into the callback class. I think this ends up with
a more solid model than just trying to serialize the existing
callback.
e.g.
ServiceClient.sendReceiveNonBlocking(OMElement payload, Class
callbackClass, Serializable state);
then when the response comes back we do..
Callback callback = (Callback)callbackClass.newInstance();
if (callback instanceof Injectable) {
callback.setState(state);
}
callback.onComplete(result)
Paul
On 3/15/07, Paul Fremantle [EMAIL PROTECTED] wrote:
Gul
A while back we had a discussion about what happens if the system
crashes and sandesha then delivers the message after a restart. At
that point it was stated that when Sandesha is involved, it news up
instances instead of using saved callbacks.
I will check with the Sandesha gurus.
Paul
On 3/14/07, Gul Onural [EMAIL PROTECTED] wrote:
I have the same issue as Gilbert. We don't just want unblocking API,
but real async. API.
I took a quick look into Sandesha2 and I am trying to understand your
comments (reply to Gilbert)
on Sandesha2.
You say the behavior we want can be achieved using Sandesha2. But I am
not sure I truly understand rest of your
comments on Sandesha2. Can you elaborate a bit more ?
I believe that when you use Sandesha2 for reliable messaging you
get the behavior you want.
I agree that there ought to be a way of specifying a class or a
factory instead of an instance.
In that case it would be up to you to manage the correlation based
on looking inside the message.
Thanks.
-Original Message-
From: Paul Fremantle [mailto:[EMAIL PROTECTED]
Sent: Monday, March 12, 2007 7:06 PM
To: axis-user@ws.apache.org; axis-dev@ws.apache.org
Subject: Re: Real Asynchronous WebServices with JMS
Gilbert
We had a similar discussion to this about Sandesha2. I believe that when
you use Sandesha2 for reliable messaging you get the behaviour you want.
I agree that there ought to be a way of specifying a class or a factory
instead of an instance. In that case it would be up to you to manage the
correlation based on looking inside the message.
I guess at the moment you could implement what you desire by
implementing the response handling as a new service. Now you need to
start the JMS transport and Axis2 as a server at the client end
yourself, and find the EPR of the response service. Set this as the
replyTo of the outgoing request and then make a one-way invocation
against the real service.
Does that make sense? Effectively you are modelling the service as two
one-ways at the client side.
Paul
On 3/12/07, Gilbert Scheiblhofer [EMAIL PROTECTED] wrote:
Hi,
there is a lot information about asynchronous WS-calls using
asynchronous calls on client and transport level. I want to build
asynchronous WS-calls using JMS as transport and I don't think that
the current capabilities of axis2 are really asynchronous. The main
problem is that with axis2 asynchrounous calls are done using
callbacks, but whenever I use callbacks the client has to hold state
for this call. So this is not really asynchronous, it is just a
non-blocking API. What happens if the client shuts down before it
could process the response?
Is there any (easy) way to do real asynchrounous calls using JMS and
the JMSCorrelationId for the client to correlate the response to the
request. I'm thinking of a solution where the axis-stub should
instantiate the callback-object and additionally to the response
provides the correlation information.
Thanks,
Gilbert
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Paul Fremantle
VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
http://bloglines.com/blog/paulfremantle
[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
VP/Technology, WSO2 and
[Axis2] Parameter Oder and jaxws tests problem
Lets take this wsdl fragment. wsdl:message name=RequestMessage1 wsdl:part name=Part1 type=xsd:string/ wsdl:part name=Part2 type=xsd:string/ wsdl:part name=Part3 type=xsd:string/ /wsdl:message wsdl:message name=ResponseMessage1 wsdl:part name=Part4 type=xsd:string/ /wsdl:message ... wsdl:portType name=PortType1 wsdl:operation name=Operation1 parameterOrder=Part2 Part1 Part3 wsdl:input message=tns:RequestMessage1/ wsdl:output message=tns:ResponseMessage1/ /wsdl:operation /wsdl:portType Assume this portType binds to an rpc/literal type soap binding. Then the Request message should have parts Part1,Part2, Part3. What about the response Message? The wsdl spec says the only part we can miss should be the return type. Therefore the response message should have a part called *result* (instead of Part4 since it is the return type) Please correct me if I wrong. However In the current implementation I have made a mistake, So that the response does not include any parts. I belive this is wrong. The jaxws tests have a test called RPCProxyTests.java and it uses the RPCLit.wsdl. this wsdl contains similar cases as in above. eg. wsdl:message name=testListsRequest wsdl:part name=arg_0_0 type=impl:QNameList/ wsdl:part name=arg_1_0 type=impl:CalendarList/ wsdl:part name=arg_2_0 type=impl:StringList/ wsdl:part name=arg_3_0 type=impl:BigIntegerList/ wsdl:part name=arg_4_0 type=impl:LongList/ wsdl:part name=arg_5_0 type=impl:EnumList/ wsdl:part name=arg_7_0 type=impl:EnumList2/ wsdl:part name=arg_6_0 type=impl:complexAll/ /wsdl:message wsdl:message name=testCalendarList1Response wsdl:part name=testCalendarList1Return type=impl:CalendarList/ /wsdl:message wsdl:operation name=testLists parameterOrder=arg_0_0 arg_1_0 arg_2_0 arg_3_0 arg_4_0 arg_5_0 arg_7_0 arg_6_0 wsdl:input message=impl:testListsRequest name=testListsRequest/ wsdl:output message=impl:testListsResponse name=testListsResponse/ /wsdl:operation The problem is, When I fixed the earlier problem in WSDL11ToAxisServiceBuilder (i.e. to insert the return type) It seems This test case get fail. As a result of this I can not fix this bug and can someone please look into this test case? Can someone check whether it generates a part for *testCalendarList1Return* and similar parts as well. Thankx. Amila. -- Amila Suriarachchi, WSO2 Inc.
[jira] Commented: (AXIS2-1597) WAR deployment on WLS results in incorrect service configuration
[ https://issues.apache.org/jira/browse/AXIS2-1597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12481125 ] James Shiell commented on AXIS2-1597: - Got the bugger. This occurs if another META-INF/services.xml is accessible on the app-server classpath. As ClassLoader.getResource(..) will check the parent classloader first it results in this being read in preference to the service file. Hence the app-server accessible file is always returned. Hence you end up with the solutions: 1. Ensure no other META-INF/services.xml are accessible from the app-server CP, or 2. Override ClassLoader.getResource() in DeploymentClassLoader and ensure the local CP is checked first. WAR deployment on WLS results in incorrect service configuration Key: AXIS2-1597 URL: https://issues.apache.org/jira/browse/AXIS2-1597 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: kernel Affects Versions: 1.1 Environment: WLS 9.2 Reporter: James Shiell Assigned To: Deepal Jayasinghe When Axis is deployed as a WAR on WLS 9.2 the service configuration mappings in AxisConfiguration appear to be bollocksed. I have two services (declared in the following order) - version.aar, and a custom Muse service, containing four services in a single service group. However, the AxisConfiguration object describes all services as having a filename of the version.aar file (full path). This breaks Muse, which tries to lookup the muse.xml in the service AAR, only to be directed to the wrong one by the configuration. This does not occur in an exploded deployment. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-1749) Wrong Java2WSDL generation
[
https://issues.apache.org/jira/browse/AXIS2-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12481131
]
Geir Egil Hansen commented on AXIS2-1749:
-
With the patch installed on Axis2 1.1.1 I now get
xs:restriction base=ns:A
shouldn't it be
xs:extension base=ns:A
In my case, the sub-class is an extension to base rather than a restriction.
Is there any cases where restriction is necessary? Couldn't extension always be
used here?
I changed the patched a bit by replacing
XmlSchemaComplexContentRestriction complexRestriction = new
XmlSchemaComplexContentRestriction();
with
XmlSchemaComplexContentExtension complexExtension = new
XmlSchemaComplexContentExtension();
and of course replacing use of complexRestriction with complexExtension.
But the question is; When to use extension and when to use restriction, and how
to switch between the two?
Wrong Java2WSDL generation
--
Key: AXIS2-1749
URL: https://issues.apache.org/jira/browse/AXIS2-1749
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: codegen
Affects Versions: 1.1
Reporter: Jabber W
Assigned To: Deepal Jayasinghe
Attachments: axis2-1749and2116.txt, axis2patch1749and2116-v2.txt,
patch-1749.txt
During the generation of type definitions Java2WSDL of axis2-1.1 flattens
chains of extender java data types to independent schema types without
extending relations between them, while Axis121 stores these relations by
extension base.
For example: say,
class A { public String someString; public A someLink; } and
class B extends A { public int someInt; }
and the exposed service is:
class MySvc { String myOp(A arg) {..} }
Running of Java2WSDL on it:
java2wsdl -cn MySvc -xc B
creates 2 non-related types:
xs:complexType name=A
xs:sequence
xs:element name=someLink type=ns:A/
xs:element name=someString type=xs:string/
/xs:sequence
/xs:complexType
and
xs:complexType name=B
xs:sequence
xs:element name=someLink type=ns:A/
xs:element name=someString type=xs:string/
xs:element name=someInt type=xs:int/
/xs:sequence
/xs:complexType
while B should be:
xs:complexType name=B
xs:complexContent
xs:extension base=ns:A
xs:sequence
xs:element name=someInt type=xs:int/
/xs:sequence
/xs:extension
/xs:complexContent
/xs:complexType
Since complexType B is not extension of ? it (the B type element) can't be
passed as the someLink.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] Parameter Oder and jaxws tests problem
Nick, Rich, Thoughts please. thanks, dims On 3/15/07, Amila Suriarachchi [EMAIL PROTECTED] wrote: Lets take this wsdl fragment. wsdl:message name=RequestMessage1 wsdl:part name=Part1 type=xsd:string/ wsdl:part name=Part2 type=xsd:string/ wsdl:part name=Part3 type=xsd:string/ /wsdl:message wsdl:message name=ResponseMessage1 wsdl:part name=Part4 type=xsd:string/ /wsdl:message ... wsdl:portType name=PortType1 wsdl:operation name=Operation1 parameterOrder=Part2 Part1 Part3 wsdl:input message=tns:RequestMessage1/ wsdl:output message=tns:ResponseMessage1/ /wsdl:operation /wsdl:portType Assume this portType binds to an rpc/literal type soap binding. Then the Request message should have parts Part1,Part2, Part3. What about the response Message? The wsdl spec says the only part we can miss should be the return type. Therefore the response message should have a part called *result* (instead of Part4 since it is the return type) Please correct me if I wrong. However In the current implementation I have made a mistake, So that the response does not include any parts. I belive this is wrong. The jaxws tests have a test called RPCProxyTests.java and it uses the RPCLit.wsdl. this wsdl contains similar cases as in above. eg. wsdl:message name=testListsRequest wsdl:part name=arg_0_0 type=impl:QNameList/ wsdl:part name=arg_1_0 type=impl:CalendarList/ wsdl:part name=arg_2_0 type=impl:StringList/ wsdl:part name=arg_3_0 type=impl:BigIntegerList/ wsdl:part name=arg_4_0 type=impl:LongList/ wsdl:part name=arg_5_0 type=impl:EnumList/ wsdl:part name=arg_7_0 type=impl:EnumList2/ wsdl:part name=arg_6_0 type=impl:complexAll/ /wsdl:message wsdl:message name=testCalendarList1Response wsdl:part name=testCalendarList1Return type=impl:CalendarList/ /wsdl:message wsdl:operation name=testLists parameterOrder=arg_0_0 arg_1_0 arg_2_0 arg_3_0 arg_4_0 arg_5_0 arg_7_0 arg_6_0 wsdl:input message=impl:testListsRequest name=testListsRequest/ wsdl:output message=impl:testListsResponse name=testListsResponse/ /wsdl:operation The problem is, When I fixed the earlier problem in WSDL11ToAxisServiceBuilder ( i.e. to insert the return type) It seems This test case get fail. As a result of this I can not fix this bug and can someone please look into this test case? Can someone check whether it generates a part for *testCalendarList1Return* and similar parts as well. Thankx. Amila. -- Amila Suriarachchi, WSO2 Inc. -- Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [AXIS2] Wrong parameter names for mail transport in axis2.xml
Hi Samida,
I just wanted to say that if someone decides to comment out the mail
transport configuration from the axis2.xml file he could run into a trouble
because the parameter names there are not the same as defined in the
org.apache.axis2.transport.mail.Constants
and those are checked in the init() methods of the
org.apache.axis2.transport.mail.SimpleMailListener and
org.apache.axis2.transport.mail.MailTransportSender classes
Regards, Vasil
On 3/15/07, Saminda Abeyruwan [EMAIL PROTECTED] wrote:
Hi Vasil,
Thanks for using Axis2 mail transport. There are many properties that
could have come under transportReciever/ {SimpleMailListener} and
transportSender/ {MailTransportSender}. One could configure the transport
Sender or listener pragmatically or from the configuration file {
axis2.xml}.
As Axis2 uses Java Mail API for transport, Java Mail API uses Properties
to configure itself. Thus, if Axis2.xml is being used to configure this
transport each parameter will map to a property that you have set in the
Java Mail API. This will make life easier.
There could be many ways to configure Mail transport (SSL/NON-SSL), we
didn't put a default configuration in defaut_axis2.xml.
Please refer to mail-configuration.html and mail-transport.html to more
information.
Thank you
Saminda
On 3/15/07, Vasil Benov [EMAIL PROTECTED] wrote:
Hi axis2 devs,
I have found out that the parameter names in the axis2.xml for
configuring mail transport bear wrong names.
here the relevant sections from the axis2.xml file:
transportReceiver name=mail class=
org.apache.axis2.transport.mail.SimpleMailListener
parameter name=mail.store.protocol i think this parameter
is needed as well (it is missing in the default axis2.xml)
parameter name= transport.mail.pop3.host
locked=false127.0.0.1/parameter
= should read name=mail.pop3.host ...
parameter name=transport.mail.pop3.user
locked=falseaxis2/parameter= shuold read name=
mail.pop3.user ...
parameter name=transport.mail.pop3.password
locked=falseaxis2/parameter
parameter name=transport.mail.pop3.port
locked=false110/parameter = should read name=mail.pop3.port
/transportReceiver
transportSender name=mailto class=
org.apache.axis2.transport.mail.MailTransportSender
parameter name=transport.mail.smtp.host locked=false
127.0.0.1/parameter
= should read name= mail.smtp.host ...
parameter name=transport.mail.smtp.user
locked=falseaxis2/parameter = shuold read name=mail.smtp.user
...
parameter name= transport.mail.smtp.password
locked=falseaxis2/parameter
parameter name=transport.mail.smtp.port
locked=false25/parameter should read name= mail.pop3.port
/transportSender
Regards Vasil
--
Vasil Benov,
Mobile: +359(0)889/202682
@-mail: benovv at gmail dot com
ICQ: 140269988
GPG Fingerprint: 2CDC 5DA0 4C0A 7C06 5259 DE12 ACF3 177C 8906 0908
Public Key URL:
*) http://random.sks.keyserver.penguin.de/
--
Saminda Abeyruwan
Software Engineer
WSO2 Inc. - www.wso2.org
--
Vasil Benov,
Mobile: +359(0)889/202682
@-mail: benovv at gmail dot com
ICQ: 140269988
GPG Fingerprint: 2CDC 5DA0 4C0A 7C06 5259 DE12 ACF3 177C 8906 0908
Public Key URL:
*) http://random.sks.keyserver.penguin.de/
[jira] Commented: (AXIS2-2267) Adding utility APIs for Metadata Exchange
[
https://issues.apache.org/jira/browse/AXIS2-2267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12481180
]
Gee Chia commented on AXIS2-2267:
-
I have uploaded the new patch for this jira, and the code is available in JIRA
2281 patch.
Adding utility APIs for Metadata Exchange
--
Key: AXIS2-2267
URL: https://issues.apache.org/jira/browse/AXIS2-2267
Project: Axis 2.0 (Axis2)
Issue Type: Improvement
Components: modules
Affects Versions: nightly
Reporter: Gee Chia
Fix For: nightly
Attachments: MexUpdateFeb27Patch
The patch includes utility APIs and minor bug fixes described below:
org.apache.axis2.dataretrieval changes:
1. ServiceData - changed from protected interface/API to public (so
customized data locator has access to the APIs)
2. DataLocatorFactory (protected api changed to public )
3. DataRetrievalUtil::convertOMElement - throws exception to handle
the case when there is no ServiceData.xml to load
AxisService::getWSDL,
if (result != null result.length 0) - check length for non-empty
data result array
Mex Module (org.apache.axis2.mex package)
Basically, added fromOM mehtods to populate java class object from
OMElement, also following convenient APIs, and
clean-up.
1. MexUtil - new APIs
public static Metadata fromOM(OMElement omElement) throws
MexException{}
public static Metadata fromOM(OMElement omElement, String
mexNamespaceValue) throws MexException{
2. Metadata new APIs
public MetadataSection[] getMetadataSection(String dialect )
public MetadataSection[] getMetadataSection(String dialect, String
identifier)
public MetadataSection[] getMetadataSection(String dialect, String
identifier, OutputForm form)
3. Other misc changes/fixes
MetadataReference - Added getEPRElement, toOM deal with EPR, etc.
Message Receiver - dialet to dialect
Sample Usage:
Sample usage - Please refer java doc for details.
Metadata metadata = MexUtil.fromOM(result);
// Return all WSDL metadata sections
MetadataSection[] sections =
metadata.getMetadataSection(http://schemas.xmlsoap.org/wsdl/;);
// Return all inline WSDL metadata sections
metadata.getMetadataSection(http://schemas.xmlsoap.org/wsdl/;, null,
OutputForm.INLINE_FORM);
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-2267) Adding utility APIs for Metadata Exchange
[
https://issues.apache.org/jira/browse/AXIS2-2267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davanum Srinivas resolved AXIS2-2267.
-
Resolution: Fixed
Fixed in svn revision 518662
thanks,
dims
Adding utility APIs for Metadata Exchange
--
Key: AXIS2-2267
URL: https://issues.apache.org/jira/browse/AXIS2-2267
Project: Axis 2.0 (Axis2)
Issue Type: Improvement
Components: modules
Affects Versions: nightly
Reporter: Gee Chia
Fix For: nightly
Attachments: MexUpdateFeb27Patch
The patch includes utility APIs and minor bug fixes described below:
org.apache.axis2.dataretrieval changes:
1. ServiceData - changed from protected interface/API to public (so
customized data locator has access to the APIs)
2. DataLocatorFactory (protected api changed to public )
3. DataRetrievalUtil::convertOMElement - throws exception to handle
the case when there is no ServiceData.xml to load
AxisService::getWSDL,
if (result != null result.length 0) - check length for non-empty
data result array
Mex Module (org.apache.axis2.mex package)
Basically, added fromOM mehtods to populate java class object from
OMElement, also following convenient APIs, and
clean-up.
1. MexUtil - new APIs
public static Metadata fromOM(OMElement omElement) throws
MexException{}
public static Metadata fromOM(OMElement omElement, String
mexNamespaceValue) throws MexException{
2. Metadata new APIs
public MetadataSection[] getMetadataSection(String dialect )
public MetadataSection[] getMetadataSection(String dialect, String
identifier)
public MetadataSection[] getMetadataSection(String dialect, String
identifier, OutputForm form)
3. Other misc changes/fixes
MetadataReference - Added getEPRElement, toOM deal with EPR, etc.
Message Receiver - dialet to dialect
Sample Usage:
Sample usage - Please refer java doc for details.
Metadata metadata = MexUtil.fromOM(result);
// Return all WSDL metadata sections
MetadataSection[] sections =
metadata.getMetadataSection(http://schemas.xmlsoap.org/wsdl/;);
// Return all inline WSDL metadata sections
metadata.getMetadataSection(http://schemas.xmlsoap.org/wsdl/;, null,
OutputForm.INLINE_FORM);
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-2281) Adding configurable parameter for Metadata Exchange
[ https://issues.apache.org/jira/browse/AXIS2-2281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved AXIS2-2281. - Resolution: Fixed Fixed svn revision 518662 thanks, dims Adding configurable parameter for Metadata Exchange --- Key: AXIS2-2281 URL: https://issues.apache.org/jira/browse/AXIS2-2281 Project: Axis 2.0 (Axis2) Issue Type: Improvement Components: modules Affects Versions: 1.2 Reporter: Gee Chia Fix For: 1.2 Attachments: JIRA2281and2267PatchMar13, MEXPatchJira2281 This JIRA is to add configrable parameter for Metadata Exchange function. Following are the two configuration requirements that currently identified: a. Once metadataExchange module is engaged globally in axis2.xml, we need a way to disable GetMetadata request for a service. b. When a GetMetadata request is issued, the /mex:Metadata element returns multiple /mex:MetadataSection units. A MetadatSection could be either the embedded XML (inline), an endpoint reference to a Metadata Resource i.e. MetadataReference, or a URL i.e. Location element. The WS-MEX spec does not define what output forms: inline, Location or MetadataReference should be returned for a GetMetadata request. Currently, MexMessageReceiver just default to generating Metadata Sections for all the 3 possible output forms as stated in the spec. We need a way to configure the Metadata Section content to return for a GetMetadata request. For example, if there is large amount of data, large amount of inline xml might not be desirable. The outputform allows to configure only GetMetadata response with Metadata Sections of Metadata Reference and Location instead of actual information. Solution implemented: Adding metadataExchange element parameter configuration in axis2.xml and services.xml, allows to support the above configuration needs as well as future needs. Following are the configurables items: enable attribute - possible values: false. This is used to disable MEX support for a service. When disabled, MexDisabledException will be returned to the sender of GetMetadata request. outputform element contains optional dialect attribute and required forms attribute. possible values for forms: inline,location,reference.If not configured, default is inline,location, and reference. Note that the outputform only avoided unnessary processing in creating Metadata sections for data format that is not needed. As an example, parameter name=metadataExchange locked=false outputform dialect=http://schemas.xmlsoap.org/wsdl/; forms=inline,location / outputform forms=reference,location / /parameter If the above configuration is added to the axis2.xml, this means the GetMetadata response will contain Metadata Sections of actual WSDL data, and URL for the WSDL dialect, and for other dialects such as policy, schema, etc., only Metadata Sections with MetadataReference and Location will be included in the response. The order of precedence for the output form will be similar to the data locator look-up: a. dialect specific at service level i.e. configured in services.xml b. service level i.e. without dialect attribute specified c. dialect specific at global level i,e, configured in axis2.xml d. service level i.e. without dialect attribute specified e. default output forms to all: inline, location, reference Summary of code changes: New class: org.apache.axis2.mex.MexDisabledException Modified classes: MexConstants - adding constants for configurable items refere in metadataExchange parameter MexMessageReceiver - Access the parameter axis configuration and service configuration Check if MEX is disabled before processing Call MexUtil.determineOutputForm(..) instead of default to all 3 output forms. MexUtil: Added APIs: determineOutputForm(..), check_MEX_disabled() -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL
Re: [Axis2] Parameter Oder and jaxws tests problem
Amila, Assume this portType binds to an rpc/literal type soap binding. Then the Request message should have parts Part1,Part2, Part3. What about the response Message? The wsdl spec says the only part we can miss should be the return type. Yes, the request would have each of those parts and they should follow the parameter order defined in the wsdl:operation. This is fine per section 2.4.6 of the WSDL spec [1]. The response would contain the single part defined in the response message, which is not included in the parameter order. Therefore the response message should have a part called *result* (instead of Part4 since it is the return type) Please correct me if I wrong. I wasn't able to find anything in the spec that dictates the name of the return part. My interpretation has always been that if there is one part, and that part doesn't match any of the parts defined in the request, then it is the return type. If it DOES match a request part, then it's an INOUT param rather than a return. Is there a section of the spec that I'm missing that dictates that part name (not saying there isn't, I could just be missing it)? [1] - http://www.w3.org/TR/wsdl#_parameter Regards, -Nick Amila Suriarachchi [EMAIL PROTECTED] 03/15/2007 07:22 AM Please respond to axis-user@ws.apache.org To axis-user@ws.apache.org, axis-dev@ws.apache.org cc Subject [Axis2] Parameter Oder and jaxws tests problem Lets take this wsdl fragment. wsdl:message name=RequestMessage1 wsdl:part name=Part1 type=xsd:string/ wsdl:part name=Part2 type=xsd:string/ wsdl:part name=Part3 type=xsd:string/ /wsdl:message wsdl:message name=ResponseMessage1 wsdl:part name=Part4 type=xsd:string/ /wsdl:message ... wsdl:portType name=PortType1 wsdl:operation name=Operation1 parameterOrder=Part2 Part1 Part3 wsdl:input message=tns:RequestMessage1/ wsdl:output message=tns:ResponseMessage1/ /wsdl:operation /wsdl:portType Assume this portType binds to an rpc/literal type soap binding. Then the Request message should have parts Part1,Part2, Part3. What about the response Message? The wsdl spec says the only part we can miss should be the return type. Therefore the response message should have a part called *result* (instead of Part4 since it is the return type) Please correct me if I wrong. However In the current implementation I have made a mistake, So that the response does not include any parts. I belive this is wrong. The jaxws tests have a test called RPCProxyTests.java and it uses the RPCLit.wsdl. this wsdl contains similar cases as in above. eg. wsdl:message name=testListsRequest wsdl:part name=arg_0_0 type=impl:QNameList/ wsdl:part name=arg_1_0 type=impl:CalendarList/ wsdl:part name=arg_2_0 type=impl:StringList/ wsdl:part name=arg_3_0 type=impl:BigIntegerList/ wsdl:part name=arg_4_0 type=impl:LongList/ wsdl:part name=arg_5_0 type=impl:EnumList/ wsdl:part name=arg_7_0 type=impl:EnumList2/ wsdl:part name=arg_6_0 type=impl:complexAll/ /wsdl:message wsdl:message name=testCalendarList1Response wsdl:part name=testCalendarList1Return type=impl:CalendarList/ /wsdl:message wsdl:operation name=testLists parameterOrder=arg_0_0 arg_1_0 arg_2_0 arg_3_0 arg_4_0 arg_5_0 arg_7_0 arg_6_0 wsdl:input message=impl:testListsRequest name=testListsRequest/ wsdl:output message=impl:testListsResponse name=testListsResponse/ /wsdl:operation The problem is, When I fixed the earlier problem in WSDL11ToAxisServiceBuilder ( i.e. to insert the return type) It seems This test case get fail. As a result of this I can not fix this bug and can someone please look into this test case? Can someone check whether it generates a part for *testCalendarList1Return* and similar parts as well. Thankx. Amila. -- Amila Suriarachchi, WSO2 Inc.
[Axis2]package name is used as the targetNamespace
Hi,
We had the titled prob for a little while during the axis2 integration
work into geronimo and I'd like to get some advise from the axis2 list,
as we feel it is most appropriate to fix this in axis2.
I have a HelloWorld.java that has this:
package test.mypackage;
import javax.jws.WebMethod;
import javax.jws.WebService;
@WebService(name=HelloWorld, targetNamespace =
http://example.org/hello/xsd;)
public class HelloWorld {
@WebMethod
public String sayHello(String me){
return Hello +me;
}
}
However, when I request the wsdl...I get something like this:
wsdl:definitions targetNamespace=http://mypackage.test/xsd;
...
Notice the targetnamespace was munged and changed from it's originally
declared namespace of http://example.com/hello/xsd;. I want the one
that is both declared in the included wsdl (or the one declared in the
annotation).
So in the geronimo integration code, when .wsdl file isn't in the app
war file, we call
AxisService.createService(endpointClassName,configurationContext.getAxisConfiguration(),JAXWSMessageReceiver.class);
By stepping through the code, the above line will call construct an
SchemaGenerator object. Since schemaTargetNameSpace is null,
Java2WSDLUtils.schemaNamespaceFromClassName is called and it seems to
create the namespace based on the package name, insted of what 's
specified in the annotation.
Can someone please confirm if that is the expected behavior of the
Java2WSDLUtils? Is the tool designed not to process any of the
annotation stuff?
Thanks, Lin
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-2329) Invocation of a non-existing method
[
https://issues.apache.org/jira/browse/AXIS2-2329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12481262
]
Karl Philipp commented on AXIS2-2329:
-
Sorry, the code snipped extracted from the java class named
AddServicePortServiceMessageReceiverInOut.java
is incomplete:
private net.mycompany.ei.messaging.datatypes.EIMessageContext
getEiMessageContext(
net.mycompany.crm.contract.services.addservice.AddService0 wrappedType){
return wrappedType.getAddService0().getEiMessageContext();
}
Invocation of a non-existing method
---
Key: AXIS2-2329
URL: https://issues.apache.org/jira/browse/AXIS2-2329
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: adb
Affects Versions: 1.1.1
Environment: Windows XP Professional Service Pack 2, Ant 1.6.5
Reporter: Karl Philipp
Using (Ant snippet)
java classname=org.apache.axis2.wsdl.WSDL2Java fork=true
maxmemory=1024m
arg line=-uri wsdl/${service}Port.wsdl -o ${service}
-d adb -wv 1.1 -ss -uw/
classpath
fileset dir=${axis2.dir}/lib
include name=*.jar /
/fileset
/classpath
/java
a java class named
AddServicePortServiceMessageReceiverInOut.java
is generated that does a call of a method named getAddService0() as stated
below:
net.mycompany.crm.contract.services.addservice.AddService0 wrappedType){
return wrappedType.getAddService0().getEiMessageContext();
}
But the java class AddService0 contains only a method named
public net.mycompany.crm.contract.services.addservice.AddService
getAddService()
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-2329) Invocation of a non-existing method
Invocation of a non-existing method
---
Key: AXIS2-2329
URL: https://issues.apache.org/jira/browse/AXIS2-2329
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: adb
Affects Versions: 1.1.1
Environment: Windows XP Professional Service Pack 2, Ant 1.6.5
Reporter: Karl Philipp
Using (Ant snippet)
java classname=org.apache.axis2.wsdl.WSDL2Java fork=true
maxmemory=1024m
arg line=-uri wsdl/${service}Port.wsdl -o ${service}
-d adb -wv 1.1 -ss -uw/
classpath
fileset dir=${axis2.dir}/lib
include name=*.jar /
/fileset
/classpath
/java
a java class named
AddServicePortServiceMessageReceiverInOut.java
is generated that does a call of a method named getAddService0() as stated
below:
net.mycompany.crm.contract.services.addservice.AddService0 wrappedType){
return wrappedType.getAddService0().getEiMessageContext();
}
But the java class AddService0 contains only a method named
public net.mycompany.crm.contract.services.addservice.AddService
getAddService()
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-1749) Wrong Java2WSDL generation
[
https://issues.apache.org/jira/browse/AXIS2-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12481280
]
Manoj Khangaonkar commented on AXIS2-1749:
--
Gier,
I meant it to be ComplexExtension , but looks like I made it
ComplexRestriction. Good catch.
In java derived types extend base types - hence extension
Since this is java2WSDL - how do you model restriction in java ? In other
words, can you think of a case in java code
where the corresponding schema needs to be restriction.
I will update the patch to generate xs:extension base=
but if you have a use case for restriction, let me know
Mj
Wrong Java2WSDL generation
--
Key: AXIS2-1749
URL: https://issues.apache.org/jira/browse/AXIS2-1749
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: codegen
Affects Versions: 1.1
Reporter: Jabber W
Assigned To: Deepal Jayasinghe
Attachments: axis2-1749and2116.txt, axis2patch1749and2116-v2.txt,
patch-1749.txt
During the generation of type definitions Java2WSDL of axis2-1.1 flattens
chains of extender java data types to independent schema types without
extending relations between them, while Axis121 stores these relations by
extension base.
For example: say,
class A { public String someString; public A someLink; } and
class B extends A { public int someInt; }
and the exposed service is:
class MySvc { String myOp(A arg) {..} }
Running of Java2WSDL on it:
java2wsdl -cn MySvc -xc B
creates 2 non-related types:
xs:complexType name=A
xs:sequence
xs:element name=someLink type=ns:A/
xs:element name=someString type=xs:string/
/xs:sequence
/xs:complexType
and
xs:complexType name=B
xs:sequence
xs:element name=someLink type=ns:A/
xs:element name=someString type=xs:string/
xs:element name=someInt type=xs:int/
/xs:sequence
/xs:complexType
while B should be:
xs:complexType name=B
xs:complexContent
xs:extension base=ns:A
xs:sequence
xs:element name=someInt type=xs:int/
/xs:sequence
/xs:extension
/xs:complexContent
/xs:complexType
Since complexType B is not extension of ? it (the B type element) can't be
passed as the someLink.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-2330) NPE in SchemaReaderImpl
NPE in SchemaReaderImpl --- Key: AXIS2-2330 URL: https://issues.apache.org/jira/browse/AXIS2-2330 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Reporter: Nikhil Thaker Assigned To: Nikhil Thaker Attachments: JIRA_2330_NPEinSchemaReaderImpl.txt Detailed description Heres the stack trace for the issue: ERROR: javax.xml.ws.WebServiceException: java.lang.NullPointerException at org.apache.axis2.jaxws.ExceptionFactory.createWebServiceException(ExceptionFactory.java:179) at org.apache.axis2.jaxws.ExceptionFactory.makeWebServiceException(ExceptionFactory.java:79) at org.apache.axis2.jaxws.ExceptionFactory.makeWebServiceException(ExceptionFactory.java:133) at org.apache.axis2.jaxws.marshaller.impl.alt.DocLitBareMethodMarshaller.marshalRequest(DocLitBareMethodMarshaller.java :316) at org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.createRequest(JAXWSProxyHandler.java:308) at org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.invokeSEIMethod(JAXWSProxyHandler.java:159) at org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.invoke(JAXWSProxyHandler.java:142) at $Proxy9.echoAnySimpleTypeTest(Unknown Source) at com.sun.ts.tests.jaxws.ee.w2j.document.literal.marshalltest.Client.MarshallAnySimpleTypeTest(Client.java:749) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:615) at com.sun.ts.lib.harness.EETest.run(EETest.java:495) at com.sun.ts.lib.harness.ServiceEETest.run(ServiceEETest.java:112) at com.sun.ts.tests.common.vehicle.EmptyVehicleRunner.run(EmptyVehicleRunner.java:30) at com.sun.ts.lib.harness.ServiceEETest.run(ServiceEETest.java:102) at com.sun.ts.lib.harness.EETest.getPropsReady(EETest.java:392) at com.sun.ts.lib.harness.ServiceEETest.run(ServiceEETest.java:209) at com.sun.ts.lib.harness.EETest.run(EETest.java:204) at com.sun.ts.tests.common.vehicle.VehicleClient.main(VehicleClient.java:27) Caused by: java.lang.NullPointerException at org.apache.axis2.jaxws.wsdl.impl.SchemaReaderImpl.readSchemaBindingPackageName(SchemaReaderImpl.java:166) at org.apache.axis2.jaxws.wsdl.impl.SchemaReaderImpl.processSchema(SchemaReaderImpl.java:103) at org.apache.axis2.jaxws.wsdl.impl.SchemaReaderImpl.processImport(SchemaReaderImpl.java:142) at org.apache.axis2.jaxws.wsdl.impl.SchemaReaderImpl.processSchema(SchemaReaderImpl.java:135) at org.apache.axis2.jaxws.wsdl.impl.SchemaReaderImpl.processImport(SchemaReaderImpl.java:142) at org.apache.axis2.jaxws.wsdl.impl.SchemaReaderImpl.processSchema(SchemaReaderImpl.java:135) at org.apache.axis2.jaxws.wsdl.impl.SchemaReaderImpl.readPackagesFromSchema(SchemaReaderImpl.java:88) at org.apache.axis2.jaxws.runtime.description.marshal.impl.PackageSetBuilder.getPackagesFromSchema(PackageSetBuilder.ja va:123) at org.apache.axis2.jaxws.runtime.description.marshal.impl.MarshalServiceRuntimeDescriptionBuilder.init(MarshalServiceR untimeDescriptionBuilder.java:123) at org.apache.axis2.jaxws.runtime.description.marshal.impl.MarshalServiceRuntimeDescriptionBuilder.create(MarshalServic eRuntimeDescriptionBuilder.java:59) at org.apache.axis2.jaxws.runtime.description.marshal.MarshalServiceRuntimeDescriptionFactory.get(MarshalServiceRuntime DescriptionFactory.java:42) at org.apache.axis2.jaxws.marshaller.impl.alt.MethodMarshallerUtils.getMarshalDesc(MethodMarshallerUtils.java:988) at org.apache.axis2.jaxws.marshaller.impl.alt.DocLitBareMethodMarshaller.marshalRequest(DocLitBareMethodMarshaller.java :277) ... 17 more I will provide fix for this issue. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-2330) NPE in SchemaReaderImpl
[ https://issues.apache.org/jira/browse/AXIS2-2330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikhil Thaker updated AXIS2-2330: - Attachment: JIRA_2330_NPEinSchemaReaderImpl.txt NPE in SchemaReaderImpl --- Key: AXIS2-2330 URL: https://issues.apache.org/jira/browse/AXIS2-2330 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Reporter: Nikhil Thaker Assigned To: Nikhil Thaker Attachments: JIRA_2330_NPEinSchemaReaderImpl.txt Detailed description Heres the stack trace for the issue: ERROR: javax.xml.ws.WebServiceException: java.lang.NullPointerException at org.apache.axis2.jaxws.ExceptionFactory.createWebServiceException(ExceptionFactory.java:179) at org.apache.axis2.jaxws.ExceptionFactory.makeWebServiceException(ExceptionFactory.java:79) at org.apache.axis2.jaxws.ExceptionFactory.makeWebServiceException(ExceptionFactory.java:133) at org.apache.axis2.jaxws.marshaller.impl.alt.DocLitBareMethodMarshaller.marshalRequest(DocLitBareMethodMarshaller.java :316) at org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.createRequest(JAXWSProxyHandler.java:308) at org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.invokeSEIMethod(JAXWSProxyHandler.java:159) at org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.invoke(JAXWSProxyHandler.java:142) at $Proxy9.echoAnySimpleTypeTest(Unknown Source) at com.sun.ts.tests.jaxws.ee.w2j.document.literal.marshalltest.Client.MarshallAnySimpleTypeTest(Client.java:749) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:615) at com.sun.ts.lib.harness.EETest.run(EETest.java:495) at com.sun.ts.lib.harness.ServiceEETest.run(ServiceEETest.java:112) at com.sun.ts.tests.common.vehicle.EmptyVehicleRunner.run(EmptyVehicleRunner.java:30) at com.sun.ts.lib.harness.ServiceEETest.run(ServiceEETest.java:102) at com.sun.ts.lib.harness.EETest.getPropsReady(EETest.java:392) at com.sun.ts.lib.harness.ServiceEETest.run(ServiceEETest.java:209) at com.sun.ts.lib.harness.EETest.run(EETest.java:204) at com.sun.ts.tests.common.vehicle.VehicleClient.main(VehicleClient.java:27) Caused by: java.lang.NullPointerException at org.apache.axis2.jaxws.wsdl.impl.SchemaReaderImpl.readSchemaBindingPackageName(SchemaReaderImpl.java:166) at org.apache.axis2.jaxws.wsdl.impl.SchemaReaderImpl.processSchema(SchemaReaderImpl.java:103) at org.apache.axis2.jaxws.wsdl.impl.SchemaReaderImpl.processImport(SchemaReaderImpl.java:142) at org.apache.axis2.jaxws.wsdl.impl.SchemaReaderImpl.processSchema(SchemaReaderImpl.java:135) at org.apache.axis2.jaxws.wsdl.impl.SchemaReaderImpl.processImport(SchemaReaderImpl.java:142) at org.apache.axis2.jaxws.wsdl.impl.SchemaReaderImpl.processSchema(SchemaReaderImpl.java:135) at org.apache.axis2.jaxws.wsdl.impl.SchemaReaderImpl.readPackagesFromSchema(SchemaReaderImpl.java:88) at org.apache.axis2.jaxws.runtime.description.marshal.impl.PackageSetBuilder.getPackagesFromSchema(PackageSetBuilder.ja va:123) at org.apache.axis2.jaxws.runtime.description.marshal.impl.MarshalServiceRuntimeDescriptionBuilder.init(MarshalServiceR untimeDescriptionBuilder.java:123) at org.apache.axis2.jaxws.runtime.description.marshal.impl.MarshalServiceRuntimeDescriptionBuilder.create(MarshalServic eRuntimeDescriptionBuilder.java:59) at org.apache.axis2.jaxws.runtime.description.marshal.MarshalServiceRuntimeDescriptionFactory.get(MarshalServiceRuntime DescriptionFactory.java:42) at org.apache.axis2.jaxws.marshaller.impl.alt.MethodMarshallerUtils.getMarshalDesc(MethodMarshallerUtils.java:988) at org.apache.axis2.jaxws.marshaller.impl.alt.DocLitBareMethodMarshaller.marshalRequest(DocLitBareMethodMarshaller.java :277) ... 17 more I will provide fix for this issue. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-2330) NPE in SchemaReaderImpl
[ https://issues.apache.org/jira/browse/AXIS2-2330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikhil Thaker resolved AXIS2-2330. -- Resolution: Fixed Patch applied revision #518743 NPE in SchemaReaderImpl --- Key: AXIS2-2330 URL: https://issues.apache.org/jira/browse/AXIS2-2330 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Reporter: Nikhil Thaker Assigned To: Nikhil Thaker Attachments: JIRA_2330_NPEinSchemaReaderImpl.txt Detailed description Heres the stack trace for the issue: ERROR: javax.xml.ws.WebServiceException: java.lang.NullPointerException at org.apache.axis2.jaxws.ExceptionFactory.createWebServiceException(ExceptionFactory.java:179) at org.apache.axis2.jaxws.ExceptionFactory.makeWebServiceException(ExceptionFactory.java:79) at org.apache.axis2.jaxws.ExceptionFactory.makeWebServiceException(ExceptionFactory.java:133) at org.apache.axis2.jaxws.marshaller.impl.alt.DocLitBareMethodMarshaller.marshalRequest(DocLitBareMethodMarshaller.java :316) at org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.createRequest(JAXWSProxyHandler.java:308) at org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.invokeSEIMethod(JAXWSProxyHandler.java:159) at org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.invoke(JAXWSProxyHandler.java:142) at $Proxy9.echoAnySimpleTypeTest(Unknown Source) at com.sun.ts.tests.jaxws.ee.w2j.document.literal.marshalltest.Client.MarshallAnySimpleTypeTest(Client.java:749) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:615) at com.sun.ts.lib.harness.EETest.run(EETest.java:495) at com.sun.ts.lib.harness.ServiceEETest.run(ServiceEETest.java:112) at com.sun.ts.tests.common.vehicle.EmptyVehicleRunner.run(EmptyVehicleRunner.java:30) at com.sun.ts.lib.harness.ServiceEETest.run(ServiceEETest.java:102) at com.sun.ts.lib.harness.EETest.getPropsReady(EETest.java:392) at com.sun.ts.lib.harness.ServiceEETest.run(ServiceEETest.java:209) at com.sun.ts.lib.harness.EETest.run(EETest.java:204) at com.sun.ts.tests.common.vehicle.VehicleClient.main(VehicleClient.java:27) Caused by: java.lang.NullPointerException at org.apache.axis2.jaxws.wsdl.impl.SchemaReaderImpl.readSchemaBindingPackageName(SchemaReaderImpl.java:166) at org.apache.axis2.jaxws.wsdl.impl.SchemaReaderImpl.processSchema(SchemaReaderImpl.java:103) at org.apache.axis2.jaxws.wsdl.impl.SchemaReaderImpl.processImport(SchemaReaderImpl.java:142) at org.apache.axis2.jaxws.wsdl.impl.SchemaReaderImpl.processSchema(SchemaReaderImpl.java:135) at org.apache.axis2.jaxws.wsdl.impl.SchemaReaderImpl.processImport(SchemaReaderImpl.java:142) at org.apache.axis2.jaxws.wsdl.impl.SchemaReaderImpl.processSchema(SchemaReaderImpl.java:135) at org.apache.axis2.jaxws.wsdl.impl.SchemaReaderImpl.readPackagesFromSchema(SchemaReaderImpl.java:88) at org.apache.axis2.jaxws.runtime.description.marshal.impl.PackageSetBuilder.getPackagesFromSchema(PackageSetBuilder.ja va:123) at org.apache.axis2.jaxws.runtime.description.marshal.impl.MarshalServiceRuntimeDescriptionBuilder.init(MarshalServiceR untimeDescriptionBuilder.java:123) at org.apache.axis2.jaxws.runtime.description.marshal.impl.MarshalServiceRuntimeDescriptionBuilder.create(MarshalServic eRuntimeDescriptionBuilder.java:59) at org.apache.axis2.jaxws.runtime.description.marshal.MarshalServiceRuntimeDescriptionFactory.get(MarshalServiceRuntime DescriptionFactory.java:42) at org.apache.axis2.jaxws.marshaller.impl.alt.MethodMarshallerUtils.getMarshalDesc(MethodMarshallerUtils.java:988) at org.apache.axis2.jaxws.marshaller.impl.alt.DocLitBareMethodMarshaller.marshalRequest(DocLitBareMethodMarshaller.java :277) ... 17 more I will provide fix for this issue. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (AXIS2-2330) NPE in SchemaReaderImpl
[ https://issues.apache.org/jira/browse/AXIS2-2330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikhil Thaker closed AXIS2-2330. NPE in SchemaReaderImpl --- Key: AXIS2-2330 URL: https://issues.apache.org/jira/browse/AXIS2-2330 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Reporter: Nikhil Thaker Assigned To: Nikhil Thaker Attachments: JIRA_2330_NPEinSchemaReaderImpl.txt Detailed description Heres the stack trace for the issue: ERROR: javax.xml.ws.WebServiceException: java.lang.NullPointerException at org.apache.axis2.jaxws.ExceptionFactory.createWebServiceException(ExceptionFactory.java:179) at org.apache.axis2.jaxws.ExceptionFactory.makeWebServiceException(ExceptionFactory.java:79) at org.apache.axis2.jaxws.ExceptionFactory.makeWebServiceException(ExceptionFactory.java:133) at org.apache.axis2.jaxws.marshaller.impl.alt.DocLitBareMethodMarshaller.marshalRequest(DocLitBareMethodMarshaller.java :316) at org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.createRequest(JAXWSProxyHandler.java:308) at org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.invokeSEIMethod(JAXWSProxyHandler.java:159) at org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.invoke(JAXWSProxyHandler.java:142) at $Proxy9.echoAnySimpleTypeTest(Unknown Source) at com.sun.ts.tests.jaxws.ee.w2j.document.literal.marshalltest.Client.MarshallAnySimpleTypeTest(Client.java:749) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:615) at com.sun.ts.lib.harness.EETest.run(EETest.java:495) at com.sun.ts.lib.harness.ServiceEETest.run(ServiceEETest.java:112) at com.sun.ts.tests.common.vehicle.EmptyVehicleRunner.run(EmptyVehicleRunner.java:30) at com.sun.ts.lib.harness.ServiceEETest.run(ServiceEETest.java:102) at com.sun.ts.lib.harness.EETest.getPropsReady(EETest.java:392) at com.sun.ts.lib.harness.ServiceEETest.run(ServiceEETest.java:209) at com.sun.ts.lib.harness.EETest.run(EETest.java:204) at com.sun.ts.tests.common.vehicle.VehicleClient.main(VehicleClient.java:27) Caused by: java.lang.NullPointerException at org.apache.axis2.jaxws.wsdl.impl.SchemaReaderImpl.readSchemaBindingPackageName(SchemaReaderImpl.java:166) at org.apache.axis2.jaxws.wsdl.impl.SchemaReaderImpl.processSchema(SchemaReaderImpl.java:103) at org.apache.axis2.jaxws.wsdl.impl.SchemaReaderImpl.processImport(SchemaReaderImpl.java:142) at org.apache.axis2.jaxws.wsdl.impl.SchemaReaderImpl.processSchema(SchemaReaderImpl.java:135) at org.apache.axis2.jaxws.wsdl.impl.SchemaReaderImpl.processImport(SchemaReaderImpl.java:142) at org.apache.axis2.jaxws.wsdl.impl.SchemaReaderImpl.processSchema(SchemaReaderImpl.java:135) at org.apache.axis2.jaxws.wsdl.impl.SchemaReaderImpl.readPackagesFromSchema(SchemaReaderImpl.java:88) at org.apache.axis2.jaxws.runtime.description.marshal.impl.PackageSetBuilder.getPackagesFromSchema(PackageSetBuilder.ja va:123) at org.apache.axis2.jaxws.runtime.description.marshal.impl.MarshalServiceRuntimeDescriptionBuilder.init(MarshalServiceR untimeDescriptionBuilder.java:123) at org.apache.axis2.jaxws.runtime.description.marshal.impl.MarshalServiceRuntimeDescriptionBuilder.create(MarshalServic eRuntimeDescriptionBuilder.java:59) at org.apache.axis2.jaxws.runtime.description.marshal.MarshalServiceRuntimeDescriptionFactory.get(MarshalServiceRuntime DescriptionFactory.java:42) at org.apache.axis2.jaxws.marshaller.impl.alt.MethodMarshallerUtils.getMarshalDesc(MethodMarshallerUtils.java:988) at org.apache.axis2.jaxws.marshaller.impl.alt.DocLitBareMethodMarshaller.marshalRequest(DocLitBareMethodMarshaller.java :277) ... 17 more I will provide fix for this issue. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Fwd: Real Asynchronous WebServices with JMS
[Hadn't copied to the dev list]
-- Forwarded message --
From: Chamikara Jayalath [EMAIL PROTECTED]
Date: Mar 15, 2007 7:16 PM
Subject: Re: Real Asynchronous WebServices with JMS
To: Gul Onural [EMAIL PROTECTED]
Cc: axis-user@ws.apache.org
Hi All,
I also believe that passing a class than the instance will be a better
approach here. Letting the user pass the object kind of conveys that we will
be preserving the state, which we actually will not be doing.
We still couldn't commit the persistent implementation of the Sandesha2
StorageManager to Apache due to it's dependency on Hibernate. Apache legal
team informed us that we have to wait till some legal issues are solved.
Till then the code is available at [1].
Also +1 for Paul's suggestion to let the user pass an Serializable object
(or an XML) to be managed by the persistence layer.
Chamikara
[1] http://wso2.org/repos/wso2/trunk/commons/sandesha2-persistence/
On 3/15/07, Gul Onural [EMAIL PROTECTED] wrote:
I know the WS-RM is not particularly concerned with async. invocation of
web services, but passing class instead of an instance would make
Sandesha2 quite usable for asynchrony purposes.
Any comments from Sandesha2 gurus ? I assume Chamikara is copied to
provide comments ?
Gul
-Original Message-
From: Paul Fremantle [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 15, 2007 7:55 AM
To: axis-user@ws.apache.org
Cc: axis-dev@ws.apache.org; Chamikara Jayalath
Subject: Re: Real Asynchronous WebServices with JMS
Gil, Gul
This only happens with the persistent implementation of Sandesha.
So - I think you are making a really good point here, and I think we
need to add another approach to the callback model.
Currently the callback only takes an instance. Now, one approach is that
we could try to serialize that instance class. However, I think thats
not necessarily a scalable model.
I would rather that for the truly async case we pass in a class instead
of an instance.
Then the question is whether to leave it up to the user to store their
own state, or whether to help them. If we help them, I would rather
explicitly pass a java.io.Serializable or even better an XML document
and then inject it into the callback class. I think this ends up with a
more solid model than just trying to serialize the existing callback.
e.g.
ServiceClient.sendReceiveNonBlocking(OMElement payload, Class
callbackClass, Serializable state);
then when the response comes back we do..
Callback callback = (Callback)callbackClass.newInstance();
if (callback instanceof Injectable) {
callback.setState(state);
}
callback.onComplete(result)
Paul
On 3/15/07, Paul Fremantle [EMAIL PROTECTED] wrote:
Gul
A while back we had a discussion about what happens if the system
crashes and sandesha then delivers the message after a restart. At
that point it was stated that when Sandesha is involved, it news up
instances instead of using saved callbacks.
I will check with the Sandesha gurus.
Paul
On 3/14/07, Gul Onural [EMAIL PROTECTED] wrote:
I have the same issue as Gilbert. We don't just want unblocking
API, but real async. API.
I took a quick look into Sandesha2 and I am trying to understand
your comments (reply to Gilbert) on Sandesha2.
You say the behavior we want can be achieved using Sandesha2. But I
am not sure I truly understand rest of your comments on Sandesha2.
Can you elaborate a bit more ?
I believe that when you use Sandesha2 for reliable messaging
you get the behavior you want.
I agree that there ought to be a way of specifying a class or
a factory instead of an instance.
In that case it would be up to you to manage the correlation
based on looking inside the message.
Thanks.
-Original Message-
From: Paul Fremantle [mailto:[EMAIL PROTECTED]
Sent: Monday, March 12, 2007 7:06 PM
To: axis-user@ws.apache.org; axis-dev@ws.apache.org
Subject: Re: Real Asynchronous WebServices with JMS
Gilbert
We had a similar discussion to this about Sandesha2. I believe that
when you use Sandesha2 for reliable messaging you get the behaviour
you want.
I agree that there ought to be a way of specifying a class or a
factory instead of an instance. In that case it would be up to you
to manage the correlation based on looking inside the message.
I guess at the moment you could implement what you desire by
implementing the response handling as a new service. Now you need to
start the JMS transport and Axis2 as a server at the client end
yourself, and find the EPR of the response service. Set this as
the replyTo of the outgoing request and then make a one-way
invocation against the real service.
Does that make sense? Effectively you are modelling the service as
two one-ways at the client side.
Paul
On 3/12/07, Gilbert Scheiblhofer [EMAIL PROTECTED]
wrote:
Hi,
there is a lot information about asynchronous WS-calls using
[jira] Updated: (AXIS2-2293) Update the resource.properties files
[ https://issues.apache.org/jira/browse/AXIS2-2293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ming Cheung updated AXIS2-2293: --- Attachment: patch_os_424436_1_0314b.txt Ann Robinson I both found a build failure from previous patch. Hence, I upload this patch to correct the build break. Update the resource.properties files Key: AXIS2-2293 URL: https://issues.apache.org/jira/browse/AXIS2-2293 Project: Axis 2.0 (Axis2) Issue Type: Improvement Components: jaxws, kernel Environment: no special environment needs Reporter: Ming Cheung Assigned To: Ann Robinson Attachments: patch_d424436_0306.txt, patch_os_424436_1_0314.txt, patch_os_424436_1_0314a.txt, patch_os_424436_1_0314b.txt Updated and removed some of the i18n messages from both kernal and medata bundles. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-2329) Invocation of a non-existing method
[
https://issues.apache.org/jira/browse/AXIS2-2329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12481414
]
Davanum Srinivas commented on AXIS2-2329:
-
Karl,
Can you please upload your wsdl/xsd's?
thanks,
dims
Invocation of a non-existing method
---
Key: AXIS2-2329
URL: https://issues.apache.org/jira/browse/AXIS2-2329
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: adb
Affects Versions: 1.1.1
Environment: Windows XP Professional Service Pack 2, Ant 1.6.5
Reporter: Karl Philipp
Using (Ant snippet)
java classname=org.apache.axis2.wsdl.WSDL2Java fork=true
maxmemory=1024m
arg line=-uri wsdl/${service}Port.wsdl -o ${service}
-d adb -wv 1.1 -ss -uw/
classpath
fileset dir=${axis2.dir}/lib
include name=*.jar /
/fileset
/classpath
/java
a java class named
AddServicePortServiceMessageReceiverInOut.java
is generated that does a call of a method named getAddService0() as stated
below:
net.mycompany.crm.contract.services.addservice.AddService0 wrappedType){
return wrappedType.getAddService0().getEiMessageContext();
}
But the java class AddService0 contains only a method named
public net.mycompany.crm.contract.services.addservice.AddService
getAddService()
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-2328) Out of memory error in Callback receiver
[ https://issues.apache.org/jira/browse/AXIS2-2328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved AXIS2-2328. - Resolution: Fixed Out of memory error in Callback receiver Key: AXIS2-2328 URL: https://issues.apache.org/jira/browse/AXIS2-2328 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: client-api Affects Versions: nightly Environment: linux, sun jdk 1.5.0_10 Reporter: Michele Mazzucco Priority: Critical Attachments: AXIS2-2328.patch The CallbackReceiver stores the callback object into a hash map, but it never removes it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-2328) Out of memory error in Callback receiver
[ https://issues.apache.org/jira/browse/AXIS2-2328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12481415 ] Davanum Srinivas commented on AXIS2-2328: - Fixed in svn rev 518825 thanks, dims Out of memory error in Callback receiver Key: AXIS2-2328 URL: https://issues.apache.org/jira/browse/AXIS2-2328 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: client-api Affects Versions: nightly Environment: linux, sun jdk 1.5.0_10 Reporter: Michele Mazzucco Priority: Critical Attachments: AXIS2-2328.patch The CallbackReceiver stores the callback object into a hash map, but it never removes it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-2326) WSDL2Java generates too many if sentences in MessageReceiver's fromOM method with xmlbeans
[ https://issues.apache.org/jira/browse/AXIS2-2326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12481417 ] Davanum Srinivas commented on AXIS2-2326: - Jorge, can u please upload your wsdl/xsd? thx, dims WSDL2Java generates too many if sentences in MessageReceiver's fromOM method with xmlbeans -- Key: AXIS2-2326 URL: https://issues.apache.org/jira/browse/AXIS2-2326 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: codegen Affects Versions: 1.1.1 Environment: Windows XP SP2, Java 1.5, Eclipse 3.2.2, Eclipse Axis Plugin 1.2.1 Reporter: Jorge Fernández Priority: Trivial If I define in a wsdl that different methods are throwing the same exception, in the fromOM method of the MessageReceiver class generated, it appears a if statement for the exception as many times as methods are throwing it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-2325) Java2WSDL does not generate faults correctly
[ https://issues.apache.org/jira/browse/AXIS2-2325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas updated AXIS2-2325: Assignee: Amila Chinthaka Suriarachchi Java2WSDL does not generate faults correctly Key: AXIS2-2325 URL: https://issues.apache.org/jira/browse/AXIS2-2325 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: codegen Affects Versions: 1.1.1 Environment: Windows XP Java 1.5, Eclipse 3.2.2, Axis2 Eclipse Plugin 1.2.1 Reporter: Jorge Fernández Assigned To: Amila Chinthaka Suriarachchi Priority: Minor Attachments: API.java, API.wsdl, IncorrectPasswordFault.java, IncorrectUserFault.java The first problem is that in the WSDL generated my fault name is ignored and instead it's compound from the operation name and Fault. Also if I throw two exceptions from one operation, in the WSDL only one appears and with the name I said before. I attach the API from where I build the WSDL, the Faults classes and the WSDL generated. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-2322) If i generate skeleton classes, interfaces and stubs using the no matter what version of axis2 I use
[ https://issues.apache.org/jira/browse/AXIS2-2322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas updated AXIS2-2322: Assignee: Amila Chinthaka Suriarachchi If i generate skeleton classes, interfaces and stubs using the no matter what version of axis2 I use Key: AXIS2-2322 URL: https://issues.apache.org/jira/browse/AXIS2-2322 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: codegen, databinding, deployment, wsdl Affects Versions: 1.1.1, 1.1, 1.0 Environment: Windows 2000, sdk 1.5 Reporter: John McCosker Assigned To: Amila Chinthaka Suriarachchi Priority: Critical Attachments: build.xml, GENI_CommonTypes.xsd, GENI_FileSystemModifyService.wsdl, GENI_FileSystemModifyServiceTypes.xsd If i generate skeleton classes, interfaces and stubs using the wsdl2java ant task I can't then compile my classes, now I know its because all of the below mentioned methods (and others) fromOM(result.getResponseEnvelope().getBody().getFirstElement() and toEnvelope(getFactory(_operationClient.getOptions().getSoapVersionURI()) fromOM(faultElt,messageClass,null) are not included in org.apache.axis2.client.Stub as they have been left out for what-ever reason. All online documentation and mailing list indicated that, getElement() method was removed from the stub class sometime back, since the generated code no longer uses it. Please use the latest nightlies to generate your code... Ok, I have done that, does'nt work. Others suggest get the latest stable build, what version is stable, have tried, 1.0, 1.1, 1.1.1, extracted axis.war tried that, and tried axis2-1.1.1-SNAPSHOT, but all gave the same error. What version of axis will stop creating the these properties in the stubs so that I can then compile it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-2321) Mail transport - error handling in SimpleMailListener
[ https://issues.apache.org/jira/browse/AXIS2-2321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved AXIS2-2321. - Resolution: Fixed Mail transport - error handling in SimpleMailListener - Key: AXIS2-2321 URL: https://issues.apache.org/jira/browse/AXIS2-2321 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: transports Reporter: Hans G Knudsen Attachments: simplemaillistener_loop_fix.diff If an error occurs SimpleMailListener in the run inside the loop while doing createMessageContextToMailWorker : An exception is caught but the mail is left on server - causing an error on next POP If mails have arrived after failing mails - these mails are somehow still processed in loop - but also not deleted... Exception is still caught - causing ok mails/soapmessages to processed on every POP Testcase : send and soap-mail with a build in error eg : - illegal From header : 'From: mailto:[EMAIL PROTECTED]' - axis will not send this - but mail in spoolfile could be modified. We saw error with misconfigured WCF mail library. - other syntax errors in eg mailheaders will cause same problem. - The mail is left on server - Mails after the failing mails are somehow -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-2321) Mail transport - error handling in SimpleMailListener
[ https://issues.apache.org/jira/browse/AXIS2-2321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12481419 ] Davanum Srinivas commented on AXIS2-2321: - Fixed in svn revision 518826 Mail transport - error handling in SimpleMailListener - Key: AXIS2-2321 URL: https://issues.apache.org/jira/browse/AXIS2-2321 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: transports Reporter: Hans G Knudsen Attachments: simplemaillistener_loop_fix.diff If an error occurs SimpleMailListener in the run inside the loop while doing createMessageContextToMailWorker : An exception is caught but the mail is left on server - causing an error on next POP If mails have arrived after failing mails - these mails are somehow still processed in loop - but also not deleted... Exception is still caught - causing ok mails/soapmessages to processed on every POP Testcase : send and soap-mail with a build in error eg : - illegal From header : 'From: mailto:[EMAIL PROTECTED]' - axis will not send this - but mail in spoolfile could be modified. We saw error with misconfigured WCF mail library. - other syntax errors in eg mailheaders will cause same problem. - The mail is left on server - Mails after the failing mails are somehow -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-2320) Package name generation does not match Namespace-Package mapping
[ https://issues.apache.org/jira/browse/AXIS2-2320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas updated AXIS2-2320: Assignee: Amila Chinthaka Suriarachchi Package name generation does not match Namespace-Package mapping Key: AXIS2-2320 URL: https://issues.apache.org/jira/browse/AXIS2-2320 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: codegen Reporter: Severin Ecker Assigned To: Amila Chinthaka Suriarachchi If namespace 2 package mappings are defined and those packages have upper case letters the generated code won't compile due to an uppercase/lowercase naming issue. the fix i'm using is in class org.apache.axis2.wsdl.codegen.extension.PackageFinder change line configuration.setPackageName(packageName.toLowerCase()); to configuration.setPackageName(packageName); i know uppercase letters are not the convention but still the code generated should be correct and respect the namespace-package mappings defined. with this fix generation of types works fine, but generating server side sources (like skeletons, stubs...) does still not work since the import statements there also use some kind of toLowerString() which i haven't been able to track down yet. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-2319) Mail transport does not use 'transport.mail.replyToAddress' property
[ https://issues.apache.org/jira/browse/AXIS2-2319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas updated AXIS2-2319: Assignee: Saminda Wishwajith Abeyruwan Mail transport does not use 'transport.mail.replyToAddress' property Key: AXIS2-2319 URL: https://issues.apache.org/jira/browse/AXIS2-2319 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: transports Reporter: Hans G Knudsen Assigned To: Saminda Wishwajith Abeyruwan I noticed in MailTransportSender that the property transport.mail.replyToAddress is only read and assigned to mailToInfo.setFromAddress - but never used (by mailToInfo.getFromInfo nor in MailSender).. You can specify the 'From' by using the JavaMail - mail.smtp.from property. Is the 'replyToAddress' meant to be transfered to the MIME 'Reply-To' or the 'From' ?? If you give me a hint - I could supply a diff with a proposal for a fix /hans -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-2319) Mail transport does not use 'transport.mail.replyToAddress' property
[ https://issues.apache.org/jira/browse/AXIS2-2319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12481420 ] Davanum Srinivas commented on AXIS2-2319: - Saminda, Can you please help with this one? -- dims Mail transport does not use 'transport.mail.replyToAddress' property Key: AXIS2-2319 URL: https://issues.apache.org/jira/browse/AXIS2-2319 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: transports Reporter: Hans G Knudsen Assigned To: Saminda Wishwajith Abeyruwan I noticed in MailTransportSender that the property transport.mail.replyToAddress is only read and assigned to mailToInfo.setFromAddress - but never used (by mailToInfo.getFromInfo nor in MailSender).. You can specify the 'From' by using the JavaMail - mail.smtp.from property. Is the 'replyToAddress' meant to be transfered to the MIME 'Reply-To' or the 'From' ?? If you give me a hint - I could supply a diff with a proposal for a fix /hans -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-2318) transport.http.ListingAgent: i18n problem in case of a non-English default encoding
[ https://issues.apache.org/jira/browse/AXIS2-2318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved AXIS2-2318. - Resolution: Fixed transport.http.ListingAgent: i18n problem in case of a non-English default encoding --- Key: AXIS2-2318 URL: https://issues.apache.org/jira/browse/AXIS2-2318 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: transports Affects Versions: 1.1.1 Environment: Axis2 1.1.1, Oracle OC4J 10.1.3.2 Reporter: Dmitry Method processListService in org.apache.axis2.transport.http.ListingAgent has the following on lines 207 and 231: schema.write(out); This call converts String data to bytes using system's default encoding. A bit earlier in the code there is res.setContentType(text/xml); Thus in case of an XSD file request, user's browser will get ContentType: text/xml header without encoding specified, and will assume UTF-8. But if server's default encoding is something like Cp1251 the browser may complain about bad characters (as schema comments are sometimes written in national languages). A simple workaround is to replace schema.write(out); with schema.write(new OutputStreamWriter(out, UTF8)); WSDL2Java tool seems to have a similar kind of problem as it always outputs xsd files using system's default encoding rather than UTF-8 (even if source xsds are in UTF-8). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-2318) transport.http.ListingAgent: i18n problem in case of a non-English default encoding
[ https://issues.apache.org/jira/browse/AXIS2-2318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12481421 ] Davanum Srinivas commented on AXIS2-2318: - Fixed in svn revision 518831. Please open a new jira bug for the WSDL2Java tool. thanks, dims transport.http.ListingAgent: i18n problem in case of a non-English default encoding --- Key: AXIS2-2318 URL: https://issues.apache.org/jira/browse/AXIS2-2318 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: transports Affects Versions: 1.1.1 Environment: Axis2 1.1.1, Oracle OC4J 10.1.3.2 Reporter: Dmitry Method processListService in org.apache.axis2.transport.http.ListingAgent has the following on lines 207 and 231: schema.write(out); This call converts String data to bytes using system's default encoding. A bit earlier in the code there is res.setContentType(text/xml); Thus in case of an XSD file request, user's browser will get ContentType: text/xml header without encoding specified, and will assume UTF-8. But if server's default encoding is something like Cp1251 the browser may complain about bad characters (as schema comments are sometimes written in national languages). A simple workaround is to replace schema.write(out); with schema.write(new OutputStreamWriter(out, UTF8)); WSDL2Java tool seems to have a similar kind of problem as it always outputs xsd files using system's default encoding rather than UTF-8 (even if source xsds are in UTF-8). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Axis2][continuum] BUILD FAILURE
Online report : http://ws.zones.apache.org:1/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/1/buildId/1431 Build statistics: State: Failed Previous State: Failed Started at: Fri, 16 Mar 2007 01:50:39 + Finished at: Fri, 16 Mar 2007 01:54:43 + Total time: 4m 3s Build Trigger: Forced Exit code: 70 Building machine hostname: ws.zones.apache.org Operating system : SunOS(unknown) Java version : 1.5.0_09(Sun Microsystems Inc.) Changes dims Fix for AXIS2-2328 - Out of memory error in Callback receiver /webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/util/CallbackReceiver.java dims Fix for AXIS2-2321 - Mail transport - error handling in SimpleMailListener /webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/transport/mail/SimpleMailListener.java gdaniels * Clean up mustUnderstand check in AxisEngine. Now use SOAPHeader.getHeadersToProcess() to obtain a list of targeted headers, vastly simplifying the logic in there. Use SOAPVersion to send back the appropriate MU fault for the active SOAP version. * Remove deprecated references to old UUIDGenerator. /webservices/axis2/trunk/java/modules/addressing/src/org/apache/axis2/handlers/addressing/AddressingInHandler.java /webservices/axis2/trunk/java/modules/jaxws/src/org/apache/axis2/jaxws/message/attachments/JAXBAttachmentMarshaller.java /webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/engine/AxisEngine.java /webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/i18n/resource.properties /webservices/axis2/trunk/java/modules/kernel/test/org/apache/axis2/engine/MessageContextSaveATest.java /webservices/axis2/trunk/java/modules/kernel/test/org/apache/axis2/engine/MessageContextSaveBTest.java /webservices/axis2/trunk/java/modules/kernel/test/org/apache/axis2/engine/MessageContextSaveCTest.java /webservices/axis2/trunk/java/modules/kernel/test/org/apache/axis2/engine/MessageContextSelfManagedDataTest.java /webservices/axis2/trunk/java/modules/kernel/test/org/apache/axis2/engine/OperationContextSaveTest.java dims Fix for AXIS2-2318 - transport.http.ListingAgent: i18n problem in case of a non-English default encoding /webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/transport/http/ListingAgent.java Output: Snipped Output: soapmonitor + | Gathering project list Apache Axis 2.0 - Java2WSDL | Memory: 16M/40M + + | Gathering project list Apache Axis 2.0 - Kernel | Memory: 16M/40M + + | Gathering project list Apache Axis 2.0 - Data Binding | Memory: 16M/40M + + | Gathering project list Apache Axis 2.0 - Code Generation | Memory: 16M/40M + + | Gathering project list Apache Axis 2.0 - ADB Codegen | Memory: 16M/40M + + | Gathering project list Apache Axis 2.0 - Addressing | Memory: 16M/40M + + | Gathering project list Apache Axis 2.0 - Samples | Memory: 16M/40M + + | Gathering project list Apache Axis 2.0 - spring | Memory: 16M/40M + + | Gathering project list Apache Axis 2.0 - XMLBeans Data Binding | Memory: 16M/40M + + | Gathering project list Apache Axis 2.0 - Tools | Memory: 16M/40M + + | Gathering project list Apache Axis 2.0 - Integration | Memory: 16M/40M + + | Gathering project list Apache Axis 2.0 - JAXB-RI Data Binding | Memory: 16M/40M + + | Gathering project list Apache Axis 2.0 - SAAJ API | Memory: 16M/40M + + | Gathering project list Apache Axis 2.0 - JAXWS API | Memory: 16M/40M + + | Gathering
[jira] Resolved: (AXIS2-2315) Mail transport handling of MIME Message-Id / In-Reply-To
[ https://issues.apache.org/jira/browse/AXIS2-2315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved AXIS2-2315. - Resolution: Fixed Mail transport handling of MIME Message-Id / In-Reply-To Key: AXIS2-2315 URL: https://issues.apache.org/jira/browse/AXIS2-2315 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: transports Reporter: Hans G Knudsen Attachments: mail_transport_proposal.diff, MailBasedOutTransportInfo.java Mail transport does not save Message-Id from request to be set as In-Reply-To on reply -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-2315) Mail transport handling of MIME Message-Id / In-Reply-To
[ https://issues.apache.org/jira/browse/AXIS2-2315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12481423 ] Davanum Srinivas commented on AXIS2-2315: - Applied in svn revision 518834 thanks, dims Mail transport handling of MIME Message-Id / In-Reply-To Key: AXIS2-2315 URL: https://issues.apache.org/jira/browse/AXIS2-2315 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: transports Reporter: Hans G Knudsen Attachments: mail_transport_proposal.diff, MailBasedOutTransportInfo.java Mail transport does not save Message-Id from request to be set as In-Reply-To on reply -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Axis2][continuum] BUILD FAILURE
Online report : http://ws.zones.apache.org:1/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/1/buildId/1432 Build statistics: State: Failed Previous State: Failed Started at: Fri, 16 Mar 2007 01:55:34 + Finished at: Fri, 16 Mar 2007 01:56:48 + Total time: 1m 14s Build Trigger: Forced Exit code: 70 Building machine hostname: ws.zones.apache.org Operating system : SunOS(unknown) Java version : 1.5.0_09(Sun Microsystems Inc.) Changes No files changed Output: Snipped Output: Apache Axis 2.0 - JAXB-RI Data Binding | Memory: 26M/38M + + | Gathering project list Apache Axis 2.0 - SAAJ API | Memory: 26M/38M + + | Gathering project list Apache Axis 2.0 - JAXWS API | Memory: 26M/38M + + | Gathering project list Apache Axis 2.0 - SAAJ | Memory: 26M/38M + + | Gathering project list Apache Axis 2.0 - Metadata | Memory: 26M/38M + + | Gathering project list Apache Axis 2.0 - JAX-WS | Memory: 26M/38M + + | Gathering project list Apache Axis 2.0 - JiBX Data Binding | Memory: 26M/38M + + | Gathering project list Apache Axis 2.0 - JSON | Memory: 26M/38M + + | Gathering project list Apache Axis 2.0 - Metadata Exchange | Memory: 26M/38M + + | Gathering project list Apache Axis 2.0 - MTOM Policy | Memory: 26M/38M + + | Gathering project list Apache Axis 2.0 - ping | Memory: 26M/38M + + | Gathering project list Apache Axis 2.0 - soapmonitor | Memory: 26M/38M + multiproject:goal: Starting the reactor... Our processing order: Apache Axis 2.0 - Java2WSDL Apache Axis 2.0 - Kernel Apache Axis 2.0 - Data Binding Apache Axis 2.0 - Code Generation Apache Axis 2.0 - ADB Codegen Apache Axis 2.0 - Addressing Apache Axis 2.0 - Samples Apache Axis 2.0 - spring Apache Axis 2.0 - XMLBeans Data Binding Apache Axis 2.0 - Tools Apache Axis 2.0 - Integration Apache Axis 2.0 - JAXB-RI Data Binding Apache Axis 2.0 - SAAJ API Apache Axis 2.0 - JAXWS API Apache Axis 2.0 - SAAJ Apache Axis 2.0 - Metadata Apache Axis 2.0 - JAX-WS Apache Axis 2.0 - JiBX Data Binding Apache Axis 2.0 - JSON Apache Axis 2.0 - Metadata Exchange Apache Axis 2.0 - MTOM Policy Apache Axis 2.0 - ping Apache Axis 2.0 - soapmonitor + | Executing multiproject:install-callback Apache Axis 2.0 - Java2WSDL | Memory: 26M/38M + DEPRECATED: the default goal should be specified in the build section of project.xml instead of maven.xml DEPRECATED: the default goal should be specified in the build section of project.xml instead of maven.xml Trying to get missing/snapshot dependencies required by Apache Axis 2.0 - Java2WSDL: Attempting to download axiom-api-SNAPSHOT.jar. Skipping download as local copy is up to date! Attempting to download axiom-impl-SNAPSHOT.jar. Skipping download as local copy is up to date! Attempting to download XmlSchema-SNAPSHOT.jar. Skipping download as local copy is up to date! build:start: multiproject:install-callback: [echo] Running jar:install for Apache Axis 2.0 - Java2WSDL java:prepare-filesystem: [mkdir] Created dir: /export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/java2wsdl/target/classes Running post goal: java:prepare-filesystem java:compile: [echo] Compiling to /export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/java2wsdl/target/classes [javac] Compiling 23 source files to /export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/java2wsdl/target/classes java:jar-resources: Copying 2 files to /export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/java2wsdl/target/classes/META-INF test:test: [echo] No tests to run. jar:jar: [jar] Building jar:
[jira] Resolved: (AXIS2-2314) Creating multiple instances of Jar files, running out of disk space
[ https://issues.apache.org/jira/browse/AXIS2-2314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved AXIS2-2314. - Resolution: Fixed Creating multiple instances of Jar files, running out of disk space --- Key: AXIS2-2314 URL: https://issues.apache.org/jira/browse/AXIS2-2314 Project: Axis 2.0 (Axis2) Issue Type: Bug Environment: WinXP, Tomact5.0.28, Axis2.1.0, JDK1.4.2 Reporter: Ayondeep Datta Using Axis2.1.0 for creating client side stubs for connecting to a web service.Every time a web service call is made copy of axis2 jar files is created causing machine to run out of disk space. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-2314) Creating multiple instances of Jar files, running out of disk space
[ https://issues.apache.org/jira/browse/AXIS2-2314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12481425 ] Davanum Srinivas commented on AXIS2-2314: - Fixed in svn revision 518644 thanks, dims Creating multiple instances of Jar files, running out of disk space --- Key: AXIS2-2314 URL: https://issues.apache.org/jira/browse/AXIS2-2314 Project: Axis 2.0 (Axis2) Issue Type: Bug Environment: WinXP, Tomact5.0.28, Axis2.1.0, JDK1.4.2 Reporter: Ayondeep Datta Using Axis2.1.0 for creating client side stubs for connecting to a web service.Every time a web service call is made copy of axis2 jar files is created causing machine to run out of disk space. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-2308) Misc fixes: client-side validation, disallow wsdl generation for SOAP1.2, check SEI exceptions
[ https://issues.apache.org/jira/browse/AXIS2-2308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12481426 ] Davanum Srinivas commented on AXIS2-2308: - Roy, I don't see a patch in this issue... Misc fixes: client-side validation, disallow wsdl generation for SOAP1.2, check SEI exceptions -- Key: AXIS2-2308 URL: https://issues.apache.org/jira/browse/AXIS2-2308 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Reporter: Roy A. Wood Jr. This is a culmination of 3 fixes: 1. Enable limited client side validation 2. Disallow generation of wsdl for SOAP1.2 3. Check that exceptions on SEI have the same signature on impl -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-2307) Migrating from Axis1 example has errors and is not clear
[ https://issues.apache.org/jira/browse/AXIS2-2307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas updated AXIS2-2307: Assignee: Chatra Nakkawita Migrating from Axis1 example has errors and is not clear Key: AXIS2-2307 URL: https://issues.apache.org/jira/browse/AXIS2-2307 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: documentation Affects Versions: 1.1.1 Reporter: Sebb Assigned To: Chatra Nakkawita The sample Axis2 snippet does not seem to agree with the API. The EndpointReference class does not have a (String,String) constructor. The method ClientUtil.getEchoOMElement() does not exist. XMLStreamException is not thrown by the ServiceClient class. It would also help if the import statements were included. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-2303) java2wsdl-maven-plugin throws ClassNotFoundException on execution of java2wsdl goal
[
https://issues.apache.org/jira/browse/AXIS2-2303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davanum Srinivas resolved AXIS2-2303.
-
Resolution: Fixed
java2wsdl-maven-plugin throws ClassNotFoundException on execution of
java2wsdl goal
---
Key: AXIS2-2303
URL: https://issues.apache.org/jira/browse/AXIS2-2303
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: Tools
Environment: Maven 2.0.5, Windows, JDK 1.5
Reporter: Shane Isbell
Priority: Minor
Fix For: nightly
Attachments: java2wsdl-plugin-main-artifact.patch,
java2wsdl-plugin-main-artifact.patch, java2wsdl-plugin.patch,
patch-tests-main-artifact.zip, patch-tests.zip
When invoking the java2wsdl maven plugin on a project, I receive a
java.lang.ClassNotFoundException. This is due to the maven plugin not adding
the pom dependencies to the option map ( which is fed into the class loader).
build
plugins
plugin
groupIdorg.apache.axis2/groupId
artifactIdaxis2-java2wsdl-maven-plugin/artifactId
executions
execution
goals
goaljava2wsdl/goal
/goals
/execution
/executions
configuration
classNametest.TestInterface/className
outputFileNametarget/service.wsdl/outputFileName
/configuration
/plugin
/plugins
/build
Stack Trace:
[INFO] [axis2-java2wsdl:java2wsdl {execution: default}]
java.lang.Exception: java.lang.ClassNotFoundException: test.TestInterface
at
org.apache.ws.java2wsdl.Java2WSDLCodegenEngine.generate(Java2WSDLCode
genEngine.java:58)
at
org.apache.axis2.maven2.java2wsdl.Java2WSDLMojo.execute(Java2WSDLMojo
.java:164)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
nManager.java:420)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
ultLifecycleExecutor.java:539)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
fecycle(DefaultLifecycleExecutor.java:480)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
ltLifecycleExecutor.java:459)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
dleFailures(DefaultLifecycleExecutor.java:311)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
ts(DefaultLifecycleExecutor.java:278)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
fecycleExecutor.java:143)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:330)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:123)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: java.lang.ClassNotFoundException: test.TestInterface
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at
org.codehaus.classworlds.RealmClassLoader.loadClassDirect(RealmClassL
oader.java:195)
at
org.codehaus.classworlds.DefaultClassRealm.loadClass(DefaultClassReal
m.java:255)
at
org.codehaus.classworlds.DefaultClassRealm.loadClass(DefaultClassReal
m.java:274)
at
org.codehaus.classworlds.DefaultClassRealm.loadClass(DefaultClassReal
m.java:274)
at
org.codehaus.classworlds.RealmClassLoader.loadClass(RealmClassLoader.
java:214)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:242)
at
org.apache.ws.java2wsdl.Java2WSDLUtils.namespaceFromClassName(Java2WS
DLUtils.java:63)
at
org.apache.ws.java2wsdl.Java2WSDLUtils.schemaNamespaceFromClassName(J
ava2WSDLUtils.java:82)
at
[jira] Commented: (AXIS2-2303) java2wsdl-maven-plugin throws ClassNotFoundException on execution of java2wsdl goal
[
https://issues.apache.org/jira/browse/AXIS2-2303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12481429
]
Davanum Srinivas commented on AXIS2-2303:
-
Thanks Shane. Checked in the last patch in svn revision 518835
-- dims
java2wsdl-maven-plugin throws ClassNotFoundException on execution of
java2wsdl goal
---
Key: AXIS2-2303
URL: https://issues.apache.org/jira/browse/AXIS2-2303
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: Tools
Environment: Maven 2.0.5, Windows, JDK 1.5
Reporter: Shane Isbell
Priority: Minor
Fix For: nightly
Attachments: java2wsdl-plugin-main-artifact.patch,
java2wsdl-plugin-main-artifact.patch, java2wsdl-plugin.patch,
patch-tests-main-artifact.zip, patch-tests.zip
When invoking the java2wsdl maven plugin on a project, I receive a
java.lang.ClassNotFoundException. This is due to the maven plugin not adding
the pom dependencies to the option map ( which is fed into the class loader).
build
plugins
plugin
groupIdorg.apache.axis2/groupId
artifactIdaxis2-java2wsdl-maven-plugin/artifactId
executions
execution
goals
goaljava2wsdl/goal
/goals
/execution
/executions
configuration
classNametest.TestInterface/className
outputFileNametarget/service.wsdl/outputFileName
/configuration
/plugin
/plugins
/build
Stack Trace:
[INFO] [axis2-java2wsdl:java2wsdl {execution: default}]
java.lang.Exception: java.lang.ClassNotFoundException: test.TestInterface
at
org.apache.ws.java2wsdl.Java2WSDLCodegenEngine.generate(Java2WSDLCode
genEngine.java:58)
at
org.apache.axis2.maven2.java2wsdl.Java2WSDLMojo.execute(Java2WSDLMojo
.java:164)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
nManager.java:420)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
ultLifecycleExecutor.java:539)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
fecycle(DefaultLifecycleExecutor.java:480)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
ltLifecycleExecutor.java:459)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
dleFailures(DefaultLifecycleExecutor.java:311)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
ts(DefaultLifecycleExecutor.java:278)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
fecycleExecutor.java:143)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:330)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:123)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: java.lang.ClassNotFoundException: test.TestInterface
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at
org.codehaus.classworlds.RealmClassLoader.loadClassDirect(RealmClassL
oader.java:195)
at
org.codehaus.classworlds.DefaultClassRealm.loadClass(DefaultClassReal
m.java:255)
at
org.codehaus.classworlds.DefaultClassRealm.loadClass(DefaultClassReal
m.java:274)
at
org.codehaus.classworlds.DefaultClassRealm.loadClass(DefaultClassReal
m.java:274)
at
org.codehaus.classworlds.RealmClassLoader.loadClass(RealmClassLoader.
java:214)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:242)
at
org.apache.ws.java2wsdl.Java2WSDLUtils.namespaceFromClassName(Java2WS
DLUtils.java:63)
at
org.apache.ws.java2wsdl.Java2WSDLUtils.schemaNamespaceFromClassName(J
[jira] Resolved: (AXIS2-2297) Incorrect wsdl4j license
[ https://issues.apache.org/jira/browse/AXIS2-2297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved AXIS2-2297. - Resolution: Fixed Incorrect wsdl4j license Key: AXIS2-2297 URL: https://issues.apache.org/jira/browse/AXIS2-2297 Project: Axis 2.0 (Axis2) Issue Type: Bug Affects Versions: 1.1.1 Reporter: Jukka Zitting Priority: Minor axis2-1.1.1/lib/wsdl4j-LICENSE.txt claims that the wsdl4j license is ASLv2, when the license actually is CPL. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-2297) Incorrect wsdl4j license
[ https://issues.apache.org/jira/browse/AXIS2-2297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12481430 ] Davanum Srinivas commented on AXIS2-2297: - Checked in the correct license (picked from the wsdl4j zip dist) -- dims Incorrect wsdl4j license Key: AXIS2-2297 URL: https://issues.apache.org/jira/browse/AXIS2-2297 Project: Axis 2.0 (Axis2) Issue Type: Bug Affects Versions: 1.1.1 Reporter: Jukka Zitting Priority: Minor axis2-1.1.1/lib/wsdl4j-LICENSE.txt claims that the wsdl4j license is ASLv2, when the license actually is CPL. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-2294) AXIS2 generates invalid fault element for SOAP1.1 binding in the WSDL
[ https://issues.apache.org/jira/browse/AXIS2-2294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas updated AXIS2-2294: Assignee: Amila Chinthaka Suriarachchi AXIS2 generates invalid fault element for SOAP1.1 binding in the WSDL - Key: AXIS2-2294 URL: https://issues.apache.org/jira/browse/AXIS2-2294 Project: Axis 2.0 (Axis2) Issue Type: Bug Affects Versions: 1.1.1 Reporter: donald yang Assigned To: Amila Chinthaka Suriarachchi WSDL generator of AXIS2 has a bug. When I retrieve the WSDL for Version web service using the following method: http://localhost:8080/axis2/services/Version?wsdl the generated WSDL is invalid if a operation has fault message. The SOAP 12 binding element is correct, just SOAP1.1 binding element[1] is invalid. It should be [2]. [1] original SOAP1.1 binding element wsdl:binding name=VersionSOAP11Binding type=axis2:VersionPortType soap:binding transport=http://schemas.xmlsoap.org/soap/http style=document/ wsdl:operation name=getVersion soap:operation soapAction=urn:getVersion style=document/ wsdl:input soap:body use=literal/ /wsdl:input wsdl:output soap:body use=literal/ /wsdl:output wsdl:fault name=getVersionFault soap:body use=literal/ /wsdl:fault /wsdl:operation /wsdl:binding [2] correct one wsdl:fault name=getVersionFault soap12:fault use=literal name=getVersionFault/ /wsdl:fault -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-2295) generated wsdl:fault is not BP2032 conform
[ https://issues.apache.org/jira/browse/AXIS2-2295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas updated AXIS2-2295: Assignee: Amila Chinthaka Suriarachchi generated wsdl:fault is not BP2032 conform -- Key: AXIS2-2295 URL: https://issues.apache.org/jira/browse/AXIS2-2295 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: Tools Affects Versions: 1.1.1 Environment: Windows XP Reporter: Sven Wündrich Assigned To: Amila Chinthaka Suriarachchi If I start with an hand written wsdl, which is also BP conform, then the WSDL2Java generates an wsdl, which is not conform to the BP2032 (R2754). The problem is, that the WSDL2Java generates a wrong soap:fault element within the wsdl:fault element. wsdl:fault name=aException soap:fault name=aException use=literal/ /wsdl:fault will be generated to wsdl:fault name=aException soap:body use=literal / /wsdl:fault The WSDL2Java replaces the soap:fault element with the soap:body element and the ws-i BP test results in an error. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-2293) Update the resource.properties files
[ https://issues.apache.org/jira/browse/AXIS2-2293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12481431 ] Davanum Srinivas commented on AXIS2-2293: - Anne, Will you be taking care of this? thanks, dims Update the resource.properties files Key: AXIS2-2293 URL: https://issues.apache.org/jira/browse/AXIS2-2293 Project: Axis 2.0 (Axis2) Issue Type: Improvement Components: jaxws, kernel Environment: no special environment needs Reporter: Ming Cheung Assigned To: Ann Robinson Attachments: patch_d424436_0306.txt, patch_os_424436_1_0314.txt, patch_os_424436_1_0314a.txt, patch_os_424436_1_0314b.txt Updated and removed some of the i18n messages from both kernal and medata bundles. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-2292) wsdl2java produces a stub that cannot be compiled, when the wsdl file contains an element defined as a restriction on a duration type
[
https://issues.apache.org/jira/browse/AXIS2-2292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davanum Srinivas updated AXIS2-2292:
Assignee: Amila Chinthaka Suriarachchi
wsdl2java produces a stub that cannot be compiled, when the wsdl file
contains an element defined as a restriction on a duration type
-
Key: AXIS2-2292
URL: https://issues.apache.org/jira/browse/AXIS2-2292
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: adb, codegen
Environment: nightly build as of 3/2/07
Reporter: Carmen Checa
Assigned To: Amila Chinthaka Suriarachchi
This is the sample wsdl:
?xml version=1.0 encoding=UTF-8?
wsdl:definitions xmlns:wsdl = http://schemas.xmlsoap.org/wsdl/
xmlns:wsdlsoap = http://schemas.xmlsoap.org/wsdl/soap/ xmlns:xsd =
http://www.w3.org/2001/XMLSchema xmlns:ns =
http://schemas.xmlsoap.org/soap/encoding/ xmlns:myns = http://MyNamespace
targetNamespace = http://MyNamespace
wsdl:types
xsd:schema elementFormDefault = qualified
version = 1.0.0.3 targetNamespace = http://MyNamespace
xsd:element name = Operation1Content
xsd:simpleType
xsd:restriction
base = xsd:duration
xsd:minInclusive value = P0Y0M0DT0H0M0S /
/
xsd:restriction
/ xsd:simpleType
/ xsd:element
/ xsd:schema
/ wsdl:types
wsdl:message name = Operation1Msg
wsdl:part name = body element =
myns:Operation1Content /
/ wsdl:message
wsdl:portType name = MyPortType
wsdl:operation name = Operation1
wsdl:input message =
myns:Operation1Msg /
wsdl:output message =
myns:Operation1Msg /
/ wsdl:operation
/ wsdl:portType
wsdl:binding name = MyBinding type = myns:MyPortType
wsdlsoap:binding style = document transport =
http://schemas.xmlsoap.org/soap/http /
wsdl:operation name = Operation1
wsdlsoap:operation soapAction =
MyOperation /
wsdl:input
wsdlsoap:body use =
literal /
/ wsdl:input
wsdl:output
wsdlsoap:body use =
literal /
/ wsdl:output
/ wsdl:operation
/ wsdl:binding
wsdl:service name = MyService
wsdl:port name = MyPort binding =
myns:MyBinding
wsdlsoap:address location =
http://localhost:8080/MyService /
/ wsdl:port
/ wsdl:service
/ wsdl:definitions
This is the compilation error:
[javac]
C:\sdk\axis2build\generatedClient\src\mynamespace\MyServiceStub.java:686:
cannot find symbol
[javac] symbol : method
compare(org.apache.axis2.databinding.types.Duration,java.lang.String)
[javac] location: class org.apache.axis2.databinding.utils.ConverterUtil
[javac] if
(org.apache.axis2.databinding.utils.ConverterUtil.compare(param, ) = 0){
[javac]
^
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-2282) Session Management not supporting different session identifiers (e.g. ssnid)
[ https://issues.apache.org/jira/browse/AXIS2-2282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas updated AXIS2-2282: Assignee: Deepal Jayasinghe Session Management not supporting different session identifiers (e.g. ssnid) Key: AXIS2-2282 URL: https://issues.apache.org/jira/browse/AXIS2-2282 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: transports Affects Versions: 1.1.1 Reporter: Thomas Michelbach Assigned To: Deepal Jayasinghe I'm having a problem with session using a Service Client. I have two methods calling two different operations of a web service. The webservice is not implemented in axis2. I need to use a session so the web service can identify the axis2 client by each call. My class defines a single ServiceClient to make two different call. It has following option turned on: client.getOptions().setManageSession(true ); When I make the first call to the server, it runs the webservice and responds correctly. Following header is then passed: HTTP/1.0 200 OK Set-Cookie: ssnid=4383SO95jARAuR1Ad3Cc6clMdI1KEQo-62; path=/; Content-Type: text/xml;charset=utf-8 Connection: Keep-Alive Content-Length: 646 By the second call the client does not put the session data back to identify itself. So it passes only this information: SOAPAction: urn:anonOutInOp User-Agent: Axis2 Authorization: Basic [based64usernamepassword] Host: localhost:5554 Content-Length: 453 Content-Type: text/xml; charset=UTF-8 This was posted to the user mailing list and the conclusion was that axis2 does not support ssnid as session id. So a axis2 client can't communicate with another application server using session management. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-2277) JMS Message Id in request message context
[
https://issues.apache.org/jira/browse/AXIS2-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12481432
]
Davanum Srinivas commented on AXIS2-2277:
-
Rajith,
Could you please lend a hand with this one?
thanks,
dims
JMS Message Id in request message context
-
Key: AXIS2-2277
URL: https://issues.apache.org/jira/browse/AXIS2-2277
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: transports
Affects Versions: 1.1.1
Environment: Windows XP
Reporter: John Turner
Assigned To: Rajith Attapattu
The correlation id on a JMS message is not set correctly. It appears that
this is occuring because the mesage id is not set on creation of the request
message context (JMSMessageReceiver.createMessageContext). I added the
following line of code and it appears to have fixed the problem.
private MessageContext createMessageContext(Message message) {
InputStream in = JMSUtils.getInputStream(message);
try {
MessageContext msgContext = new MessageContext();
.
msgContext.getOptions().setMessageId(message.getJMSMessageID());
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-2273) The toString() methods in the metadata description package should not cause fatal errors
[ https://issues.apache.org/jira/browse/AXIS2-2273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved AXIS2-2273. - Resolution: Fixed The toString() methods in the metadata description package should not cause fatal errors Key: AXIS2-2273 URL: https://issues.apache.org/jira/browse/AXIS2-2273 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Affects Versions: 1.2 Reporter: Dustin Amrhein Priority: Minor Fix For: 1.2 Attachments: patch2.txt Wrap the toString() methods of the metadata description classes with a try catch block. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-2273) The toString() methods in the metadata description package should not cause fatal errors
[ https://issues.apache.org/jira/browse/AXIS2-2273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12481433 ] Davanum Srinivas commented on AXIS2-2273: - Fixed in svn revision 518841 thanks, dims The toString() methods in the metadata description package should not cause fatal errors Key: AXIS2-2273 URL: https://issues.apache.org/jira/browse/AXIS2-2273 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Affects Versions: 1.2 Reporter: Dustin Amrhein Priority: Minor Fix For: 1.2 Attachments: patch2.txt Wrap the toString() methods of the metadata description classes with a try catch block. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-2266) Permanent JMS Response Queue
[ https://issues.apache.org/jira/browse/AXIS2-2266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas updated AXIS2-2266: Assignee: Rajith Attapattu Permanent JMS Response Queue Key: AXIS2-2266 URL: https://issues.apache.org/jira/browse/AXIS2-2266 Project: Axis 2.0 (Axis2) Issue Type: Improvement Components: transports Affects Versions: 1.1.1 Environment: Windows XP Reporter: John Turner Assigned To: Rajith Attapattu When using the JMS transport a service client stub specifies a temporary JMS queue as the ReplyTo destination. A useful feature would be to be able to configure a permanent ReplyTo queue for the generated client stub and the service endpoint. In a request/response communication the association would be made through the message id or correlation id. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-2266) Permanent JMS Response Queue
[ https://issues.apache.org/jira/browse/AXIS2-2266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12481434 ] Davanum Srinivas commented on AXIS2-2266: - Can you please help with this? thanks, dims Permanent JMS Response Queue Key: AXIS2-2266 URL: https://issues.apache.org/jira/browse/AXIS2-2266 Project: Axis 2.0 (Axis2) Issue Type: Improvement Components: transports Affects Versions: 1.1.1 Environment: Windows XP Reporter: John Turner Assigned To: Rajith Attapattu When using the JMS transport a service client stub specifies a temporary JMS queue as the ReplyTo destination. A useful feature would be to be able to configure a permanent ReplyTo queue for the generated client stub and the service endpoint. In a request/response communication the association would be made through the message id or correlation id. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-2265) Could not set Expect 100-continue HTTP header
[ https://issues.apache.org/jira/browse/AXIS2-2265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12481435 ] Davanum Srinivas commented on AXIS2-2265: - Kate, What's the scenario you are dealing with? thansk, dims Could not set Expect 100-continue HTTP header Key: AXIS2-2265 URL: https://issues.apache.org/jira/browse/AXIS2-2265 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: kernel Affects Versions: 1.1.1 Reporter: Kate Wang I need to set Expect 100-continue http header, but I could not find a way to do it in axis2. I tried to add it as a custom header, but it would not work. After I examine the code more carefully, it seems to me that it is not possible to add it. In org.apache.axis2.transport.http.SOAPOverHTTPSender.java, at line 105, if HTTP version is 1.1, this header would be set. But in org.apche.commons.httpclient.methods.ExpectContinueMethod.java's addRequestHeaders() method, this header would be removed because HttpMethodParam.USE_EXPECT_CONTINUE is never set. I searched through axis2 source code and didn't find a way to set this parameter. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-2277) JMS Message Id in request message context
[
https://issues.apache.org/jira/browse/AXIS2-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davanum Srinivas updated AXIS2-2277:
Assignee: Rajith Attapattu
JMS Message Id in request message context
-
Key: AXIS2-2277
URL: https://issues.apache.org/jira/browse/AXIS2-2277
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: transports
Affects Versions: 1.1.1
Environment: Windows XP
Reporter: John Turner
Assigned To: Rajith Attapattu
The correlation id on a JMS message is not set correctly. It appears that
this is occuring because the mesage id is not set on creation of the request
message context (JMSMessageReceiver.createMessageContext). I added the
following line of code and it appears to have fixed the problem.
private MessageContext createMessageContext(Message message) {
InputStream in = JMSUtils.getInputStream(message);
try {
MessageContext msgContext = new MessageContext();
.
msgContext.getOptions().setMessageId(message.getJMSMessageID());
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-2242) Caused by: org.apache.axis2.schema.SchemaCompilationException: ... is not supported
[
https://issues.apache.org/jira/browse/AXIS2-2242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12481437
]
Davanum Srinivas commented on AXIS2-2242:
-
Sorry. There is no plan to support RPC/Encoded wsdl's in Axis2.
thanks,
dims
Caused by: org.apache.axis2.schema.SchemaCompilationException: ... is not
supported
---
Key: AXIS2-2242
URL: https://issues.apache.org/jira/browse/AXIS2-2242
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: codegen
Affects Versions: 1.1.1
Environment: windows xp, axis2-1.1.1, java 1.6.0
Reporter: Warren Goldman
JAVA VERSION
C:\tools\eclipse\workspace\MyProjectjava -version
java version 1.6.0
Java(TM) SE Runtime Environment (build 1.6.0-b105)
Java HotSpot(TM) Client VM (build 1.6.0-b105, mixed mode, sharing)
CLASSPATH
C:\tools\eclipse\workspace\MyProjectset
classpath=c:\tools\eclipse\workspace\ax
is2-1.1.1\lib\activation-1.1.jar;c:\tools\eclipse\workspace\axis2-1.1.1\lib\anno
gen-0.1.0.jar;c:\tools\eclipse\workspace\axis2-1.1.1\lib\axiom-api-1.2.2.jar;c:\
tools\eclipse\workspace\axis2-1.1.1\lib\axiom-dom-1.2.2.jar;c:\tools\eclipse\wor
kspace\axis2-1.1.1\lib\axiom-impl-1.2.2.jar;c:\tools\eclipse\workspace\axis2-1.1
.1\lib\axis2-adb-1.1.1.jar;c:\tools\eclipse\workspace\axis2-1.1.1\lib\axis2-adb-
codegen-1.1.1.jar;c:\tools\eclipse\workspace\axis2-1.1.1\lib\axis2-codegen-1.1.1
.jar;c:\tools\eclipse\workspace\axis2-1.1.1\lib\axis2-java2wsdl-1.1.1.jar;c:\too
ls\eclipse\workspace\axis2-1.1.1\lib\axis2-jaxbri-1.1.1.jar;c:\tools\eclipse\wor
kspace\axis2-1.1.1\lib\axis2-jibx-1.1.1.jar;c:\tools\eclipse\workspace\axis2-1.1
.1\lib\axis2-kernel-1.1.1.jar;c:\tools\eclipse\workspace\axis2-1.1.1\lib\axis2-s
aaj-1.1.1.jar;c:\tools\eclipse\workspace\axis2-1.1.1\lib\axis2-soapmonitor-1.1.1
.jar;c:\tools\eclipse\workspace\axis2-1.1.1\lib\axis2-tools-1.1.1.jar;c:\tools\e
clipse\workspace\axis2-1.1.1\lib\axis2-sprint-1.1.1.jar;c:\tools\eclipse\workspa
ce\axis2-1.1.1\lib\axis2-xmlbeans-1.1.1.jar;c:\tools\eclipse\workspace\axis2-1.1
.1\lib\jaxb-api-2.0.2.jar;c:\tools\eclipse\workspace\axis2-1.1.1\lib\jaxb-impl-2
.0.2.jar;c:\tools\eclipse\workspace\axis2-1.1.1\lib\jaxb-xjc-2.0.2.jar;c:\tools\
eclipse\workspace\axis2-1.1.1\lib\mail-1.4.jar;c:\tools\eclipse\workspace\axis2-
1.1.1\lib\wsdl4j-1.6.2.jar;c:\tools\eclipse\workspace\axis2-1.1.1\lib\commons-lo
gging-1.1.jar;c:\tools\eclipse\workspace\axis2-1.1.1\lib\neethi-2.0.jar;c:\tools
\eclipse\workspace\axis2-1.1.1\lib\XmlSchema-1.2.jar;
WSDL COMMAND
C:\tools\eclipse\workspace\MyProjectjava org.apache.axis2.wsdl.WSDL2Java
-uri M
cKessonUserService.wsdl -p com.mckesson.secureServices.wsdl.usr -s
RESULT (ERROR)
Exception in thread main
org.apache.axis2.wsdl.codegen.CodeGenerationException
: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException
at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGener
ationEngine.java:224)
at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32)
at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21)
Caused by: java.lang.RuntimeException:
java.lang.reflect.InvocationTargetExcepti
on
at
org.apache.axis2.wsdl.codegen.extension.SimpleDBExtension.engage(Simp
leDBExtension.java:52)
at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGener
ationEngine.java:177)
... 2 more
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.axis2.wsdl.codegen.extension.SimpleDBExtension.engage(Simp
leDBExtension.java:49)
... 3 more
Caused by: org.apache.axis2.schema.SchemaCompilationException:
{http://schemas.x
mlsoap.org/soap/encoding/}UserProfileResponse is not supported.
at
org.apache.axis2.schema.SchemaCompiler.findClassName(SchemaCompiler.j
ava:828)
at
org.apache.axis2.schema.SchemaCompiler.processElement(SchemaCompiler.
java:700)
at
org.apache.axis2.schema.SchemaCompiler.processElement(SchemaCompiler.
java:495)
at
org.apache.axis2.schema.SchemaCompiler.process(SchemaCompiler.java:15
44)
at
org.apache.axis2.schema.SchemaCompiler.processParticle(SchemaCompiler
.java:1506)
at
org.apache.axis2.schema.SchemaCompiler.processComplexType(SchemaCompi
ler.java:959)
at
org.apache.axis2.schema.SchemaCompiler.processAnonymousComplexSchemaT
ype(SchemaCompiler.java:891)
at
[jira] Updated: (AXIS2-2235) WSDL2Java ignore required attributes in xsd
[ https://issues.apache.org/jira/browse/AXIS2-2235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas updated AXIS2-2235: Assignee: Amila Chinthaka Suriarachchi WSDL2Java ignore required attributes in xsd --- Key: AXIS2-2235 URL: https://issues.apache.org/jira/browse/AXIS2-2235 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: wsdl Affects Versions: 1.1.1 Environment: Linux Fedora fc5, tomcat 6.0.7, java1.5.0_11, Axis2 1.1.1 Reporter: Federica Ciotti Assigned To: Amila Chinthaka Suriarachchi Attachments: BindingTemplate.java, publish_v2.wsdl, ServiceInfo.java, uddi_v2.xsd The java class generated for the element hasn't the requires field serviceKey and BusinessKey. This happen for oher xml element similar to this one. xsd:element name=serviceInfo type=uddi:serviceInfo/ xsd:complexType name=serviceInfo xsd:sequence xsd:element ref=uddi:name minOccurs=0 maxOccurs=unbounded/ /xsd:sequence xsd:attribute name=serviceKey type=uddi:serviceKey use=required/ xsd:attribute name=businessKey type=uddi:businessKey use=required/ /xsd:complexType In the following case the choice element and the two attributes are completly ignored in the generated java class: xsd:element name=bindingTemplate type=uddi:bindingTemplate/ xsd:complexType name=bindingTemplate xsd:sequence xsd:element ref=uddi:description minOccurs=0 maxOccurs=unbounded/ xsd:choice xsd:element ref=uddi:accessPoint/ xsd:element ref=uddi:hostingRedirector/ /xsd:choice xsd:element ref=uddi:tModelInstanceDetails/ /xsd:sequence xsd:attribute name=serviceKey type=uddi:serviceKey use=optional/ xsd:attribute name=bindingKey type=uddi:bindingKey use=required/ /xsd:complexType I tried to use the latest snapshot but, since my wsdl hasn't service element, I get a generation error. Attached are the two java classes of the examples showed and the wsdl. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-2224) quickstartjibx sample does not work
[ https://issues.apache.org/jira/browse/AXIS2-2224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas updated AXIS2-2224: Assignee: Dennis Sosnoski quickstartjibx sample does not work --- Key: AXIS2-2224 URL: https://issues.apache.org/jira/browse/AXIS2-2224 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: samples Affects Versions: nightly Environment: winxp, jdk1.5, tomcat 5.5.16 Reporter: Charitha Kankanamge Assigned To: Dennis Sosnoski Following exception thrown when running ant generate.service task in quickstartjibx sample. [wsdl2java] SystemId Unknown; Line #5; Column #44; Had IO Exception with stylesheet file: databindsupporter [wsdl2java] SystemId Unknown; Line #5; Column #44; Had IO Exception with stylesheet file: databindsupporter compile.src: [javac] Compiling 4 source files to C:\Axis\axis2-SNAPSHOT\samples\quickstartjibx\build\service\build\classes [javac] C:\Axis\axis2-SNAPSHOT\samples\quickstartjibx\build\service\src\samples\quickstart\service\jibx\StockQuoteServiceMessageReceiverInOnly.java:39: cannot find symbol [javac] symbol : method jibxReceiver0(org.apache.axiom.om.OMElement,samples.quickstart.service.jibx.StockQuoteServiceSkeletonInterface,nulltype) [javac] location: class samples.quickstart.service.jibx.StockQuoteServiceMessageReceiverInOnly [javac] jibxReceiver0(inMessage.getEnvelope().getBody().getFirstElement(), skel, null); [javac] ^ [javac] C:\Axis\axis2-SNAPSHOT\samples\quickstartjibx\build\service\src\samples\quickstart\service\jibx\StockQuoteServiceMessageReceiverInOut.java:42: canno t find symbol [javac] symbol : method jibxReceiver1(org.apache.axiom.om.OMElement,samples.quickstart.service.jibx.StockQuoteServiceSkeletonInterface,org.apache.axiom.soa p.SOAPFactory) [javac] location: class samples.quickstart.service.jibx.StockQuoteServiceMessageReceiverInOut [javac] envelope = jibxReceiver1(msgContext.getEnvelope().getBody().getFirstElement(), skel, getSOAPFactory(msgContext)); [javac]^ [javac] Note: Some input files use unchecked or unsafe operations. [javac] Note: Recompile with -Xlint:unchecked for details. [javac] 2 errors BUILD FAILED Steps to reproduce: --- 1. Navigate to Axis2_home/samples/quickstartjibx directory 2. Enter ant command -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-2224) quickstartjibx sample does not work
[ https://issues.apache.org/jira/browse/AXIS2-2224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12481440 ] Davanum Srinivas commented on AXIS2-2224: - Dennis, can you please look at this one? -- dims quickstartjibx sample does not work --- Key: AXIS2-2224 URL: https://issues.apache.org/jira/browse/AXIS2-2224 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: samples Affects Versions: nightly Environment: winxp, jdk1.5, tomcat 5.5.16 Reporter: Charitha Kankanamge Assigned To: Dennis Sosnoski Following exception thrown when running ant generate.service task in quickstartjibx sample. [wsdl2java] SystemId Unknown; Line #5; Column #44; Had IO Exception with stylesheet file: databindsupporter [wsdl2java] SystemId Unknown; Line #5; Column #44; Had IO Exception with stylesheet file: databindsupporter compile.src: [javac] Compiling 4 source files to C:\Axis\axis2-SNAPSHOT\samples\quickstartjibx\build\service\build\classes [javac] C:\Axis\axis2-SNAPSHOT\samples\quickstartjibx\build\service\src\samples\quickstart\service\jibx\StockQuoteServiceMessageReceiverInOnly.java:39: cannot find symbol [javac] symbol : method jibxReceiver0(org.apache.axiom.om.OMElement,samples.quickstart.service.jibx.StockQuoteServiceSkeletonInterface,nulltype) [javac] location: class samples.quickstart.service.jibx.StockQuoteServiceMessageReceiverInOnly [javac] jibxReceiver0(inMessage.getEnvelope().getBody().getFirstElement(), skel, null); [javac] ^ [javac] C:\Axis\axis2-SNAPSHOT\samples\quickstartjibx\build\service\src\samples\quickstart\service\jibx\StockQuoteServiceMessageReceiverInOut.java:42: canno t find symbol [javac] symbol : method jibxReceiver1(org.apache.axiom.om.OMElement,samples.quickstart.service.jibx.StockQuoteServiceSkeletonInterface,org.apache.axiom.soa p.SOAPFactory) [javac] location: class samples.quickstart.service.jibx.StockQuoteServiceMessageReceiverInOut [javac] envelope = jibxReceiver1(msgContext.getEnvelope().getBody().getFirstElement(), skel, getSOAPFactory(msgContext)); [javac]^ [javac] Note: Some input files use unchecked or unsafe operations. [javac] Note: Recompile with -Xlint:unchecked for details. [javac] 2 errors BUILD FAILED Steps to reproduce: --- 1. Navigate to Axis2_home/samples/quickstartjibx directory 2. Enter ant command -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-2223) soap over jms
[
https://issues.apache.org/jira/browse/AXIS2-2223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davanum Srinivas updated AXIS2-2223:
Assignee: Rajith Attapattu
soap over jms
-
Key: AXIS2-2223
URL: https://issues.apache.org/jira/browse/AXIS2-2223
Project: Axis 2.0 (Axis2)
Issue Type: Improvement
Affects Versions: 1.1.1
Environment: Linux Red Hat 3
Reporter: Fabio Ferri
Assigned To: Rajith Attapattu
Hi all,
I am new to Axis2 and to axis in general.
I need to create an Axis2 client starting from the WSDL provided by the
server.
I have gone through changing the axis2.xml file with the filowing
information:
transportReceiver name=jms
class=org.apache.axis2.transport.jms.JMSListener
parameter name=TibcoQueueConnectionFactory locked=false
parameter name=java.naming.factory.initial
locked=falsecom.tibco.tibjms.naming.TibjmsInitialContextFactory/parameter
parameter name=java.naming.provider.url
locked=falsetibjmsnaming://localhost:7222/parameter
parameter name=transport.jms.ConnectionFactoryJNDIName
locked=falseQueueConnectionFactory/parameter
/parameter
/transportReceiver
transportSender name=jms
class=org.apache.axis2.transport.jms.JMSSender/
and after that I have used the wsdl2java tool to generate the java stub. I
have then created a simple client that was using this stub:
public class testAxis2JMS {
/**
* @param args
*/
public static void main(String[] args) {
// TODO Auto-generated method stub
try{
String endpointURL = jms:/TCM.INTEGRAT.REQ.ADDRESS?
+
transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactory
+ java.naming.factory.initial=
+ com.tibco.tibjms.naming.TibjmsInitialContextFactory
+ java.naming.provider.url=tibjmsnaming://localhost:7222
+ java.naming.security.principal=user
+ java.naming.security.credentials=password;
IntfTestWSfromXSDProcessServiceStub stub =
new IntfTestWSfromXSDProcessServiceStub(endpointURL);
Indirizzo ind = new Indirizzo();
ind.setCitta(Rome);
ind.setNumero(2);
ind.setVia(blabla);
Output out = stub.TestWSfromXSDProcessOp(ind);
System.out.println(Code : + out.getCode());
System.out.println(Me : + out.getMsg());
} catch(Exception e){
e.printStackTrace();
System.out.println(\n\n\n);
}
}
}
Now when I send the request to the jms server the message is successfully
sent. The problem is that the web service that I am calling needs to have
some more information on the JMS header sent from my client to the jms server.
The jms message sent look like this:
$Header:
JMSMessageID=ID:EMS-SERVER.8A445C9FBB14:3
JMSTimestamp=Wed Feb 07 17:18:09 CET 2007
JMSDestination=Queue[TCM.INTEGRAT.REQ.ADDRESS]
JMSDeliveryMode=PERSISTENT
JMSCorrelationID=null
JMSType=null
JMSReplyTo=Queue[$TMP$.EMS-SERVER.8A445C9FBB14.3]
JMSPriority=4
$Properties:
SOAPAction=test/Axis2
$Body:
?xml version='1.0' encoding='utf-8'?soapenv:Envelope
xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;soapenv:Header
/soapenv:Bodyns1:Indirizzo
xmlns:ns1=http://www.tibco.com/schemas/eChannel/Schema.xsd;ns1:cittaRome/ns1:cittans1:viablabla/ns1:vians1:numero2/ns1:numero/ns1:Indirizzo/soapenv:Body/soapenv:Envelope
The problem is that it should look like this:
$Header:
JMSMessageID=ID:EMS-SERVER.8A445C9FBB184:8
JMSTimestamp=Thu Feb 08 10:09:16 CET 2007
JMSDestination=Queue[TCM.INTEGRAT.REQ.ADDRESS]
JMSDeliveryMode=PERSISTENT
JMSCorrelationID=null
JMSType=null
JMSReplyTo=Queue[$TMP$.EMS-SERVER.8A445C9FBB185.7]
JMSPriority=4
$Properties:
Content_Type=application/xml; charset=utf-8
Mime_Version=1.0
SoapAction=test/Axis2
$Body:
?xml version='1.0' encoding='utf-8'?soapenv:Envelope
xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;soapenv:Header
/soapenv:Bodyns1:Indirizzo
xmlns:ns1=http://www.tibco.com/schemas/eChannel/Schema.xsd;ns1:cittaRome/ns1:cittans1:viablabla/ns1:vians1:numero2/ns1:numero/ns1:Indirizzo/soapenv:Body/soapenv:Envelope
There are this two properties in the jms message header (Content_Type and
Mime_Version) that I need to add in order to make the Web Servixce server
work.
Apparently, API doesn't support custom JMS properties and I do not have an
easy solution.
regards,
Fabio
--
This message is
[jira] Commented: (AXIS2-2223) soap over jms
[
https://issues.apache.org/jira/browse/AXIS2-2223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12481441
]
Davanum Srinivas commented on AXIS2-2223:
-
Rajith,
Thoughts please...
-- dims
soap over jms
-
Key: AXIS2-2223
URL: https://issues.apache.org/jira/browse/AXIS2-2223
Project: Axis 2.0 (Axis2)
Issue Type: Improvement
Affects Versions: 1.1.1
Environment: Linux Red Hat 3
Reporter: Fabio Ferri
Assigned To: Rajith Attapattu
Hi all,
I am new to Axis2 and to axis in general.
I need to create an Axis2 client starting from the WSDL provided by the
server.
I have gone through changing the axis2.xml file with the filowing
information:
transportReceiver name=jms
class=org.apache.axis2.transport.jms.JMSListener
parameter name=TibcoQueueConnectionFactory locked=false
parameter name=java.naming.factory.initial
locked=falsecom.tibco.tibjms.naming.TibjmsInitialContextFactory/parameter
parameter name=java.naming.provider.url
locked=falsetibjmsnaming://localhost:7222/parameter
parameter name=transport.jms.ConnectionFactoryJNDIName
locked=falseQueueConnectionFactory/parameter
/parameter
/transportReceiver
transportSender name=jms
class=org.apache.axis2.transport.jms.JMSSender/
and after that I have used the wsdl2java tool to generate the java stub. I
have then created a simple client that was using this stub:
public class testAxis2JMS {
/**
* @param args
*/
public static void main(String[] args) {
// TODO Auto-generated method stub
try{
String endpointURL = jms:/TCM.INTEGRAT.REQ.ADDRESS?
+
transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactory
+ java.naming.factory.initial=
+ com.tibco.tibjms.naming.TibjmsInitialContextFactory
+ java.naming.provider.url=tibjmsnaming://localhost:7222
+ java.naming.security.principal=user
+ java.naming.security.credentials=password;
IntfTestWSfromXSDProcessServiceStub stub =
new IntfTestWSfromXSDProcessServiceStub(endpointURL);
Indirizzo ind = new Indirizzo();
ind.setCitta(Rome);
ind.setNumero(2);
ind.setVia(blabla);
Output out = stub.TestWSfromXSDProcessOp(ind);
System.out.println(Code : + out.getCode());
System.out.println(Me : + out.getMsg());
} catch(Exception e){
e.printStackTrace();
System.out.println(\n\n\n);
}
}
}
Now when I send the request to the jms server the message is successfully
sent. The problem is that the web service that I am calling needs to have
some more information on the JMS header sent from my client to the jms server.
The jms message sent look like this:
$Header:
JMSMessageID=ID:EMS-SERVER.8A445C9FBB14:3
JMSTimestamp=Wed Feb 07 17:18:09 CET 2007
JMSDestination=Queue[TCM.INTEGRAT.REQ.ADDRESS]
JMSDeliveryMode=PERSISTENT
JMSCorrelationID=null
JMSType=null
JMSReplyTo=Queue[$TMP$.EMS-SERVER.8A445C9FBB14.3]
JMSPriority=4
$Properties:
SOAPAction=test/Axis2
$Body:
?xml version='1.0' encoding='utf-8'?soapenv:Envelope
xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;soapenv:Header
/soapenv:Bodyns1:Indirizzo
xmlns:ns1=http://www.tibco.com/schemas/eChannel/Schema.xsd;ns1:cittaRome/ns1:cittans1:viablabla/ns1:vians1:numero2/ns1:numero/ns1:Indirizzo/soapenv:Body/soapenv:Envelope
The problem is that it should look like this:
$Header:
JMSMessageID=ID:EMS-SERVER.8A445C9FBB184:8
JMSTimestamp=Thu Feb 08 10:09:16 CET 2007
JMSDestination=Queue[TCM.INTEGRAT.REQ.ADDRESS]
JMSDeliveryMode=PERSISTENT
JMSCorrelationID=null
JMSType=null
JMSReplyTo=Queue[$TMP$.EMS-SERVER.8A445C9FBB185.7]
JMSPriority=4
$Properties:
Content_Type=application/xml; charset=utf-8
Mime_Version=1.0
SoapAction=test/Axis2
$Body:
?xml version='1.0' encoding='utf-8'?soapenv:Envelope
xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;soapenv:Header
/soapenv:Bodyns1:Indirizzo
xmlns:ns1=http://www.tibco.com/schemas/eChannel/Schema.xsd;ns1:cittaRome/ns1:cittans1:viablabla/ns1:vians1:numero2/ns1:numero/ns1:Indirizzo/soapenv:Body/soapenv:Envelope
There are this two properties in the jms message header (Content_Type and
Mime_Version) that I need to add in order to make the Web Servixce server
work.
Apparently, API doesn't support custom JMS properties and I do not have an
easy solution.
[jira] Updated: (AXIS2-2211) Support Axis2 services implemented with script langauges invoked by Apache BSF
[ https://issues.apache.org/jira/browse/AXIS2-2211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas updated AXIS2-2211: Assignee: Thilina Gunarathne Support Axis2 services implemented with script langauges invoked by Apache BSF -- Key: AXIS2-2211 URL: https://issues.apache.org/jira/browse/AXIS2-2211 Project: Axis 2.0 (Axis2) Issue Type: New Feature Affects Versions: nightly Reporter: ant elder Assigned To: Thilina Gunarathne Fix For: nightly Attachments: scriptingPatch.txt This patch adds support for Axis2 services implemented with script langauges. It uses Apache BSF so all script languages supported by BSF may be used. Its based on the same function used in Synapse and Tuscany. It supports two was of being used, either using the usual services.xml file with a script MessageReceiver, or as a script Module which monitors a script services directory and hot deploys / hot updates any script put in that directory. When using the script MessageReceiver there are two ways of defining the script in the services.xml, either with the script source defined in a seperate file or with the script source defined inline as a parameter value. See the javadoc comment in org.apache.axis2.scripting.ScriptReceiver for more details. When using the script module scripts currently need to have an associated WSDL file to define the service. The script and wsdl need to have the same name so the two can be linked together. For example, you have scriptServices/stockquote.wsdl and scriptServices/stockquote.js in the Axis2 repository directory then an Axis2 service would be deployed at /axis2/services/stockquote. The script language is determined from the file extension of the script source file. Currently a single script function is called for all service operations, the Axis2 MessageContext is passed into that function decorated with helper methods to access the payload XML in a way appropriate for the script language, for example E4X for JavaScript or ReXML for Ruby. I'd like to continue working on this, hopefully with input from you guys. There's a few things that could be reviewed/improved and it needs things like samples and doc. Be really good to get it working with the wso2 axiom e4x impl. I'd also like to extend it to make it easy to implement handlers in script languages. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-2211) Support Axis2 services implemented with script langauges invoked by Apache BSF
[ https://issues.apache.org/jira/browse/AXIS2-2211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12481442 ] Davanum Srinivas commented on AXIS2-2211: - Thilina, Can you please pick this up? thanks, dims Support Axis2 services implemented with script langauges invoked by Apache BSF -- Key: AXIS2-2211 URL: https://issues.apache.org/jira/browse/AXIS2-2211 Project: Axis 2.0 (Axis2) Issue Type: New Feature Affects Versions: nightly Reporter: ant elder Assigned To: Thilina Gunarathne Fix For: nightly Attachments: scriptingPatch.txt This patch adds support for Axis2 services implemented with script langauges. It uses Apache BSF so all script languages supported by BSF may be used. Its based on the same function used in Synapse and Tuscany. It supports two was of being used, either using the usual services.xml file with a script MessageReceiver, or as a script Module which monitors a script services directory and hot deploys / hot updates any script put in that directory. When using the script MessageReceiver there are two ways of defining the script in the services.xml, either with the script source defined in a seperate file or with the script source defined inline as a parameter value. See the javadoc comment in org.apache.axis2.scripting.ScriptReceiver for more details. When using the script module scripts currently need to have an associated WSDL file to define the service. The script and wsdl need to have the same name so the two can be linked together. For example, you have scriptServices/stockquote.wsdl and scriptServices/stockquote.js in the Axis2 repository directory then an Axis2 service would be deployed at /axis2/services/stockquote. The script language is determined from the file extension of the script source file. Currently a single script function is called for all service operations, the Axis2 MessageContext is passed into that function decorated with helper methods to access the payload XML in a way appropriate for the script language, for example E4X for JavaScript or ReXML for Ruby. I'd like to continue working on this, hopefully with input from you guys. There's a few things that could be reviewed/improved and it needs things like samples and doc. Be really good to get it working with the wso2 axiom e4x impl. I'd also like to extend it to make it easy to implement handlers in script languages. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-2202) NullPointerException invoking a stub method
[ https://issues.apache.org/jira/browse/AXIS2-2202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas updated AXIS2-2202: Assignee: Amila Chinthaka Suriarachchi NullPointerException invoking a stub method --- Key: AXIS2-2202 URL: https://issues.apache.org/jira/browse/AXIS2-2202 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: codegen Affects Versions: 1.1.1 Environment: Linux Fedora fc5, tomcat 6.0.7, java1.5.0_11, Axis2 1.1.1 Reporter: Federica Ciotti Assigned To: Amila Chinthaka Suriarachchi Service skeleton generated from wsdl with axis2 1.1.1 Client stub generate with axis2 1.1 (getting generation problems with 1.1.1 ) Trying to invoke a stub method form a client class I get: java.lang.NullPointerException at com.ctc.wstx.sw.BaseNsStreamWriter.doWriteAttr(BaseNsStreamWriter.java:467) at com.ctc.wstx.sw.BaseNsStreamWriter.writeAttribute(BaseNsStreamWriter.java:229) at org.apache.axiom.om.impl.MTOMXMLStreamWriter.writeAttribute(MTOMXMLStreamWriter.java:134) at org.apache.axiom.om.impl.util.OMSerializerUtil.serializeStartpart(OMSerializerUtil.java:387) at org.apache.axiom.om.impl.util.OMSerializerUtil.serializeStartpart(OMSerializerUtil.java:171) at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:803) at org.apache.axiom.om.impl.llom.OMSourcedElementImpl.internalSerialize(OMSourcedElementImpl.java:555) at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:792) at org.apache.axiom.om.impl.llom.OMSourcedElementImpl.internalSerialize(OMSourcedElementImpl.java:546) at org.apache.axiom.om.impl.llom.OMSourcedElementImpl.serialize(OMSourcedElementImpl.java:583) at uddi_org.publication_v2.PublishSoapServiceStub$Get_authToken20$1.serialize(PublishSoapServiceStub.java:29717) at org.apache.axiom.om.impl.llom.OMSourcedElementImpl.internalSerializeAndConsume(OMSourcedElementImpl.java:574) at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:819) at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerializeAndConsume(OMElementImpl.java:848) at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:819) at org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.internalSerialize(SOAPEnvelopeImpl.java:180) at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerializeAndConsume(OMElementImpl.java:848) at org.apache.axiom.om.impl.llom.OMNodeImpl.serializeAndConsume(OMNodeImpl.java:419) at org.apache.axis2.transport.http.SOAPMessageFormatter.writeTo(SOAPMessageFormatter.java:55) at org.apache.axis2.transport.http.AxisRequestEntity.writeRequest(AxisRequestEntity.java:85) 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:547) at org.apache.axis2.transport.http.SOAPOverHTTPSender.send(SOAPOverHTTPSender.java:119) at org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:349) at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:208) at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:519) at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:310) at org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:276) at uddi_org.publication_v2.PublishSoapServiceStub.get_authToken(PublishSoapServiceStub.java:1195) at uddi_client.PublishClient.getAuthToken(PublishClient.java:28) at uddi_client.PublishClient.main(PublishClient.java:11) Tomcat log exception is: Feb 16, 2007 11:45:54 AM org.apache.catalina.core.StandardWrapperValve invoke SEVERE: Servlet.service() for servlet AxisServlet threw exception java.lang.NullPointerException at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:330) at
[jira] Updated: (AXIS2-2185) Add Service Object Supplier Support
[ https://issues.apache.org/jira/browse/AXIS2-2185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas updated AXIS2-2185: Assignee: Davanum Srinivas Add Service Object Supplier Support - Key: AXIS2-2185 URL: https://issues.apache.org/jira/browse/AXIS2-2185 Project: Axis 2.0 (Axis2) Issue Type: New Feature Components: jaxws Environment: All Reporter: Mehdi Bahribayli Assigned To: Davanum Srinivas Attachments: SOS_patch.txt EndpointLifecycleManagerImpl does not use ServiceObjectSupplier service parameter and always creates new instance of service object by serviceImplClass.newInstance(). So we can not use JAXWS with other service object suppliers like Spring. Ali Ebrahimi Mehdi Bahribayli -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-2179) Unexpected subelement inheritance attribute
[ https://issues.apache.org/jira/browse/AXIS2-2179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas updated AXIS2-2179: Assignee: Amila Chinthaka Suriarachchi Unexpected subelement inheritance attribute --- Key: AXIS2-2179 URL: https://issues.apache.org/jira/browse/AXIS2-2179 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: databinding Affects Versions: 1.1.1 Environment: Linux 2.6.12 Jrockit 1.4.2 weblogic 8.2 Axis2 1.1.1 Reporter: Olivier DUGAST Assigned To: Amila Chinthaka Suriarachchi Attachments: ServiceTest.zip Hi all, I try to use Axis2 with my service. One of my methods return a tab of BeanB class which extend an other BeanA class. But the SOAP response return only the attribute of BeanB without the attribute of BeanA as you can see below : extract of wsdl - xs:element name=BeanB type=ax21:BeanB / xs:complexType name=BeanB xs:sequence xs:element name=attributeA nillable=true type=xs:string / xs:element name=attributeB nillable=true type=xs:string / /xs:sequence /xs:complexType ... xs:element name=getBeanBTabResponse xs:complexType xs:sequence xs:element maxOccurs=unbounded name=return nillable=true type=ns0:BeanB / /xs:sequence /xs:complexType /xs:element ... -- SOAP request ?xml version='1.0' encoding='utf-8'? soapenv:Envelope xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope; soapenv:Header / soapenv:Body getBeanBTab / /soapenv:Body /soapenv:Envelope - SOAP response of getBeanBTab webmethod without attribute A - ?xml version='1.0' encoding='utf-8'? soapenv:Envelope xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope; soapenv:Header / soapenv:Body ns:getBeanBTabResponse xmlns:ns=http://server.me.com/xsd; ns:return attributeB xmlns=http://bean.service.server.me.com/xsd;attrB BeanB/attributeB /ns:return /ns:getBeanBTabResponse /soapenv:Body /soapenv:Envelope -- When i try to invoke the method getBeanBTab as you can see above, no attributeA return , i catch this Exception : --- stack trace --- Exception in thread main java.lang.RuntimeException: java.lang.RuntimeException: Unexpected subelement attributeB at com.me.client.ServiceTestStub.fromOM(ServiceTestStub.java:3720) at com.me.client.ServiceTestStub.getBeanBTab(ServiceTestStub.java:365) at com.me.client.ServiceTestClient.getBeanBTab(ServiceTestClient.java:61) at com.me.client.ServiceTestClientMain.main(ServiceTestClientMain.java:15) Caused by: java.lang.RuntimeException: Unexpected subelement attributeB at com.me.client.ServiceTestStub$BeanB$Factory.parse(ServiceTestStub.java:1304) at com.me.client.ServiceTestStub$GetBeanBTabResponse$Factory.parse(ServiceTestStub.java:3592) at com.me.client.ServiceTestStub.fromOM(ServiceTestStub.java:3714) ... 3 more -- -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-2175) wsdl2java wsdl creation for interop. with .net
[ https://issues.apache.org/jira/browse/AXIS2-2175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas updated AXIS2-2175: Assignee: Amila Chinthaka Suriarachchi wsdl2java wsdl creation for interop. with .net --- Key: AXIS2-2175 URL: https://issues.apache.org/jira/browse/AXIS2-2175 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: wsdl Affects Versions: 1.1.1 Environment: Windows XP 5.1 on system architecture: x86 - Tomcat 5.5.9 - Jre 1.5.0 - Axis2 1.1.1 - .net 2005 Reporter: Asrael Assigned To: Amila Chinthaka Suriarachchi We are trying to operate with a .net client. The problem is in the wsdl recreated by the wsdl2java operation. Here i paste the original wsdl: ?xml version=1.0 encoding=UTF-8? wsdl:definitions xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/; xmlns:tm=http://microsoft.com/wsdl/mime/textMatching/; xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/; xmlns:mime=http://schemas.xmlsoap.org/wsdl/mime/; xmlns:tns=http://soapServlet.it/RInterface; xmlns:s=http://www.w3.org/2001/XMLSchema; xmlns:http=http://schemas.xmlsoap.org/wsdl/http/; targetNamespace=http://soapServlet.it/RInterface; xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/; wsdl:types s:schema elementFormDefault=qualified targetNamespace=http://soapServlet.it/RInterface; s:element name=getBuilding s:complexType s:sequence s:element minOccurs=0 maxOccurs=1 name=projectID type=s:string / s:element minOccurs=0 maxOccurs=1 name=userID type=s:string / /s:sequence /s:complexType /s:element s:element name=getBuildingResponse s:complexType s:sequence s:element minOccurs=0 maxOccurs=1 name=getBuildingResult type=tns:ArrayOfBuild / /s:sequence /s:complexType /s:element s:complexType name=ArrayOfBuild s:sequence s:element minOccurs=0 maxOccurs=unbounded name=Build nillable=true type=tns:Build / /s:sequence /s:complexType s:complexType name=Build s:all s:element minOccurs=0 maxOccurs=1 name=ID type=s:string / s:element minOccurs=0 maxOccurs=1 name=Val type=s:string / /s:all /s:complexType /s:schema /wsdl:types wsdl:message name=getBuildingSoapIn wsdl:part element=tns:getBuilding name=parameters / /wsdl:message wsdl:message name=getBuildingSoapOut wsdl:part element=tns:getBuildingResponse name=parameters / /wsdl:message wsdl:portType name=TerSoapEngine wsdl:operation name=getBuilding wsdl:input message=tns:getBuildingSoapIn / wsdl:output message=tns:getBuildingSoapOut / /wsdl:operation /wsdl:portType wsdl:binding name=TerSoapEngine type=tns:TerSoapEngine soap:binding transport=http://schemas.xmlsoap.org/soap/http; / wsdl:operation name=getBuilding soap:operation soapAction=http://soapServlet.it/RInterface/getBuilding; style=document / wsdl:input soap:body use=literal / /wsdl:input wsdl:output soap:body use=literal / /wsdl:output /wsdl:operation /wsdl:binding wsdl:service name=TerSoapEngine wsdl:port name=TerSoapEngine binding=tns:TerSoapEngine soap:address location=http://10.1.1.12/TerSoapEngine; / /wsdl:port /wsdl:service /wsdl:definitions and the wsdl create by wsdl2java wsdl:definitions xmlns:tns=http://soapServlet.it/RInterface; xmlns:soap12=http://schemas.xmlsoap.org/wsdl/soap12/; xmlns:http=http://schemas.xmlsoap.org/wsdl/http/; xmlns:mime=http://schemas.xmlsoap.org/wsdl/mime/; xmlns:tm=http://microsoft.com/wsdl/mime/textMatching/; xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/; xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/; xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/; xmlns:s=http://www.w3.org/2001/XMLSchema; targetNamespace=http://soapServlet.it/RInterface;wsdl:typess:schema attributeFormDefault=unqualified elementFormDefault=qualified targetNamespace=http://soapServlet.it/RInterface; s:element name=getBuilding s:complexType s:sequence s:element minOccurs=0 name=projectID type=s:string / s:element minOccurs=0 name=userID type=s:string / /s:sequence /s:complexType /s:element s:element name=getBuildingResponse s:complexType s:sequence s:element minOccurs=0 name=getBuildingResult type=tns:ArrayOfBuild / /s:sequence /s:complexType /s:element s:complexType name=ArrayOfBuild s:sequence
[jira] Updated: (AXIS2-2143) Broken link in chapter Installing and Testing Client Code (part of the online-documentation)
[ https://issues.apache.org/jira/browse/AXIS2-2143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas updated AXIS2-2143: Assignee: Chatra Nakkawita Broken link in chapter Installing and Testing Client Code (part of the online-documentation) -- Key: AXIS2-2143 URL: https://issues.apache.org/jira/browse/AXIS2-2143 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: documentation, samples, build,site Affects Versions: 1.1.1 Environment: Firefox 2.0.0.1 (German Edition) Reporter: Karl Philipp Assigned To: Chatra Nakkawita Priority: Minor Click the link http://ws.apache.org/axis2/1_1_1/userguide-installingtesting.html#installingtesting The chapter Apache Axis2 User's Guide - Installing and Testing Client Code will be displayed. Go to the section Content and click the link labeled Introducing Axis2: A Not Found error message will be displayed by the Firefox browser. A workaround for returning to the chapter Introducing Axis2 from the chapter Apache Axis2 User's Guide - Installing and Testing Client Code is a detour ;): First click the link of a sub chapter belonging to the chapter Introducing Axis2 or another chapter and then the link identifiying the chapter Introducing Axis2. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-2141) Identifier of a directory does not match the identifier of the corresponding directory provided with the Axis2 Standard Distribution
[ https://issues.apache.org/jira/browse/AXIS2-2141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas updated AXIS2-2141: Assignee: Chatra Nakkawita Identifier of a directory does not match the identifier of the corresponding directory provided with the Axis2 Standard Distribution Key: AXIS2-2141 URL: https://issues.apache.org/jira/browse/AXIS2-2141 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: documentation, samples, build,site Affects Versions: 1.1.1 Environment: N/A Reporter: Karl Philipp Assigned To: Chatra Nakkawita Priority: Trivial Pay attention to the online-document Apache Axis2 User's Guide, chapter Installing and Testing Client Code, that is http://ws.apache.org/axis2/1_1_1/userguide-installingtesting.html#installingtesting There you can read: ... to the directory J2EE_HOME/webapps/axis2-1.1.1/WEB-INF/services (Note ... But the Axis2 Standard Distribution I downloaded on February 8th, 2007 only contains a path of the form J2EE_HOME/webapps/axis2/WEB-INF/services that is the sub string -1.1.1 has been removed from the identifier of the corresponding directory provided wiht the Axis2 Standard Distribution. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-2140) Location of sample Axis2UserGuide.wsdl should be more clarified
[ https://issues.apache.org/jira/browse/AXIS2-2140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas updated AXIS2-2140: Assignee: Chatra Nakkawita Location of sample Axis2UserGuide.wsdl should be more clarified - Key: AXIS2-2140 URL: https://issues.apache.org/jira/browse/AXIS2-2140 Project: Axis 2.0 (Axis2) Issue Type: Improvement Components: documentation, samples, build,site Affects Versions: 1.1.1 Environment: N/A Reporter: Karl Philipp Assigned To: Chatra Nakkawita Priority: Minor The online-document Apache Axis2 User's Guide, chapter Creating Clients, section Axis Data Binding (ADB), that is http://ws.apache.org/axis2/1_1_1/userguide-creatingclients.html#adb explains to create a client using ADB with the sample Axis2UserGuide.wsdl. But because I was adviced to download and unpack the Apache Axis2 Standard Distribution two lines above I thought Axis2UserGuide.wsdl is part of the Standard Distribution. Negative! Later on I figured out that the Code Listing 5 http://ws.apache.org/axis2/1_1_1/userguide-codelisting5.html mentioned in a paragraph above represents the wsdl file Axis2UserGuide.wsdl. But only the contents of Code Listing 5 contains a hint clarifying this fact: wsdl:service name=Axis2UserGuideService I miss such a reference in the explanation for creating a client using ADB to improve the reading flow. For example, all occurences of the identifier Axis2UserGuide.wsdl could be underlaid with a link that directs to the Code Listing 5. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-2136) MTOM code example - incorrect variable declaration
[ https://issues.apache.org/jira/browse/AXIS2-2136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas updated AXIS2-2136: Assignee: Chatra Nakkawita MTOM code example - incorrect variable declaration -- Key: AXIS2-2136 URL: https://issues.apache.org/jira/browse/AXIS2-2136 Project: Axis 2.0 (Axis2) Issue Type: Improvement Components: documentation Environment: any Reporter: sumedha rubasinghe Assigned To: Chatra Nakkawita Priority: Minor Following variable declaration is incorrect redundant. MTOM with Axis2 |---Programming Model |--- DataHandler dataHandler = new DataHandler(dataSource); -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-2137) Common invocation using Axis2 client framework
[ https://issues.apache.org/jira/browse/AXIS2-2137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12481443 ] Davanum Srinivas commented on AXIS2-2137: - Should'nt we spend more effort on WSIF/Axis2 integration? thanks, dims Common invocation using Axis2 client framework -- Key: AXIS2-2137 URL: https://issues.apache.org/jira/browse/AXIS2-2137 Project: Axis 2.0 (Axis2) Issue Type: Improvement Components: client-api Affects Versions: nightly Reporter: Hasalaka Waravita Attachments: Axis2-Common-Invocation-Framwework.zip This is a patch for Axis2 to use existing client framwork to invoke Web Services using any tranport. It enables Axis2 ServiceClient to invoke non SOAP based WS as well. Please refer Readme.txt -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-2125) Asynchronous web service invocation does not return XML response on a SOAP fault
[ https://issues.apache.org/jira/browse/AXIS2-2125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas updated AXIS2-2125: Assignee: Nick Gallardo Asynchronous web service invocation does not return XML response on a SOAP fault Key: AXIS2-2125 URL: https://issues.apache.org/jira/browse/AXIS2-2125 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: client-api Affects Versions: 1.1 Environment: All Reporter: footh Assigned To: Nick Gallardo Priority: Minor When using the asynchronous sendReceiveNonBlocking call to invoke a web service, there is no way to retrieve the XML response if a SOAP Fault occurs. The XML response is always returned on the blocking invocation methods. I believe the same should hold for the asynchronous calls - there should always be a way to retreive the raw XML response. I sifted through the source code, in particular the NonBlockingInvocationWorker class (I'm looking at the one in OutInAxisOperation). The block of code that appears to be the problem looks something like this (in the run() method of NonBlockingInvocationWorker): if (body.hasFault()) ..call the callback's onError method else ..call the callback's onComplete method It seems the else clause should be eliminated and onComplete should always be called whether it is a SOAP Fault or not. This would result in both onError() and onComplete() being called in the case of a SOAP Fault, but I don't see that as being a big problem as the client can deal with it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-2121) WSDL2Java jibx binding issue
[ https://issues.apache.org/jira/browse/AXIS2-2121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas updated AXIS2-2121: Assignee: Dennis Sosnoski WSDL2Java jibx binding issue - Key: AXIS2-2121 URL: https://issues.apache.org/jira/browse/AXIS2-2121 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: wsdl Affects Versions: 1.1.1 Environment: windows xp Reporter: Ravi Varanasi Assigned To: Dennis Sosnoski Attachments: CM2NameZipSearch.wsdl, jibx-binding.xml Get the following error while running WSDL2Java . Any help is appreciated. Command : %AXIS2_HOME%\bin\wsdl2java -d jibx -Ebindingfile jibx-binding.xml -uri CM2NameZipSearch.wsdl Error: Exception in thread main org.apache.axis2.wsdl.codegen.CodeGenerationException : java.lang.IllegalArgumentException: local part cannot be null when creatinga QName at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:224) at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32) at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21) Caused by: java.lang.IllegalArgumentException: local part cannot be null when creating a QName at javax.xml.namespace.QName.init(QName.java:164) at javax.xml.namespace.QName.init(QName.java:113) at org.apache.axis2.jibx.CodeGenerationUtility.collectTopLevelComponents(CodeGenerationUtility.java:993) at org.apache.axis2.jibx.CodeGenerationUtility.engage(CodeGenerationUtility.java:301) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.axis2.wsdl.codegen.extension.JiBXExtension.engage(JiBXExtension.java:74) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:177) Binding: binding force-classes=true add-constructors=true xmlns:s0=http://tempuri.org/; mapping abstract=true class=org.tempuri.NameZipSearchRequest type-name=s0:NameZipSearchRequest value name=FirstName style=attribute field=firstName/ value name=LastName style=attribute field=lastName/ value name=MiddleInitial style=attribute field=middleInitial/ value name=Zip style=attribute field=zip/ value name=ZipFour style=attribute field=zipFour/ /mapping mapping type-name=s0:SubmitNameZipSearch class=org.tempuri.SubmitNameZipSearch structure field=nameZipSearchRequest name=objRequest map-as=s0:NameZipSearchRequest/ /mapping mapping abstract=true class=org.tempuri.LoanSummary type-name=s0:LoanSummary value name=FirstName style=attribute field=firstName/ value name=LastName style=attribute field=lastName/ value name=MiddleInitial style=attribute field=middleInitial/ value name=PropertyAddress1 style=attribute field=propertyAddress1/ value name=PropertyAddress2 style=attribute field=propertyAddress2/ value name=PropertyCity style=attribute field=propertyCity/ value name=PropertyZip style=attribute field=propertyZip/ value name=LoanType style=attribute field=loanType/ value name=LoanNumber style=attribute field=loanNumber/ value name=AccountStatus style=attribute field=accountStatus/ value name=CurrentBalanace style=attribute field=currentBalance/ /mapping mapping abstract=true class=org.tempuri.LoanSummaries type-name=s0:ArrayOfLoanSummary value name=LoanSummary style=attribute field=loanSummary/ /mapping mapping abstract=true class=org.tempuri.NameZipSearchResponse type-name=s0:NameZipSearchResponse structure field=loanSummaries name=LoanSummary map-as=s0:ArrayOfLoanSummary/ value field=refineSearch name=RefineSearch/ /mapping mapping type-name=s0:SubmitNameZipSearchResponse class=org.tempuri.NameZipSearchResponse structure field=SubmitNameZipSearchResult name=SubmitNameZipSearchResult map-as=s0:NameZipSearchResponse/ /mapping /binding WSDL:?xml version=1.0 encoding=utf-8? definitions xmlns:http=http://schemas.xmlsoap.org/wsdl/http/;
[jira] Commented: (AXIS2-2125) Asynchronous web service invocation does not return XML response on a SOAP fault
[ https://issues.apache.org/jira/browse/AXIS2-2125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12481444 ] Davanum Srinivas commented on AXIS2-2125: - Nick, Anything else needs to be done for this one? -- dims Asynchronous web service invocation does not return XML response on a SOAP fault Key: AXIS2-2125 URL: https://issues.apache.org/jira/browse/AXIS2-2125 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: client-api Affects Versions: 1.1 Environment: All Reporter: footh Assigned To: Nick Gallardo Priority: Minor When using the asynchronous sendReceiveNonBlocking call to invoke a web service, there is no way to retrieve the XML response if a SOAP Fault occurs. The XML response is always returned on the blocking invocation methods. I believe the same should hold for the asynchronous calls - there should always be a way to retreive the raw XML response. I sifted through the source code, in particular the NonBlockingInvocationWorker class (I'm looking at the one in OutInAxisOperation). The block of code that appears to be the problem looks something like this (in the run() method of NonBlockingInvocationWorker): if (body.hasFault()) ..call the callback's onError method else ..call the callback's onComplete method It seems the else clause should be eliminated and onComplete should always be called whether it is a SOAP Fault or not. This would result in both onError() and onComplete() being called in the case of a SOAP Fault, but I don't see that as being a big problem as the client can deal with it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-2121) WSDL2Java jibx binding issue
[ https://issues.apache.org/jira/browse/AXIS2-2121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12481445 ] Davanum Srinivas commented on AXIS2-2121: - Dennis, Please help. -- dims WSDL2Java jibx binding issue - Key: AXIS2-2121 URL: https://issues.apache.org/jira/browse/AXIS2-2121 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: wsdl Affects Versions: 1.1.1 Environment: windows xp Reporter: Ravi Varanasi Assigned To: Dennis Sosnoski Attachments: CM2NameZipSearch.wsdl, jibx-binding.xml Get the following error while running WSDL2Java . Any help is appreciated. Command : %AXIS2_HOME%\bin\wsdl2java -d jibx -Ebindingfile jibx-binding.xml -uri CM2NameZipSearch.wsdl Error: Exception in thread main org.apache.axis2.wsdl.codegen.CodeGenerationException : java.lang.IllegalArgumentException: local part cannot be null when creatinga QName at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:224) at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32) at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21) Caused by: java.lang.IllegalArgumentException: local part cannot be null when creating a QName at javax.xml.namespace.QName.init(QName.java:164) at javax.xml.namespace.QName.init(QName.java:113) at org.apache.axis2.jibx.CodeGenerationUtility.collectTopLevelComponents(CodeGenerationUtility.java:993) at org.apache.axis2.jibx.CodeGenerationUtility.engage(CodeGenerationUtility.java:301) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.axis2.wsdl.codegen.extension.JiBXExtension.engage(JiBXExtension.java:74) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:177) Binding: binding force-classes=true add-constructors=true xmlns:s0=http://tempuri.org/; mapping abstract=true class=org.tempuri.NameZipSearchRequest type-name=s0:NameZipSearchRequest value name=FirstName style=attribute field=firstName/ value name=LastName style=attribute field=lastName/ value name=MiddleInitial style=attribute field=middleInitial/ value name=Zip style=attribute field=zip/ value name=ZipFour style=attribute field=zipFour/ /mapping mapping type-name=s0:SubmitNameZipSearch class=org.tempuri.SubmitNameZipSearch structure field=nameZipSearchRequest name=objRequest map-as=s0:NameZipSearchRequest/ /mapping mapping abstract=true class=org.tempuri.LoanSummary type-name=s0:LoanSummary value name=FirstName style=attribute field=firstName/ value name=LastName style=attribute field=lastName/ value name=MiddleInitial style=attribute field=middleInitial/ value name=PropertyAddress1 style=attribute field=propertyAddress1/ value name=PropertyAddress2 style=attribute field=propertyAddress2/ value name=PropertyCity style=attribute field=propertyCity/ value name=PropertyZip style=attribute field=propertyZip/ value name=LoanType style=attribute field=loanType/ value name=LoanNumber style=attribute field=loanNumber/ value name=AccountStatus style=attribute field=accountStatus/ value name=CurrentBalanace style=attribute field=currentBalance/ /mapping mapping abstract=true class=org.tempuri.LoanSummaries type-name=s0:ArrayOfLoanSummary value name=LoanSummary style=attribute field=loanSummary/ /mapping mapping abstract=true class=org.tempuri.NameZipSearchResponse type-name=s0:NameZipSearchResponse structure field=loanSummaries name=LoanSummary map-as=s0:ArrayOfLoanSummary/ value field=refineSearch name=RefineSearch/ /mapping mapping type-name=s0:SubmitNameZipSearchResponse class=org.tempuri.NameZipSearchResponse structure field=SubmitNameZipSearchResult name=SubmitNameZipSearchResult map-as=s0:NameZipSearchResponse/ /mapping /binding WSDL:?xml version=1.0 encoding=utf-8? definitions xmlns:http=http://schemas.xmlsoap.org/wsdl/http/;
[jira] Updated: (AXIS2-2118) Wrong action name using WS-Addressing
[ https://issues.apache.org/jira/browse/AXIS2-2118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas updated AXIS2-2118: Assignee: Amila Chinthaka Suriarachchi Wrong action name using WS-Addressing - Key: AXIS2-2118 URL: https://issues.apache.org/jira/browse/AXIS2-2118 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: client-api Affects Versions: 1.1 Reporter: Brecht Yperman Assigned To: Amila Chinthaka Suriarachchi I'm trying to communicate to a .NET/WSE2.0 webservice. I use the ServiceClient with the following constructor: ServiceClient client = new ServiceClient(ConfigurationContext cc, Definition serviceDefinition, QName serviceName, String port); The problem we have now seems to be something with addressing. I already changed the namespace using the ServiceClient options: f_client.getOptions().setProperty(AddressingConstants.WS_ADDRESSING_VERS ION, Submission.WSA_NAMESPACE); The problem that remains is that the action doesn't seem to be correct. The wsdl mentions: wsdl:binding name=Data_x0020_ExtractSoap type=tns:Data_x0020_ExtractSoap soap:binding transport=http://schemas.xmlsoap.org/soap/http; style=document/ wsdl:operation name=GetUnsentProductData soap:operation soapAction=http://www.i-label.net/Partners/WebServices/DataFeed/2005/11 /GetUnsentProductData style=document/ wsdl:input soap:body use=literal/ /wsdl:input wsdl:output soap:body use=literal/ /wsdl:output /wsdl:operation /wsdl:binding So the action should be http://www.i-label.net/Partners/WebServices/DataFeed/2005/11/GetUnsentPr oductData However the sent SOAP contains the following part: wsa:Action xmlns:wsu=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssec urity-utility-1.0.xsd wsu:Id=Id-25682308http://www.i-label.net/Partners/WebServices/DataFee d/2005/11/Data_x0020_ExtractSoap/GetUnsentProductDataRequest/wsa:Action Somehow it seems to insert the name of the Binding in the action. Is there a way to change this behaviour? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-2118) Wrong action name using WS-Addressing
[ https://issues.apache.org/jira/browse/AXIS2-2118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12481447 ] Davanum Srinivas commented on AXIS2-2118: - Amila, Could this be a codegen issue? -- dims Wrong action name using WS-Addressing - Key: AXIS2-2118 URL: https://issues.apache.org/jira/browse/AXIS2-2118 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: client-api Affects Versions: 1.1 Reporter: Brecht Yperman Assigned To: Amila Chinthaka Suriarachchi I'm trying to communicate to a .NET/WSE2.0 webservice. I use the ServiceClient with the following constructor: ServiceClient client = new ServiceClient(ConfigurationContext cc, Definition serviceDefinition, QName serviceName, String port); The problem we have now seems to be something with addressing. I already changed the namespace using the ServiceClient options: f_client.getOptions().setProperty(AddressingConstants.WS_ADDRESSING_VERS ION, Submission.WSA_NAMESPACE); The problem that remains is that the action doesn't seem to be correct. The wsdl mentions: wsdl:binding name=Data_x0020_ExtractSoap type=tns:Data_x0020_ExtractSoap soap:binding transport=http://schemas.xmlsoap.org/soap/http; style=document/ wsdl:operation name=GetUnsentProductData soap:operation soapAction=http://www.i-label.net/Partners/WebServices/DataFeed/2005/11 /GetUnsentProductData style=document/ wsdl:input soap:body use=literal/ /wsdl:input wsdl:output soap:body use=literal/ /wsdl:output /wsdl:operation /wsdl:binding So the action should be http://www.i-label.net/Partners/WebServices/DataFeed/2005/11/GetUnsentPr oductData However the sent SOAP contains the following part: wsa:Action xmlns:wsu=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssec urity-utility-1.0.xsd wsu:Id=Id-25682308http://www.i-label.net/Partners/WebServices/DataFee d/2005/11/Data_x0020_ExtractSoap/GetUnsentProductDataRequest/wsa:Action Somehow it seems to insert the name of the Binding in the action. Is there a way to change this behaviour? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-2116) java2WSDL should generate schema elements for public fields
[
https://issues.apache.org/jira/browse/AXIS2-2116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12481448
]
Davanum Srinivas commented on AXIS2-2116:
-
Manoj,
Could i trouble u to please submit a fresh patch against latest svn? getting
errors applying the latest one.
-- dims
java2WSDL should generate schema elements for public fields
---
Key: AXIS2-2116
URL: https://issues.apache.org/jira/browse/AXIS2-2116
Project: Axis 2.0 (Axis2)
Issue Type: Improvement
Components: wsdl
Affects Versions: 1.2, 1.1.1, nightly
Environment: ALL
Reporter: Manoj Khangaonkar
Attachments: axis2-1749and2116.txt, axis2patch1749and2116-v2.txt,
patch2116.txt
When java2WSDL generates schema for method parameters, it generates elements
only for properties - those that have get/set metthods.
If I have a class that has fields without get/set methods like
public class Book {
public String title ;
public String author ;
}
The complex type in types section of the WSDL is
xs:complexType name=Book
xs:sequence /
/xs:complexType
It should be
xs:complexType name=Book
xs:sequence
xs:element name=title nillable=true type=xs:string /
xs:element name=author nillable=true type=xs:string /
/xs;sequence
/xs:complexType
java2wsdl is typically used to generate WSDL for legacy code and it is not
reasonable to expect users to go add get/set methods to legacy code
just because they need to generate WSDL
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-2110) How to get WS-A info from transport layer
[
https://issues.apache.org/jira/browse/AXIS2-2110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davanum Srinivas updated AXIS2-2110:
Assignee: David Illsley
How to get WS-A info from transport layer
-
Key: AXIS2-2110
URL: https://issues.apache.org/jira/browse/AXIS2-2110
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: Addressing
Affects Versions: 1.1.1
Environment: Linux Fedora5, tomcat 6.0.7 java1.5.0_0.9, Axis2 1.1.1
Reporter: John Mayer
Assigned To: David Illsley
I't trying to get the epr of the client invoking a web service.
Where does axis store this information?
My classes do something like this:
//client class
public static void main(String[] args){
try{
EndpointReference targetEPR = new
EndpointReference(http://localhost:8080/axis2/services/RPCCalcService/;);
EndpointReference myEPR = new
EndpointReference(http://localhost:8080/axis2/services/clientService/;);
Options options = new Options();
options.setTo(targetEPR);
options.setReplyTo(myEPR);
options.setFrom(myEPR);
options.setAction(getClientName);
RPCServiceClient sender = new RPCServiceClient();
sender.setOptions(options);
QName op = new QName(http://calc/xsd;,
getClientName);
Object[] params = new Object[] { };
Class[] returnTypes = new Class[] { String.class };
Object[] response = sender.invokeBlocking(op, params,
returnTypes);
String result = (String) response[0];
System.out.println(result);
}
//method in service class
public String getClientName() {
MessageContext msgCtx = MessageContext.getCurrentMessageContext();
String remoteAddress =
(String)msgCtx.getProperty(MessageContext.REMOTE_ADDR);
//TRANSPORT_URL
TransportHeaders transport =
(TransportHeaders)msgCtx.getProperty(MessageContext.TRANSPORT_HEADERS);
String trh = ;
trh = Message Context Transport Header Propertie Keys: +
transport.keySet() +\nvalues: +transport.values();
String to = msgCtx.getTo().toString();
String from = msgCtx.getFrom().toString();
String env = msgCtx.getEnvelope().toString();
return To: + to + From: + from + evn: + env+ thr: +trh;
}
I get:
To: Address: http://localhost:8080/axis2/services/RPCCalcService/
From: Address: 127.0.0.1
evn: ?xml version='1.0' encoding='utf-8'?soapenv:Envelope
xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;soapenv:Header
/soapenv:BodygetClientName xmlns=http://calc/xsd;
//soapenv:Body/soapenv:Envelope
thr: Message Context Transport Header Propertie Keys: [host=localhost:8080,
user-agent=Axis2, transfer-encoding=chunked, content-type=text/xml;
charset=UTF-8, soapaction=getClientName]
values: [localhost:8080, Axis2, chunked, text/xml; charset=UTF-8,
getClientName]
Why wsa info are not present in the soap envelope?
How can I get the client erp
EndpointReference myEPR = new
EndpointReference(http://localhost:8080/axis2/services/clientService/;);
in the server side?
Many Thank
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-2110) How to get WS-A info from transport layer
[
https://issues.apache.org/jira/browse/AXIS2-2110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12481449
]
Davanum Srinivas commented on AXIS2-2110:
-
David, Can you please take this one?
-- dims
How to get WS-A info from transport layer
-
Key: AXIS2-2110
URL: https://issues.apache.org/jira/browse/AXIS2-2110
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: Addressing
Affects Versions: 1.1.1
Environment: Linux Fedora5, tomcat 6.0.7 java1.5.0_0.9, Axis2 1.1.1
Reporter: John Mayer
Assigned To: David Illsley
I't trying to get the epr of the client invoking a web service.
Where does axis store this information?
My classes do something like this:
//client class
public static void main(String[] args){
try{
EndpointReference targetEPR = new
EndpointReference(http://localhost:8080/axis2/services/RPCCalcService/;);
EndpointReference myEPR = new
EndpointReference(http://localhost:8080/axis2/services/clientService/;);
Options options = new Options();
options.setTo(targetEPR);
options.setReplyTo(myEPR);
options.setFrom(myEPR);
options.setAction(getClientName);
RPCServiceClient sender = new RPCServiceClient();
sender.setOptions(options);
QName op = new QName(http://calc/xsd;,
getClientName);
Object[] params = new Object[] { };
Class[] returnTypes = new Class[] { String.class };
Object[] response = sender.invokeBlocking(op, params,
returnTypes);
String result = (String) response[0];
System.out.println(result);
}
//method in service class
public String getClientName() {
MessageContext msgCtx = MessageContext.getCurrentMessageContext();
String remoteAddress =
(String)msgCtx.getProperty(MessageContext.REMOTE_ADDR);
//TRANSPORT_URL
TransportHeaders transport =
(TransportHeaders)msgCtx.getProperty(MessageContext.TRANSPORT_HEADERS);
String trh = ;
trh = Message Context Transport Header Propertie Keys: +
transport.keySet() +\nvalues: +transport.values();
String to = msgCtx.getTo().toString();
String from = msgCtx.getFrom().toString();
String env = msgCtx.getEnvelope().toString();
return To: + to + From: + from + evn: + env+ thr: +trh;
}
I get:
To: Address: http://localhost:8080/axis2/services/RPCCalcService/
From: Address: 127.0.0.1
evn: ?xml version='1.0' encoding='utf-8'?soapenv:Envelope
xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;soapenv:Header
/soapenv:BodygetClientName xmlns=http://calc/xsd;
//soapenv:Body/soapenv:Envelope
thr: Message Context Transport Header Propertie Keys: [host=localhost:8080,
user-agent=Axis2, transfer-encoding=chunked, content-type=text/xml;
charset=UTF-8, soapaction=getClientName]
values: [localhost:8080, Axis2, chunked, text/xml; charset=UTF-8,
getClientName]
Why wsa info are not present in the soap envelope?
How can I get the client erp
EndpointReference myEPR = new
EndpointReference(http://localhost:8080/axis2/services/clientService/;);
in the server side?
Many Thank
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-2105) Annotations (JSR-181) for RPCMessageReceiver
[ https://issues.apache.org/jira/browse/AXIS2-2105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas updated AXIS2-2105: Assignee: Deepal Jayasinghe Annotations (JSR-181) for RPCMessageReceiver Key: AXIS2-2105 URL: https://issues.apache.org/jira/browse/AXIS2-2105 Project: Axis 2.0 (Axis2) Issue Type: Bug Reporter: Davanum Srinivas Assigned To: Deepal Jayasinghe Now that metadata module is separate from jaxws. Would it make sense to add some support for annotations in the basic pojo support itself? thanks, dims -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-2102) The logic in the engageModuleToOperation method on PhaseResolver is very obfuscated.
[ https://issues.apache.org/jira/browse/AXIS2-2102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12481450 ] Davanum Srinivas commented on AXIS2-2102: - Bill, Could you please help cleanup these? thanks, dims The logic in the engageModuleToOperation method on PhaseResolver is very obfuscated. Key: AXIS2-2102 URL: https://issues.apache.org/jira/browse/AXIS2-2102 Project: Axis 2.0 (Axis2) Issue Type: Task Components: kernel Reporter: Bill Nagy Assigned To: Bill Nagy The logic in the engageModuleToOperation method on PhaseResolver is very obfuscated (e.g. why is there a for loop for iterating over the set of flows when there is a switch block inside of it which explicitly enumerates each flow?) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-2098) There are numerous public methods on MessageContext that do not have comments.
[ https://issues.apache.org/jira/browse/AXIS2-2098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas updated AXIS2-2098: Assignee: Bill Nagy There are numerous public methods on MessageContext that do not have comments. -- Key: AXIS2-2098 URL: https://issues.apache.org/jira/browse/AXIS2-2098 Project: Axis 2.0 (Axis2) Issue Type: Task Components: kernel Reporter: Bill Nagy Assigned To: Bill Nagy -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-2098) There are numerous public methods on MessageContext that do not have comments.
[ https://issues.apache.org/jira/browse/AXIS2-2098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12481451 ] Davanum Srinivas commented on AXIS2-2098: - Bill, Could you please help cleanup these? thanks, dims There are numerous public methods on MessageContext that do not have comments. -- Key: AXIS2-2098 URL: https://issues.apache.org/jira/browse/AXIS2-2098 Project: Axis 2.0 (Axis2) Issue Type: Task Components: kernel Reporter: Bill Nagy Assigned To: Bill Nagy -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-2094) The class level comment on ConfigurationContext is not very descriptive.
[ https://issues.apache.org/jira/browse/AXIS2-2094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas updated AXIS2-2094: Assignee: Bill Nagy The class level comment on ConfigurationContext is not very descriptive. Key: AXIS2-2094 URL: https://issues.apache.org/jira/browse/AXIS2-2094 Project: Axis 2.0 (Axis2) Issue Type: Task Components: kernel Reporter: Bill Nagy Assigned To: Bill Nagy -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-2094) The class level comment on ConfigurationContext is not very descriptive.
[ https://issues.apache.org/jira/browse/AXIS2-2094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12481452 ] Davanum Srinivas commented on AXIS2-2094: - Bill, Could you please help cleanup these? thanks, dims The class level comment on ConfigurationContext is not very descriptive. Key: AXIS2-2094 URL: https://issues.apache.org/jira/browse/AXIS2-2094 Project: Axis 2.0 (Axis2) Issue Type: Task Components: kernel Reporter: Bill Nagy Assigned To: Bill Nagy -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
