Axis2 Architecture Guide has been corrected and updated to 0.94 version of
Axis2. Review & Apply
-
Key: AXIS2-357
URL: http://issues.apache.org/jira/browse/AXIS2-357
Project: Ap
[ http://issues.apache.org/jira/browse/AXIS2-357?page=all ]
Chatra Nakkawita updated AXIS2-357:
---
Attachment: Axis2ArchitectureGuide.patch
phases.png
> Axis2 Architecture Guide has been corrected and updated to 0.94 version of
> Axis2.
[ http://issues.apache.org/jira/browse/AXIS2-357?page=all ]
Chatra Nakkawita updated AXIS2-357:
---
Attachment: Axis2ArchitectureGuide.patch
phases.png
> Axis2 Architecture Guide has been corrected and updated to 0.94 version of
> Axis2.
DonInteresting ideas. I would like some more discussion of this. The original WSRM implementation worked by serialising the internal state of Axis2. I have to say I was not a fan of this model. I think that middleware like Axis2 should fundamentally be stateless for clustering and performance reaso
updated tcp-transport.html, svn.html, CodegenToolReference.html of Axis2 0.94
version. Review & Apply
-
Key: AXIS2-358
URL: http://issues.apache.org/jira/browse/AXIS2-358
Pro
[ http://issues.apache.org/jira/browse/AXIS2-358?page=all ]
Chatra Nakkawita updated AXIS2-358:
---
Attachment: tcp-transport.patch
svn.patch
CodegenToolReference.patch
> updated tcp-transport.html, svn.html, CodegenToolRef
[ http://issues.apache.org/jira/browse/AXIS2-358?page=all ]
Saminda Wishwajith Abeyruwan resolved AXIS2-358:
Fix Version: 0.94
Resolution: Fixed
Applied
> updated tcp-transport.html, svn.html, CodegenToolReference.html of Axis
Stack overflow when processing XSD with mutual recursion
Key: AXIS2-359
URL: http://issues.apache.org/jira/browse/AXIS2-359
Project: Apache Axis 2.0 (Axis2)
Type: Bug
Components: wsdl
Versions: 0.9, 0.9
Thank you. I use the latest code in SVN (Axis2-0.94) and build (maven)
Axis2-0.94-SNAPSHOT.
But now:
used proxy properties
proxy.setUserName("user");
proxy.setPassWord("pass");
proxy.setProxyName("msserver"); // why? i use directly connect to server.
proxy.setProxyPor
Hi All,
I have seen some intrest in clustering but I see that there is no ongoing discussion or any clear requirments on this topic.
What I would like to do is to start some discussion and gather some momentum around this so we can flush out the requirments/expectations of clustering for Axis2.
[
http://issues.apache.org/jira/browse/AXIS-1911?page=comments#action_12361853 ]
Remy Viennet commented on AXIS-1911:
Hi Marc,
Do you have any news on this error ? I have the same problem with Jonas 4.4.3 /
Axis 1.2.1.
Cheers,
Remy
> String extension
Thanks,
It does seem to be a problem with anyType and/or Vector as replacing
them seems to work. It still would have been nice to get the anyType
working as it still forced me to remove that piece of hierarchy. The
Item's id was a Comparable, so in one case was a string, and in another
ano
[
http://issues.apache.org/jira/browse/AXIS2-359?page=comments#action_12361864 ]
Davanum Srinivas commented on AXIS2-359:
Our import stuff is in a deep mess!!! for starters, running w2j against the
interop wsdl's fails miserably.
http://soapinterop
[
http://issues.apache.org/jira/browse/AXIS2-359?page=comments#action_12361868 ]
Sanjiva Weerawarana commented on AXIS2-359:
---
Um, is the fix to this just the stuff that was in the original issue report? If
so that hardly qualifies as "deep mess".
Actually I think getting the balance right from Axis1 is the right thing to do. I was just using Axis1 WSDL2Java and I don't think its by any means perfect. I would say that ADB and WSDL2Java is probably the one area of Axis2 that needs the most work, but I also think its an area where we can easil
No Exceptions for Faults
Key: AXIS2-360
URL: http://issues.apache.org/jira/browse/AXIS2-360
Project: Apache Axis 2.0 (Axis2)
Type: Bug
Reporter: Davanum Srinivas
As per Ajith, "Axis2 code generator does not generate exceptions for fault
[ http://issues.apache.org/jira/browse/AXIS2-276?page=all ]
Davanum Srinivas resolved AXIS2-276:
Resolution: Fixed
already fixed.
thanks,
dims
> When serializing OM, it gives a stream exception
> ---
Team,
Q: How many test cases are in Axis 1.X's tree that run w2j and run
junit test cases using the generated code?
A: 110
Q: How many tests are in Axis2's tree that run w2j?
A: 12
Q: Is there a test for testing imports (wsdl/xsd)?
A: No
Q: Were there problems reported before for imports?
A: Ye
I am using axis2's MTOM capabilities to upload a binary file. My service
receives the request and handles it just fine with the file correctly
deposited on the server. However, axis2 hangs on the way back out.
I have verified that it gets past the generated MessageReceiver.
Below I have inclu
Dong Liu wrote:
Hi, folks,
I agree with Ajith's opinion about this persistence module for axis2.
I think the persistence module should not be restrict to certain
databases or frameworks. According to Paul's question, I would select
the first choice, and maybe a little beyond that. My current wor
Rajith Attapattu wrote:
Hi All,
I have seen some intrest in clustering but I see that there is no
ongoing discussion or any clear requirments on this topic.
What I would like to do is to start some discussion and gather some
momentum around this so we can flush out the requirments/expectati
Deepal,
If i run w2j on the WSDL for AXIS2-243
(http://issues.apache.org/jira/secure/attachment/12321416/DLDataService.wsdl)
and run the server as per my prev instructions, i don't see the
operations *IF* i don't drop my wsdl. If i drop my wsdl in resources
all's well. So basically there is a prob
But now the message receiver is null..Argh!! i'll keep looking.
-- dims
On 1/5/06, Davanum Srinivas <[EMAIL PROTECTED]> wrote:
> Deepal,
>
> If i run w2j on the WSDL for AXIS2-243
> (http://issues.apache.org/jira/secure/attachment/12321416/DLDataService.wsdl)
> and run the server as per my prev i
Ajith, Deepal,
Managed to go a little bit further...Could u please help me with the
WSDL here? (DLDataService.wsdl in AXIS2-343). incoming request looks
like this:
http://schemas.xmlsoap.org/soap/envelope/";
xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing";>http://schemas.xmlsoap.org/
FYI, Stack trace is as follows, see attached client and server side code.
thanks,
dims
Caused by: java.lang.Exception: org.apache.axis2.AxisFault: null;
nested exception is:
java.lang.NullPointerException
at org.apache.axis2.AxisFault.makeFault(AxisFault.java:254)
at
com.
Hi, folks,
I found something strange about the mechanism how axis2 service
identifies the operation corresponding to a request message.
When I used the following code to invoke a service:
...
OMElement result = call.invokeBlocking("operationName", payload);
...
If the SOAP body is *not* somethin
Hi dms
I am sorry for my late reply , if you deploy service as archive file there
has to be a services.xml describing the service then only that would be a
valid service, second in current impl you need to list all the operation
that you need to publish in services.xml (if you have 4 ops in ws
Deepal,
Then we should fix the w2j to generate all the names of the individual
operations. if you see the comments in the generated services.xml it
says
thanks,
dims
On 1/5/06, Deepal Jayasinghe <[EMAIL PROTECTED]> wrote:
> Hi dms
>
> I am sorry for my late reply , if you deploy service as arc
Oops! forgot to mention, this
(http://marc.theaimsgroup.com/?l=axis-dev&m=113650099208432&w=2) takes
care of setting the message receivers when the wsdl is present.
thanks,
dims
On 1/5/06, Davanum Srinivas <[EMAIL PROTECTED]> wrote:
> Deepal,
>
> Then we should fix the w2j to generate all the nam
ok , if we all can agree on following then we can publish all the PUBLIC
methods in service impl class.
- services.xml is just to configure the service , if service impl class has
5 methods and user need to configure only few of them in that case he will
add operation tag only for those.
- i
+1 to make it consistent AND publish the logic as well :)
thanks,
dims
On 1/5/06, Deepal Jayasinghe <[EMAIL PROTECTED]> wrote:
> ok , if we all can agree on following then we can publish all the PUBLIC
> methods in service impl class.
>
> - services.xml is just to configure the service , if serv
Here's my logic:
- Every service has an AxisService description
For most services this will come from reading the WSDL and in that case
all the WSDL operations become AxisOperation's inside the AxisService.
If the service doesn't have a WSDL, then we manufacture one using
Java2WSDL (for Ja
+1. Let's implement it (or make sure it is implemented already!)
-- dims
On 1/5/06, Sanjiva Weerawarana <[EMAIL PROTECTED]> wrote:
> Here's my logic:
>
> - Every service has an AxisService description
> For most services this will come from reading the WSDL and in that
> case
> all the W
hmmm , for my feeling is we do not need to publish all the public methods in
super class as well , and second thing is how do we figure out the
inheritance level we should look at , so for this release lets publish only
the public methods in service impl class and none of public methods in its
On Fri, 2006-01-06 at 11:12 +0600, Deepal Jayasinghe wrote:
> hmmm , for my feeling is we do not need to publish all the public methods in
> super class as well , and second thing is how do we figure out the
> inheritance level we should look at , so for this release lets publish only
> the publ
Hi, Steve,
I would like to see what you have done and refer to them. What I am
doing now is about manageability of BPEL processes which is related to
normal web services, and the WS-Resources as well. I am so glad that
so many guys here are interested in the persistence of web services.
Thanks,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Rajith Attapattu wrote:
> Hi All,
>
> I have seen some intrest in clustering but I see that there is no ongoing
> discussion or any clear requirments on this topic.
>
> What I would like to do is to start some discussion and gather some momentum
> ar
Review & apply finalized versions of index.html, userguide.html &
ServiceArchiveToolReference.html docs
---
Key: AXIS2-361
URL: http://issues.apache.org/jira/browse/AXIS2-361
[ http://issues.apache.org/jira/browse/AXIS2-361?page=all ]
Chatra Nakkawita updated AXIS2-361:
---
Attachment: index.patch
ServiceArchiveToolReference.patch
userguide.patch
> Review & apply finalized versions of index.html
[ http://issues.apache.org/jira/browse/AXIS2-361?page=all ]
Eran Chinthaka resolved AXIS2-361:
--
Fix Version: 0.94
Resolution: Fixed
Done !!!
> Review & apply finalized versions of index.html, userguide.html &
> ServiceArchiveToolReference.ht
40 matches
Mail list logo