Re: [Axis2] Deployment packaging
Deepal, i already did. -- dims On 12/3/05, Deepal Jayasinghe <[EMAIL PROTECTED]> wrote: > Thank you very much for the patch, I will apply that. > > Thanks, > Deepal > > ~Future is Open~ > > - Original Message - > From: "Alex Artigues" <[EMAIL PROTECTED]> > To: > Sent: Saturday, December 03, 2005 12:12 AM > Subject: Re: [Axis2] Deployment packaging > > > >> A patch would be awesome!! we could possibly help with perf testing as > >> well if we see the patch. > > > > And here it is! > > > > This patch does not include any attempts at optimization. It addresses > > the > > following issues: > > > > 1) Resources cannot be loaded from jars inside of the service .aar > > getResourceAsStream() has been overridden to allow this. > > > > 2) ZipInputStreams were left open by getBytes() if the target was not > > found. > > An additional try/catch block has been added after the search loop to make > > sure this happens. > > > > 3) Minor change in findLibJars() to normalize the path for startsWith() > > and > > endsWith() checks. > > > > > > What's missing from this patch is optimization code to address the > > extended > > loading times of the DeploymentClassLoader. We still don't know how to > > best > > deal with this. > > > > We forgot to extend a big "Thank You" to everyone out there working on > > this > > project in the last post. Thanks! > > > > --Alex & Ralf > > [EMAIL PROTECTED] > > [EMAIL PROTECTED] > > > > > > ### > > Sidenote: Should we post this to JIRA also? > > > > > -- Davanum Srinivas : http://wso2.com/blogs/
Re: [Axis2]Support for the wsdl based dynamic invocation
Srinath, Could you please look at DynamicInvoker in Axis1 and add corresponding functionality in Axis2? I know tons of people who use/need that :) thanks, dims On 12/2/05, Srinath Perera <[EMAIL PROTECTED]> wrote: > Hi All; > > I checked in a WSDLMEPClientBuilder, which can accept a WSDL and > produce a configured MEPClient. > > It would be very useful for the dynamic invocation (e.g. running a work flow). > > We might need to discuss the interfaces in more detail, But I just go > ahead and add it as it is completely standalone from the other things. > > Thanks > Srinath > -- Davanum Srinivas : http://wso2.com/blogs/
RE: [jira] Resolved: (AXIS-2305) Axis Fault : java.net.SocketException Connection reset
Hi Dims,
Is this fix available, I am running the same issue???
Thanks,
Parikh, Pratik
-Original Message-
From: Davanum Srinivas (JIRA) [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 29, 2005 9:13 AM
To: axis-dev@ws.apache.org
Subject: [jira] Resolved: (AXIS-2305) Axis Fault :
java.net.SocketException Connection reset
[ http://issues.apache.org/jira/browse/AXIS-2305?page=all ]
Davanum Srinivas resolved AXIS-2305:
Resolution: Duplicate
duplicate.
> Axis Fault : java.net.SocketException Connection reset
> --
>
> Key: AXIS-2305
> URL: http://issues.apache.org/jira/browse/AXIS-2305
> Project: Apache Axis
> Type: Bug
> Versions: 1.3
> Environment: Tested on Solaris 8 and Win 2000 Prof
> Reporter: Heemanshu Jain
> Priority: Blocker
>
> Hi,
> I am using Apache Axis 1.3 and JDK 1.5 to consume web services
from a SOAP webserver.
> I have a loop which executes every 5 seconds and makes a call to
the web service.
> The code works fine for a few requests but I get this error after
some requests at regular intervals. Nearly 1 failure in 50 requests.
> I have another program written in plain java code. This program is
executing with no errors. This proves that there is no problem at the
server side. (This program has hardcoded SOAP request so cannot use this
plain java code for production).
> Is this a known bug. Is there any workaround for the same
> AxisFault
> faultCode:
> {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
> faultSubcode:
> faultString: java.net.SocketException: Connection reset
> faultActor:
> faultNode:
> faultDetail:
>
> {http://xml.apache.org/axis/}stackTrace:java.net.SocketException:
Connec tion reset
> at java.net.SocketInputStream.read(Unknown Source)
> at java.io.BufferedInputStream.fill(Unknown Source)
> at java.io.BufferedInputStream.read(Unknown Source)
> at
> org.apache.axis.transport.http.HTTPSender.readHeadersFromSocket(HTTPS
> ender.java:583)
> at
org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:143)
> at
> org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrateg
> y.java:32)
> at
org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
> at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
> at
org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
> at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
> at org.apache.axis.client.Call.invoke(Call.java:2767)
> at org.apache.axis.client.Call.invoke(Call.java:2443)
> at org.apache.axis.client.Call.invoke(Call.java:2366)
> at org.apache.axis.client.Call.invoke(Call.java:1812)
> at
> com.bt.www.mta._2005._09.MTASoapPortStub.requestCheck(MTASoapPortStub
> .java:298)
> at
com.bt.www.mta.types._2005._09.Main4test.main(Main4test.java:92)
> {http://xml.apache.org/axis/}hostname:DSCP07364
> java.net.SocketException: Connection reset
> at org.apache.axis.AxisFault.makeFault(AxisFault.java:101)
> at
org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:154)
> at
> org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrateg
> y.java:32)
> at
org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
> at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
> at
org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
> at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
> at org.apache.axis.client.Call.invoke(Call.java:2767)
> at org.apache.axis.client.Call.invoke(Call.java:2443)
> at org.apache.axis.client.Call.invoke(Call.java:2366)
> at org.apache.axis.client.Call.invoke(Call.java:1812)
> at
> com.bt.www.mta._2005._09.MTASoapPortStub.requestCheck(MTASoapPortStub
> .java:298)
> at
> com.bt.www.mta.types._2005._09.Main4test.main(Main4test.java:92)
> Caused by: java.net.SocketException: Connection reset
> at java.net.SocketInputStream.read(Unknown Source)
> at java.io.BufferedInputStream.fill(Unknown Source)
> at java.io.BufferedInputStream.read(Unknown Source)
> at
> org.apache.axis.transport.http.HTTPSender.readHeadersFromSocket(HTTPS
> ender.java:583)
> at
org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:143)
> ... 11 more
> Please help.
> I need to have this running asap.
> Thanks in advance.
> Heemanshu
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
CONFIDENTIALITY NOTICE
This message and any included attachments
are from C
TCP transport interop with WCF: WSDL?
Hi everybody, I just joined this list to help you testing interop with WCF/Indigo when it comes to the TCP transport. In order to be able to test the interaction in a senseful way we need WSDL generation from Axis2. AFAIK, this is not yet available in 0.93. Is there any way to get at least some experimnetal version of this? Thanks - let's rock on :) Cheers, --- Christian Weyer WSCF - Web Services Contract-First, for real! http://www.thinktecture.com/WSCF/ jWSCF - Web Services Interface Design for Java and the Eclipse IDE http://blogs.thinktecture.com/cweyer/archive/2005/08/06/414103.aspx
XML realted projects for Grad School?
Hello, What would be a good source (website or books or journals) for xml & webservices related projects which could be done for Grad school? Looking for ideas or a list of projects from which I could pick one as a Master's project ? Thanks in advance!!
Re: svn commit: r348141 - /webservices/axis2/trunk/java/modules/saaj/src/org/apache/axis2/saaj/NodeImpl.java
Hmm...Please don't do this. If the NodeImpl class gets loaded the
ENTIRE JVM will start using our Document Builder Factory.
thanks,
-- dims
On 12/3/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Author: ruchithf
> Date: Tue Nov 22 02:17:13 2005
> New Revision: 348141
>
> URL: http://svn.apache.org/viewcvs?rev=348141&view=rev
> Log:
> Makeing the saaj imple use the OM-DOM Dom impl
>
>
> Modified:
>
> webservices/axis2/trunk/java/modules/saaj/src/org/apache/axis2/saaj/NodeImpl.java
>
> Modified:
> webservices/axis2/trunk/java/modules/saaj/src/org/apache/axis2/saaj/NodeImpl.java
> URL:
> http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/modules/saaj/src/org/apache/axis2/saaj/NodeImpl.java?rev=348141&r1=348140&r2=348141&view=diff
> ==
> ---
> webservices/axis2/trunk/java/modules/saaj/src/org/apache/axis2/saaj/NodeImpl.java
> (original)
> +++
> webservices/axis2/trunk/java/modules/saaj/src/org/apache/axis2/saaj/NodeImpl.java
> Tue Nov 22 02:17:13 2005
> @@ -21,6 +21,7 @@
> import org.apache.axis2.om.OMNode;
> import org.apache.axis2.om.OMText;
> import org.apache.axis2.om.impl.OMNodeEx;
> +import org.apache.axis2.om.impl.dom.jaxp.DocumentBuilderFactoryImpl;
> import org.apache.axis2.util.Dom2OmUtils;
> import org.w3c.dom.DOMException;
> import org.w3c.dom.Document;
> @@ -36,7 +37,12 @@
> * Class NodeImpl
> */
> public class NodeImpl implements Node {
> -
> +
> + static {
> +
> System.setProperty("javax.xml.parsers.DocumentBuilderFactory",DocumentBuilderFactoryImpl.class.getName());
> + }
> +
> +
> /**
> * Field omNode
> */
>
>
>
--
Davanum Srinivas : http://wso2.com/blogs/
Re: TCP transport interop with WCF: WSDL?
Christian, if you drop a service.wsdl in META-INF, that will be served from "?wsdl" just like Axis1.X thanks, dims On 12/3/05, Christian Weyer <[EMAIL PROTECTED]> wrote: > Hi everybody, > > I just joined this list to help you testing interop with WCF/Indigo when it > comes to the TCP transport. > In order to be able to test the interaction in a senseful way we need WSDL > generation from Axis2. AFAIK, this is not yet available in 0.93. Is there > any way to get at least some experimnetal version of this? > > Thanks - let's rock on :) > > Cheers, > --- > Christian Weyer > > WSCF - Web Services Contract-First, for real! > http://www.thinktecture.com/WSCF/ > > jWSCF - Web Services Interface Design for Java and the Eclipse IDE > http://blogs.thinktecture.com/cweyer/archive/2005/08/06/414103.aspx > > > -- Davanum Srinivas : http://wso2.com/blogs/
Re: TCP transport interop with WCF: WSDL?
Team, Here's the background example from Axis1: http://blogs.msdn.com/smguest/articles/axistcp.aspx Christian, Looking forward to making it happen :) and working with you. thanks, dims On 12/3/05, Davanum Srinivas <[EMAIL PROTECTED]> wrote: > Christian, > > if you drop a service.wsdl in META-INF, that will be served from > "?wsdl" just like Axis1.X > > thanks, > dims > > On 12/3/05, Christian Weyer <[EMAIL PROTECTED]> wrote: > > Hi everybody, > > > > I just joined this list to help you testing interop with WCF/Indigo when it > > comes to the TCP transport. > > In order to be able to test the interaction in a senseful way we need WSDL > > generation from Axis2. AFAIK, this is not yet available in 0.93. Is there > > any way to get at least some experimnetal version of this? > > > > Thanks - let's rock on :) > > > > Cheers, > > --- > > Christian Weyer > > > > WSCF - Web Services Contract-First, for real! > > http://www.thinktecture.com/WSCF/ > > > > jWSCF - Web Services Interface Design for Java and the Eclipse IDE > > http://blogs.thinktecture.com/cweyer/archive/2005/08/06/414103.aspx > > > > > > > > > -- > Davanum Srinivas : http://wso2.com/blogs/ > -- Davanum Srinivas : http://wso2.com/blogs/
Re: Question concerning criteria of wsdl document for "wrapped" styl e
Dies, You might find my bog entry on the wrapped convention helpful: http://atmanes.blogspot.com/2005/03/wrapped-documentliteral-convention.html (Check the comments for a couple of corrections to the example WSDL.) Note: If your message definition also contains header parts, Axis 1.2 will not recognize it as "wrapped" style, even though it should. AnneOn 11/30/05, [EMAIL PROTECTED] < [EMAIL PROTECTED]> wrote: Dies, Thanks for the reply. I was looking in the wrong place for "docs" concerning this. I'm using Axis1.2. Actually I was checking the wsdd generated and "wrapped" is placed in the type. (I didn't type this in manually; WSDL2Java did): At any rate I'm temporarily removing the operations in my portType and binding sections to uncover the non-compliant operations, and have isolated 2 of my operations which are okay, and two which are not. BTW, a co-worker suggested I debug the wsdl this way(removing/commenting out the operations and re-adding them) for my scenario, and although simple, it greatly helped to narrow the areas down for me.. Since I'm personally always looking for debugging tips, this might be a good one, speaking generally...Obviously, it may not work for everyone... Once again; thanks!! Cheers! Peter -Original Message- From: Dies Koper [mailto:[EMAIL PROTECTED]] Sent: Tuesday, November 29, 2005 7:13 PM To: axis-dev@ws.apache.org Subject: Re: Question concerning criteria of wsdl document for "wrapped" styl e Hello Peter, Document style operations can use the regular mapping or the "wrapper" style. See section 6.4.1 of the JAX-RPC 1.1 specification (and the example in 6.4.3) for details. Even if you generate a WSDL with "wrapped" style operations, the WSDL file will still say "document". IIRC, the WSDD does say whether Axis identified an operation as being wrapped or not. Please check whether your WSDL follows the criteria listed in the spec. If you think it does post your WSDL, maybe someone can pinpoint the problem. Regards, Dies [EMAIL PROTECTED] wrote: > Hi, > > Based on the source I viewed, the criteria for considering a wsdl > file(s) to be "wrapped" is " > + * Special case of DOCLIT where there is only one parameter > + * and it has the same qname as the operation. In > + * such cases, there is no actual type with the name...the > + * elements are treated as parameters to the operation > " > > I'm trying to get wsdl2Java to generate "wrapped" and keep getting > "document". I'm wondering if there are any other criteria I should > look > for(correct) in my wsdl, > in order to produce this type. I'm coding the type="document" in the main > .wsdl file, and unfortunately the resulting .java files and .wsdd are not > converting to "wrapped". Or is there a place in the source where I can > determine this information without being completely abstracted;-) > > Thanks for your time! > Peter A >
Re: [Axis2]Support for the wsdl based dynamic invocation
Will do :) I get in to little trouble with it I think I should be creating Call and MessageSender Objects rather than InOutMEPClient and InOnlyMEPCleint as the latter accept message contexts and AxisOperations, as a result not very user fiendly . right? But if I choose the first I can not use the information avalible to me via the WSDL (like AxisOperation) as Call and MessageSender assume certain things (e.g. create a Dummy Operation by the name) What do you think and recommand? I am not sure which way to go Thanks Srinath On 12/3/05, Davanum Srinivas <[EMAIL PROTECTED]> wrote: > Srinath, > > Could you please look at DynamicInvoker in Axis1 and add corresponding > functionality in Axis2? I know tons of people who use/need that :) > > thanks, > dims > > On 12/2/05, Srinath Perera <[EMAIL PROTECTED]> wrote: > > Hi All; > > > > I checked in a WSDLMEPClientBuilder, which can accept a WSDL and > > produce a configured MEPClient. > > > > It would be very useful for the dynamic invocation (e.g. running a work > > flow). > > > > We might need to discuss the interfaces in more detail, But I just go > > ahead and add it as it is completely standalone from the other things. > > > > Thanks > > Srinath > > > > > -- > Davanum Srinivas : http://wso2.com/blogs/ >
[Axis2] Configuration hierarchy no longer extends the WSDLComponents !
Hi, I was just observing that we no longer extend our Configuration (or Axis* , AxisOperation, etc) from the relevant WSDL component. eg AxisOperation (use to) extends WSDLOperation. I thought that was a nice thing to do because our WOM builder has the flexibility of building objects out of factory. That is you can ask the WOM builder to build a AxisOperation object rather than a WSDLOperation by registering a (AxisDescWSDLComponentFactory). IMO it is a cleaner way to build the configuration objects rather than keeping the object inside and delegating ALL the methods which it does right now. Is there any good reason why we did this change? Chathura On 12/1/05, Deepal Jayasinghe <[EMAIL PROTECTED]> wrote: > > Hi all; > > There was a class called MessageDescription to hold Message level > information (like WS policy) , but there was no any usage of that class , So > I removed that class and Added a new class called AxisMessage to do the same > thing. > > In addition to that removed handler flow data from AxisOperation and moved > that down to AxisMessage. So now there is a place holder to store WS-policy > information at the message level as well. In the same time you can add > message level parameters as well , the way of doing is my adding > element in as below; > > > > locked="false">messageIN > > > > I am sorry for send the mail after I doing this , I really forgot to send > the mail Im really sorry for that. > > Thanks, > Deepal > > ~Future is Open~ > -- Chathura Herath http://www.bloglines.com/blog/chathurah
Re: svn commit: r348141 - /webservices/axis2/trunk/java/modules/saaj/src/org/apache/axis2/saaj/NodeImpl.java
Removed - r353805
Thanks,
ruchith
On 12/4/05, Davanum Srinivas <[EMAIL PROTECTED]> wrote:
> Hmm...Please don't do this. If the NodeImpl class gets loaded the
> ENTIRE JVM will start using our Document Builder Factory.
>
> thanks,
> -- dims
>
> On 12/3/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> > Author: ruchithf
> > Date: Tue Nov 22 02:17:13 2005
> > New Revision: 348141
> >
> > URL: http://svn.apache.org/viewcvs?rev=348141&view=rev
> > Log:
> > Makeing the saaj imple use the OM-DOM Dom impl
> >
> >
> > Modified:
> >
> > webservices/axis2/trunk/java/modules/saaj/src/org/apache/axis2/saaj/NodeImpl.java
> >
> > Modified:
> > webservices/axis2/trunk/java/modules/saaj/src/org/apache/axis2/saaj/NodeImpl.java
> > URL:
> > http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/modules/saaj/src/org/apache/axis2/saaj/NodeImpl.java?rev=348141&r1=348140&r2=348141&view=diff
> > ==
> > ---
> > webservices/axis2/trunk/java/modules/saaj/src/org/apache/axis2/saaj/NodeImpl.java
> > (original)
> > +++
> > webservices/axis2/trunk/java/modules/saaj/src/org/apache/axis2/saaj/NodeImpl.java
> > Tue Nov 22 02:17:13 2005
> > @@ -21,6 +21,7 @@
> > import org.apache.axis2.om.OMNode;
> > import org.apache.axis2.om.OMText;
> > import org.apache.axis2.om.impl.OMNodeEx;
> > +import org.apache.axis2.om.impl.dom.jaxp.DocumentBuilderFactoryImpl;
> > import org.apache.axis2.util.Dom2OmUtils;
> > import org.w3c.dom.DOMException;
> > import org.w3c.dom.Document;
> > @@ -36,7 +37,12 @@
> > * Class NodeImpl
> > */
> > public class NodeImpl implements Node {
> > -
> > +
> > + static {
> > +
> > System.setProperty("javax.xml.parsers.DocumentBuilderFactory",DocumentBuilderFactoryImpl.class.getName());
> > + }
> > +
> > +
> > /**
> > * Field omNode
> > */
> >
> >
> >
>
>
> --
> Davanum Srinivas : http://wso2.com/blogs/
>
--
Ruchith
Re: [Axis2]Support for the wsdl based dynamic invocation
Very good test for refactoring client package again? Your call, am still digesting all the changes. Of course we may have to tweak a wee bit again :) thanks, -- dims On 12/3/05, Srinath Perera <[EMAIL PROTECTED]> wrote: > Will do :) > > I get in to little trouble with it > > I think I should be creating Call and MessageSender Objects rather > than InOutMEPClient and InOnlyMEPCleint as the latter accept message > contexts and AxisOperations, as a result not very user fiendly . > right? > > But if I choose the first I can not use the information avalible to me > via the WSDL (like AxisOperation) as Call and MessageSender assume > certain things (e.g. create a Dummy Operation by the name) > > What do you think and recommand? I am not sure which way to go > Thanks > Srinath > > On 12/3/05, Davanum Srinivas <[EMAIL PROTECTED]> wrote: > > Srinath, > > > > Could you please look at DynamicInvoker in Axis1 and add corresponding > > functionality in Axis2? I know tons of people who use/need that :) > > > > thanks, > > dims > > > > On 12/2/05, Srinath Perera <[EMAIL PROTECTED]> wrote: > > > Hi All; > > > > > > I checked in a WSDLMEPClientBuilder, which can accept a WSDL and > > > produce a configured MEPClient. > > > > > > It would be very useful for the dynamic invocation (e.g. running a work > > > flow). > > > > > > We might need to discuss the interfaces in more detail, But I just go > > > ahead and add it as it is completely standalone from the other things. > > > > > > Thanks > > > Srinath > > > > > > > > > -- > > Davanum Srinivas : http://wso2.com/blogs/ > > > -- Davanum Srinivas : http://wso2.com/blogs/
Re: TCP transport interop with WCF: WSDL?
Interesting...digging a bit more. WSE used DIME for framing (differentiate between 2 subsequent soap messages) and Indigo seems to use standard TCP framing. See here: http://beuchelt.blogdns.net:8080/2005/09/21/Framing+In+Indigo.aspx thanks, dims On 12/3/05, Davanum Srinivas <[EMAIL PROTECTED]> wrote: > Team, > Here's the background example from Axis1: > http://blogs.msdn.com/smguest/articles/axistcp.aspx > > Christian, > Looking forward to making it happen :) and working with you. > > thanks, > dims > > On 12/3/05, Davanum Srinivas <[EMAIL PROTECTED]> wrote: > > Christian, > > > > if you drop a service.wsdl in META-INF, that will be served from > > "?wsdl" just like Axis1.X > > > > thanks, > > dims > > > > On 12/3/05, Christian Weyer <[EMAIL PROTECTED]> wrote: > > > Hi everybody, > > > > > > I just joined this list to help you testing interop with WCF/Indigo when > > > it > > > comes to the TCP transport. > > > In order to be able to test the interaction in a senseful way we need WSDL > > > generation from Axis2. AFAIK, this is not yet available in 0.93. Is there > > > any way to get at least some experimnetal version of this? > > > > > > Thanks - let's rock on :) > > > > > > Cheers, > > > --- > > > Christian Weyer > > > > > > WSCF - Web Services Contract-First, for real! > > > http://www.thinktecture.com/WSCF/ > > > > > > jWSCF - Web Services Interface Design for Java and the Eclipse IDE > > > http://blogs.thinktecture.com/cweyer/archive/2005/08/06/414103.aspx > > > > > > > > > > > > > > > -- > > Davanum Srinivas : http://wso2.com/blogs/ > > > > > -- > Davanum Srinivas : http://wso2.com/blogs/ > -- Davanum Srinivas : http://wso2.com/blogs/
[jira] Resolved: (AXIS2-307) Generated stubs do not consistent with Call
[ http://issues.apache.org/jira/browse/AXIS2-307?page=all ] Eran Chinthaka resolved AXIS2-307: -- Resolution: Fixed This is fixed with the introduction of Options to the MEPClients. > Generated stubs do not consistent with Call > --- > > Key: AXIS2-307 > URL: http://issues.apache.org/jira/browse/AXIS2-307 > Project: Apache Axis 2.0 (Axis2) > Type: Bug > Components: databinding > Reporter: Eran Chinthaka > Assignee: Ajith Harshana Ranabahu > Fix For: 0.93 > > It seems that we do always have inconsistency with the methods in the Call > API and the methods in the Stub. IMO, all the methods that are in Call should > be made available via stub. > Current stub seems doesnot contain methods like setTimeOut. So shall we fix > this ? > Plus, one solution for this recurring problem is to use properties to pass > parameters via the Call api, so that there is no need to add methods whenever > Call changes. I think its better to use the properties from here on. > But we need to fix the current problem. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (AXIS2-321) nulls are not handled properly
nulls are not handled properly -- Key: AXIS2-321 URL: http://issues.apache.org/jira/browse/AXIS2-321 Project: Apache Axis 2.0 (Axis2) Type: Bug Components: databinding Environment: All Reporter: Ajith Harshana Ranabahu Assigned to: Ajith Harshana Ranabahu This was found during the MS interop. Axis2 framework cannot handle null values (with nil="true" attribute) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
