Re: Creating a async web sercice
Hi
By the way, do you know why it did not work with 1.4.1, it this a known
limitation?
cheers, Håkon
2009/9/17 Håkon Sagehaug hakon.sageh...@bccs.uib.no
Hi
I changed to axis2 1.5 also on the server and then all seems to work.
Thanks for the help
cheers, Håkon
2009/9/17 Håkon Sagehaug hakon.sageh...@bccs.uib.no
Hi
I also get this error message
SEVERE: The Callback for MessageID
urn:uuid:E75DBDF30A77DAB1011253193935432 was not found
org.apache.axis2.AxisFault: The Callback for MessageID
urn:uuid:E75DBDF30A77DAB1011253193935432 was not found
cheers, Håkon
2009/9/17 Håkon Sagehaug hakon.sageh...@bccs.uib.no
Hi
I used axis2 1.4.1 and changed to 1.5, but I still got time out. I
changed just on the client side, server is still using 1.4.1
2009/9/17 Amila Suriarachchi amilasuriarach...@gmail.com
What is the Axis2 version you use? try with Axis2 1.5.
hope you have set the parameter correctly.
On the server or client side?
The service.xml looks like this
service name=EchoService
messageReceivers
messageReceiver mep=http://www.w3.org/ns/wsdl/in-out;
class=no.uib.bccs.esysbio.echoservice.EchoServiceMessageReceiverInOut/
/messageReceivers
parameter
name=messageReceiver.invokeOnSeparateThreadtrue/parameter
parameter
name=ServiceClassno.uib.bccs.esysbio.echoservice.EchoServiceImpl/parameter
parameter name=useOriginalwsdltrue/parameter
parameter name=modifyUserWSDLPortAddresstrue/parameter
operation name=SayHi mep=http://www.w3.org/ns/wsdl/in-out;
namespace=http://www.bccs.uib.no/EchoService.wsdl;
actionMappinghttp://www.bccs.uib.no/EchoService.wsdl/SayHi
/actionMapping
outputActionMapping
http://www.bccs.uib.no/EchoService.wsdl/EchoServicePortType/SayHiResponse
/outputActionMapping
/operation
/service
And in my message receiver I print out this
Using async Parameter? : messageReceiver.invokeOnSeparateThread=true
So to me the server side looks correct, any more tips on the client
cheers, Håkon
thanks,
Amila.
2009/9/17 Håkon Sagehaug hakon.sageh...@bccs.uib.no
hi
thanks for the tip.
I've added the parameter to the service.xml file. For simulating a
long running ws I 've got a simple echo service where I sleep the thread
in 1 minute, like this
try {
Thread.sleep(6);
} catch (InterruptedException e) {
e.printStackTrace();
}
And my client looks like this
EchoServiceStub stub;
try {
ConfigurationContext context = ConfigurationContextFactory
.createConfigurationContextFromFileSystem(repository,
null);
stub = new EchoServiceStub(context,
http://localhost:8080/axis2/services/EchoService;);
stub._getServiceClient().engageModule(addressing);
EchoServiceCallbackHandler callback = new
EchoServiceCallbackHandler() {
public void receiveResultSayHi(SayHiResponse resp) {
System.out.print(in callback + resp.getHiResponse());
System.exit(0);
}
public void receiveErrorSayHi(Exception e) {
e.printStackTrace();
}
};
SayHi hi = new SayHi();
hi.setHi(testu);
stub._getServiceClient().getOptions().setUseSeparateListener(true);
stub.startSayHi(hi, callback);
} catch (AxisFault e) {
e.printStackTrace();
} catch (RemoteException e) {
e.printStackTrace();
}
}
But even when I use separate transport listeners I get
org.apache.axis2.AxisFault: Read timed out
at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
at
org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:193)
at
org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:75)
at
org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:371)
at
org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:209)
at
org.apache.axis2.engine.AxisEngine$TransportNonBlockingInvocationWorker.run(AxisEngine.java:630)
at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1061)
at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:575)
at java.lang.Thread.run(Thread.java:619)
on the client side.
Any more configuration needed on either sides?
cheers, Håkon
2009/9/17 Amila Suriarachchi amilasuriarach...@gmail.com
2009/9/16 Håkon Sagehaug hakon.sageh...@bccs.uib.no
Hi
I wanted to try out to make a web service async, does anyone know of
a cookbook how to do that? I found this link[1] explaning how I want my
service to work. is it the AsyncMessageReceiver from the integration
module
in axis2 svn I should use? Basically I need som help and
Re: [ANNOUNCE] Rampart1.5 Release Candidate ready for testing
Hi Gerhard, In the last comment of the related issue [1], Thilina explains why we need to have both OpenSAML jars in the distribution. Nope, unfortunately there are no obsolete jars included. Do you want to reduce size or are you facing any other issue ? regards, Nandana [1] - https://issues.apache.org/jira/browse/RAMPART-231?focusedCommentId=12757014page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_12757014 On Wed, Sep 16, 2009 at 2:55 PM, gerhard presser gpres...@groiss.comwrote: Hi, Why are there two different versions of opensaml included in the dist-package? Are there any obsolete jars if I'm using axis2 with java 1.5? regards, gerhard Nunny wrote: Hi All, Apache Rampart 1.5 (Rampart version for Axis2 1.5) Release Candidate is available here. http://people.apache.org/~nandana/rampart-1.5/RC1/dist/http://people.apache.org/%7Enandana/rampart-1.5/RC1/dist/ And the M2 repository can be found here. http://people.apache.org/~nandana/rampart-1.5/RC1/m2_repo/http://people.apache.org/%7Enandana/rampart-1.5/RC1/m2_repo/ Please test and report any issues you may find. regards, Nandana -- View this message in context: http://www.nabble.com/-ANNOUNCE--Rampart1.5-Release-Candidate-ready-for-testing-tp25252220p25471798.html Sent from the Axis - User mailing list archive at Nabble.com.
Re: [ANNOUNCE] Rampart1.5 Release Candidate ready for testing
Hi Stefan, This is the compatible version with Axis2 1.5. These [1] will be the fixes / improvements / new features included in this release. Sorry this file was not included in the RC. regards, Nandana [1] - https://svn.apache.org/repos/asf/webservices/rampart/branches/java/1_5/release-docs/ChangeLog.txt On Thu, Sep 17, 2009 at 12:22 PM, stlecho stle...@gmail.com wrote: Hi, Is this version compatible with Axis2 v1.4 and/or v1.5? Where can I find a description of the features/modifications/fixes implemented in this version? Regards, Stefan Lecho. Nunny wrote: Hi All, Apache Rampart 1.5 (Rampart version for Axis2 1.5) Release Candidate is available here. http://people.apache.org/~nandana/rampart-1.5/RC1/dist/http://people.apache.org/%7Enandana/rampart-1.5/RC1/dist/ And the M2 repository can be found here. http://people.apache.org/~nandana/rampart-1.5/RC1/m2_repo/http://people.apache.org/%7Enandana/rampart-1.5/RC1/m2_repo/ Please test and report any issues you may find. regards, Nandana -- View this message in context: http://www.nabble.com/-ANNOUNCE--Rampart1.5-Release-Candidate-ready-for-testing-tp25252220p25488633.html Sent from the Axis - User mailing list archive at Nabble.com.
Re: Creating a async web sercice
2009/9/18 Håkon Sagehaug hakon.sageh...@bccs.uib.no
Hi
By the way, do you know why it did not work with 1.4.1, it this a known
limitation?
this parameter check added after axis2 1.4.1 :)
thanks,
Amila.
cheers, Håkon
2009/9/17 Håkon Sagehaug hakon.sageh...@bccs.uib.no
Hi
I changed to axis2 1.5 also on the server and then all seems to work.
Thanks for the help
cheers, Håkon
2009/9/17 Håkon Sagehaug hakon.sageh...@bccs.uib.no
Hi
I also get this error message
SEVERE: The Callback for MessageID
urn:uuid:E75DBDF30A77DAB1011253193935432 was not found
org.apache.axis2.AxisFault: The Callback for MessageID
urn:uuid:E75DBDF30A77DAB1011253193935432 was not found
cheers, Håkon
2009/9/17 Håkon Sagehaug hakon.sageh...@bccs.uib.no
Hi
I used axis2 1.4.1 and changed to 1.5, but I still got time out. I
changed just on the client side, server is still using 1.4.1
2009/9/17 Amila Suriarachchi amilasuriarach...@gmail.com
What is the Axis2 version you use? try with Axis2 1.5.
hope you have set the parameter correctly.
On the server or client side?
The service.xml looks like this
service name=EchoService
messageReceivers
messageReceiver mep=http://www.w3.org/ns/wsdl/in-out;
class=no.uib.bccs.esysbio.echoservice.EchoServiceMessageReceiverInOut/
/messageReceivers
parameter
name=messageReceiver.invokeOnSeparateThreadtrue/parameter
parameter
name=ServiceClassno.uib.bccs.esysbio.echoservice.EchoServiceImpl/parameter
parameter name=useOriginalwsdltrue/parameter
parameter name=modifyUserWSDLPortAddresstrue/parameter
operation name=SayHi mep=http://www.w3.org/ns/wsdl/in-out;
namespace=http://www.bccs.uib.no/EchoService.wsdl;
actionMapping
http://www.bccs.uib.no/EchoService.wsdl/SayHi/actionMapping
outputActionMapping
http://www.bccs.uib.no/EchoService.wsdl/EchoServicePortType/SayHiResponse
/outputActionMapping
/operation
/service
And in my message receiver I print out this
Using async Parameter? : messageReceiver.invokeOnSeparateThread=true
So to me the server side looks correct, any more tips on the client
cheers, Håkon
thanks,
Amila.
2009/9/17 Håkon Sagehaug hakon.sageh...@bccs.uib.no
hi
thanks for the tip.
I've added the parameter to the service.xml file. For simulating a
long running ws I 've got a simple echo service where I sleep the
thread
in 1 minute, like this
try {
Thread.sleep(6);
} catch (InterruptedException e) {
e.printStackTrace();
}
And my client looks like this
EchoServiceStub stub;
try {
ConfigurationContext context = ConfigurationContextFactory
.createConfigurationContextFromFileSystem(repository,
null);
stub = new EchoServiceStub(context,
http://localhost:8080/axis2/services/EchoService;);
stub._getServiceClient().engageModule(addressing);
EchoServiceCallbackHandler callback = new
EchoServiceCallbackHandler() {
public void receiveResultSayHi(SayHiResponse resp) {
System.out.print(in callback + resp.getHiResponse());
System.exit(0);
}
public void receiveErrorSayHi(Exception e) {
e.printStackTrace();
}
};
SayHi hi = new SayHi();
hi.setHi(testu);
stub._getServiceClient().getOptions().setUseSeparateListener(true);
stub.startSayHi(hi, callback);
} catch (AxisFault e) {
e.printStackTrace();
} catch (RemoteException e) {
e.printStackTrace();
}
}
But even when I use separate transport listeners I get
org.apache.axis2.AxisFault: Read timed out
at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
at
org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:193)
at
org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:75)
at
org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:371)
at
org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:209)
at
org.apache.axis2.engine.AxisEngine$TransportNonBlockingInvocationWorker.run(AxisEngine.java:630)
at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1061)
at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:575)
at java.lang.Thread.run(Thread.java:619)
on the client side.
Any more configuration needed on either sides?
cheers, Håkon
2009/9/17 Amila Suriarachchi amilasuriarach...@gmail.com
2009/9/16 Håkon Sagehaug hakon.sageh...@bccs.uib.no
Hi
I wanted to try out to make a web service async, does anyone know of
a cookbook how to do that? I found this link[1] explaning how I want my
service to
Re: securing axis2
On Wed, Sep 16, 2009 at 3:05 AM, Chris Snow sno...@snowconsulting.co.ukwrote: Is there any documentation on how to secure an axis2 installation. do you mean the files in the installation folder (eg. axis2.xml) or requests coming to server. for former case AFAIK the only solution is to protect the folder using some OS level security. For later as Srinath has said either we can use https or ws-security. thanks, Amila. Many thanks, Chris -- Amila Suriarachchi WSO2 Inc. blog: http://amilachinthaka.blogspot.com/
Re: [ANNOUNCE] Rampart1.5 Release Candidate ready for testing
Hi Nandana, -)Thanks for the explanation. Will the opensaml1.1 references be cleared out in the final release? -)At least the slf4j-jdk14 lib should be obsolete if another logging framework is used!? regards, Gerhard Nunny wrote: Hi Gerhard, In the last comment of the related issue [1], Thilina explains why we need to have both OpenSAML jars in the distribution. Nope, unfortunately there are no obsolete jars included. Do you want to reduce size or are you facing any other issue ? regards, Nandana [1] - https://issues.apache.org/jira/browse/RAMPART-231?focusedCommentId=12757014page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_12757014 On Wed, Sep 16, 2009 at 2:55 PM, gerhard presser gpres...@groiss.comwrote: Hi, Why are there two different versions of opensaml included in the dist-package? Are there any obsolete jars if I'm using axis2 with java 1.5? regards, gerhard Nunny wrote: Hi All, Apache Rampart 1.5 (Rampart version for Axis2 1.5) Release Candidate is available here. http://people.apache.org/~nandana/rampart-1.5/RC1/dist/http://people.apache.org/%7Enandana/rampart-1.5/RC1/dist/ And the M2 repository can be found here. http://people.apache.org/~nandana/rampart-1.5/RC1/m2_repo/http://people.apache.org/%7Enandana/rampart-1.5/RC1/m2_repo/ Please test and report any issues you may find. regards, Nandana -- View this message in context: http://www.nabble.com/-ANNOUNCE--Rampart1.5-Release-Candidate-ready-for-testing-tp25252220p25471798.html Sent from the Axis - User mailing list archive at Nabble.com. -- View this message in context: http://www.nabble.com/-ANNOUNCE--Rampart1.5-Release-Candidate-ready-for-testing-tp25252220p25504470.html Sent from the Axis - User mailing list archive at Nabble.com.
Re: [ANNOUNCE] Rampart1.5 Release Candidate ready for testing
Hi Gerhard, Please see my comments inline. On Fri, Sep 18, 2009 at 1:21 PM, gerhard presser gpres...@groiss.comwrote: Hi Nandana, -)Thanks for the explanation. Will the opensaml1.1 references be cleared out in the final release? IMO porting the SAML 1.1 code to use OpenSAML 2.x needs significant amount of work, since there is a drastic API change from OpenSAML 1.1 to OpenSAML 2.x. So I think this will not be fixed in the Rampart 1.5 release. -)At least the slf4j-jdk14 lib should be obsolete if another logging framework is used!? This is an added dependency from OpenSAML 2. OpenSAML 2 uses slf4j for its internal logging requirements. regards, Gerhard Is there anything that restricts you from using these jars ? If so please post it here, we can look for an alternative if possible.. Thanks. / thilina Nunny wrote: Hi Gerhard, In the last comment of the related issue [1], Thilina explains why we need to have both OpenSAML jars in the distribution. Nope, unfortunately there are no obsolete jars included. Do you want to reduce size or are you facing any other issue ? regards, Nandana [1] - https://issues.apache.org/jira/browse/RAMPART-231?focusedCommentId=12757014page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_12757014 On Wed, Sep 16, 2009 at 2:55 PM, gerhard presser gpres...@groiss.comwrote: Hi, Why are there two different versions of opensaml included in the dist-package? Are there any obsolete jars if I'm using axis2 with java 1.5? regards, gerhard Nunny wrote: Hi All, Apache Rampart 1.5 (Rampart version for Axis2 1.5) Release Candidate is available here. http://people.apache.org/~nandana/rampart-1.5/RC1/dist/http://people.apache.org/%7Enandana/rampart-1.5/RC1/dist/ http://people.apache.org/%7Enandana/rampart-1.5/RC1/dist/ And the M2 repository can be found here. http://people.apache.org/~nandana/rampart-1.5/RC1/m2_repo/http://people.apache.org/%7Enandana/rampart-1.5/RC1/m2_repo/ http://people.apache.org/%7Enandana/rampart-1.5/RC1/m2_repo/ Please test and report any issues you may find. regards, Nandana -- View this message in context: http://www.nabble.com/-ANNOUNCE--Rampart1.5-Release-Candidate-ready-for-testing-tp25252220p25471798.html Sent from the Axis - User mailing list archive at Nabble.com. -- View this message in context: http://www.nabble.com/-ANNOUNCE--Rampart1.5-Release-Candidate-ready-for-testing-tp25252220p25504470.html Sent from the Axis - User mailing list archive at Nabble.com.
http transporter, broken pipe exception catch
Hi, I am new using axis2 platform, and i have one problem related with the exceptions throws in the http transporter. Summary of the test: * I have one client, this client sends a soap message to the server. The transporter is http. The client upload a file (SWA). The client have a timeout. * I have one server, the server is a axis2 server with the default configuration. The server save the file and process it, and send ok or not ok to the client. Summary of the problem: If when the server is processing the file and the file upload has finished, the client close the connection (the time out close the connection), the server throws a broken pipe exception. how can i catch this exception, and roll-back the action? thanks in advance --gustavo
Re: [ANNOUNCE] Rampart1.5 Release Candidate ready for testing
Hi thilina, We are using Axis2 inside an commercial software which allready ships with many libraries. Because we don't (yet) use a dependency resolution mechanism, any developer adds libraries he thinks he will need. If implementations change, libs may become obsolete. If we don't keep track of this obsolete libs, our classpath would be full of garbage and our distribution package would be very large. Because of that, e.g. logging is very tricky if you are using lots of third party libs. Every lib may use another logging framework/facade. But to trace back possible errors it would be nice that all components log to the same destination. So there are some logging-facades available (commons-logging, slf4j). The components should use this facades for logging and don't need to mind where the log goes to. Because of that, I don't think that slf4j-jdk14 is an required dependency for this project. regards, Gerhard Thilina Buddhika wrote: Hi Gerhard, Please see my comments inline. On Fri, Sep 18, 2009 at 1:21 PM, gerhard presser gpres...@groiss.comwrote: Hi Nandana, -)Thanks for the explanation. Will the opensaml1.1 references be cleared out in the final release? IMO porting the SAML 1.1 code to use OpenSAML 2.x needs significant amount of work, since there is a drastic API change from OpenSAML 1.1 to OpenSAML 2.x. So I think this will not be fixed in the Rampart 1.5 release. -)At least the slf4j-jdk14 lib should be obsolete if another logging framework is used!? This is an added dependency from OpenSAML 2. OpenSAML 2 uses slf4j for its internal logging requirements. regards, Gerhard Is there anything that restricts you from using these jars ? If so please post it here, we can look for an alternative if possible.. Thanks. / thilina Nunny wrote: Hi Gerhard, In the last comment of the related issue [1], Thilina explains why we need to have both OpenSAML jars in the distribution. Nope, unfortunately there are no obsolete jars included. Do you want to reduce size or are you facing any other issue ? regards, Nandana [1] - https://issues.apache.org/jira/browse/RAMPART-231?focusedCommentId=12757014page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_12757014 On Wed, Sep 16, 2009 at 2:55 PM, gerhard presser gpres...@groiss.comwrote: Hi, Why are there two different versions of opensaml included in the dist-package? Are there any obsolete jars if I'm using axis2 with java 1.5? regards, gerhard Nunny wrote: Hi All, Apache Rampart 1.5 (Rampart version for Axis2 1.5) Release Candidate is available here. http://people.apache.org/~nandana/rampart-1.5/RC1/dist/http://people.apache.org/%7Enandana/rampart-1.5/RC1/dist/ http://people.apache.org/%7Enandana/rampart-1.5/RC1/dist/ And the M2 repository can be found here. http://people.apache.org/~nandana/rampart-1.5/RC1/m2_repo/http://people.apache.org/%7Enandana/rampart-1.5/RC1/m2_repo/ http://people.apache.org/%7Enandana/rampart-1.5/RC1/m2_repo/ Please test and report any issues you may find. regards, Nandana -- View this message in context: http://www.nabble.com/-ANNOUNCE--Rampart1.5-Release-Candidate-ready-for-testing-tp25252220p25471798.html Sent from the Axis - User mailing list archive at Nabble.com. -- View this message in context: http://www.nabble.com/-ANNOUNCE--Rampart1.5-Release-Candidate-ready-for-testing-tp25252220p25504470.html Sent from the Axis - User mailing list archive at Nabble.com. -- View this message in context: http://www.nabble.com/-ANNOUNCE--Rampart1.5-Release-Candidate-ready-for-testing-tp25252220p25505554.html Sent from the Axis - User mailing list archive at Nabble.com.
Using Axis without a binding?
Hi all, I need to develop a service who 'packs' an XML behind a certain URL into SOAP. In this case I don't want a binding. How should I use Axis in this case? What I would like to do is this: - create the WSDL - generate a webservice with Axis - connect the generated skeleton with the available XML in order to fill the Soap envelope. Is this possible?
Re: Fw: High Priority ,Parallel requests throwing null pointer exception.
This is a known issue that occurs when using Axiom = 1.2.8 together with Sun's StAX implementation. See issue WSCOMMONS-489. Andreas On Thu, Sep 17, 2009 at 15:33, sri ram pinnamaraju_sri...@yahoo.co.in wrote: Hi All, I have a webservice developed in axis 2. Works fine when there are sequence of requests. However when two parallel request hit the Axis Servlet I get exception. When I send these two requests sequentially everything is holy . So ideally,nothing is wrong with the request. PFA : For Error Stack trace Can Some one help me out on this. Should I make some changes in axis2.xml Or there's an patch available for Axis2 servlet for this scenario. Thanks, Sriram Keep up with people you care about with Yahoo! India Mail. Learn how. Add whatever you love to the Yahoo! India homepage. Try now! Now, send attachments up to 25MB with Yahoo! India Mail. Learn how.
Re: xs:date issues in axis2-1.5
I am using axis2-1.5.
I did not experience this error with 1.4.1 version even though I found this
issue AXIS2-4447.
This is my incoming object(pojo) using java.util.Date
import java.util.Date;
/**
* Test pojo with xs:data
* @author asen
*/
public class PojoIn implements PojoI {
private static final long serialVersionUID = 1L;
private Date date = null;
private String alias = null ;
public PojoIn(){}
public Date getDate() {
return date;
}
public void setDate(Date date) {
this.date = date;
}
public String getAlias() {
return alias;
}
public void setAlias(String alias) {
this.alias = alias;
}
@Override
public String toString() {
StringBuffer sb = new StringBuffer( DATA WS IN);
sb.append(DATE: + date).append(\n);
sb.append(ALIAS: + alias).append(\n);
return sb.toString();
}
}
And this is sample web method exposed as web service through Axis2-1.5
integration with Tomcat-6.0.16
public Long storeData(PojoIn data) throws Exception {
// implementation follow
return new Long(1);
}
On Fri, Sep 18, 2009 at 12:53 AM, Amila Suriarachchi
amilasuriarach...@gmail.com wrote:
On Fri, Sep 18, 2009 at 3:05 AM, Asen asen.m.ase...@gmail.com wrote:
Hi there,
I am getting error on xs:date manipulations at the server side.
Does anyone know any solution to this problem?
Exception in thread main org.apache.axis2.AxisFault: date string can not
be less than 19 charactors
at
org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:517)
at
org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:371)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:417)
at
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:229)
at
org.apache.axis2.client.OperationClient.execute(OperationClient.java:165)
wsdl snipped:
xs:element name=endDate minOccurs=0 type=xs:date nillable=true /
My client uses wsdl2java ADB binding.
how your service is written? what is the Axis2 version you use?
thanks,
Amila.
--
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/
'Convert' AAR to standalone WAR
Hello, I'm still learning about Axis2 and I'm wondering how to convert/build a AAR generated file to a Standalone WAR, instead of deploying it to axis2.war. Currently, I'm using JBOSS 4.2.0 GA as AS and Netbeans 6.5 with Axis2 plugin. If anyone has a tutorial or tip, please let me know. Thanks in advance, Rodolfo Andrade
Re: xs:date issues in axis2-1.5
Here is how I am setting the date from the client:
Calendar calendar = Calendar.getInstance();
calendar.clear();
calendar.set(2009,8,16);
java.util.Date date = calendar.getTime();
On Fri, Sep 18, 2009 at 9:08 AM, Asen asen.m.ase...@gmail.com wrote:
I am using axis2-1.5.
I did not experience this error with 1.4.1 version even though I found this
issue AXIS2-4447.
This is my incoming object(pojo) using java.util.Date
import java.util.Date;
/**
* Test pojo with xs:data
* @author asen
*/
public class PojoIn implements PojoI {
private static final long serialVersionUID = 1L;
private Date date = null;
private String alias = null ;
public PojoIn(){}
public Date getDate() {
return date;
}
public void setDate(Date date) {
this.date = date;
}
public String getAlias() {
return alias;
}
public void setAlias(String alias) {
this.alias = alias;
}
@Override
public String toString() {
StringBuffer sb = new StringBuffer( DATA WS IN);
sb.append(DATE: + date).append(\n);
sb.append(ALIAS: + alias).append(\n);
return sb.toString();
}
}
And this is sample web method exposed as web service through Axis2-1.5
integration with Tomcat-6.0.16
public Long storeData(PojoIn data) throws Exception {
// implementation follow
return new Long(1);
}
On Fri, Sep 18, 2009 at 12:53 AM, Amila Suriarachchi
amilasuriarach...@gmail.com wrote:
On Fri, Sep 18, 2009 at 3:05 AM, Asen asen.m.ase...@gmail.com wrote:
Hi there,
I am getting error on xs:date manipulations at the server side.
Does anyone know any solution to this problem?
Exception in thread main org.apache.axis2.AxisFault: date string can
not be less than 19 charactors
at
org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:517)
at
org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:371)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:417)
at
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:229)
at
org.apache.axis2.client.OperationClient.execute(OperationClient.java:165)
wsdl snipped:
xs:element name=endDate minOccurs=0 type=xs:date nillable=true
/
My client uses wsdl2java ADB binding.
how your service is written? what is the Axis2 version you use?
thanks,
Amila.
--
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/
Re: imcompatible issue between axis2 and weblogic 10
Hi, I am using Axis 2.1.5 which has axiom 1.2.8 on weblogic 9.2 and i still get a similar error.. java.lang.ClassCastException: com.ctc.wstx.stax.WstxInputFactory at javax.xml.stream.XMLInputFactory.newInstance(XMLInputFactory.java:136) at weblogic.servlet.internal.WebAppHelper.addListenerElements(WebAppHelper.java:244) at weblogic.servlet.internal.WebAppHelper$IOHelperImpl.parseXML(WebAppHelper.java:224) at weblogic.descriptor.DescriptorCache.parseXML(DescriptorCache.java:324) at weblogic.servlet.internal.WebAppHelper.registerTagLibListeners(WebAppHelper.java:174) at weblogic.servlet.internal.EventsManager.registerEventListeners(EventsManager.java:254) at weblogic.servlet.internal.WebAppServletContext.initContextListeners(WebAppServletContext.java:1591) at weblogic.servlet.internal.WebAppServletContext.prepare(WebAppServletContext.java:1036) at weblogic.servlet.internal.HttpServer.doPostContextInit(HttpServer.java:432) at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:407) at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:549) at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:284) at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176) Can someone help? Regards, Nirav
RE: imcompatible issue between axis2 and weblogic 10
Try to use Weblogic native StAX parser. _ From: Nirav Shah [mailto:snirav.s...@gmail.com] Sent: Friday, September 18, 2009 5:01 PM To: axis-user@ws.apache.org Subject: Re: imcompatible issue between axis2 and weblogic 10 Hi, I am using Axis 2.1.5 which has axiom 1.2.8 on weblogic 9.2 and i still get a similar error.. java.lang.ClassCastException: com.ctc.wstx.stax.WstxInputFactory at javax.xml.stream.XMLInputFactory.newInstance(XMLInputFactory.java:136) at weblogic.servlet.internal.WebAppHelper.addListenerElements(WebAppHelper. java:244) at weblogic.servlet.internal.WebAppHelper$IOHelperImpl.parseXML(WebAppHelpe r.java:224) at weblogic.descriptor.DescriptorCache.parseXML(DescriptorCache.java:324) at weblogic.servlet.internal.WebAppHelper.registerTagLibListeners(WebAppHel per.java:174) at weblogic.servlet.internal.EventsManager.registerEventListeners(EventsMan ager.java:254) at weblogic.servlet.internal.WebAppServletContext.initContextListeners(WebA ppServletContext.java:1591) at weblogic.servlet.internal.WebAppServletContext.prepare(WebAppServletCont ext.java:1036) at weblogic.servlet.internal.HttpServer.doPostContextInit(HttpServer.java:4 32) at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:407) at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java: 549) at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:284) at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModu leDriver.java:176) Can someone help? Regards, Nirav This email is confidential and subject to important disclaimers and conditions including on offers for the purchase or sale of securities, accuracy and completeness of information, viruses, confidentiality, legal privilege, and legal entity disclaimers, available at http://www.jpmorgan.com/pages/disclosures/email.
Re: imcompatible issue between axis2 and weblogic 10
Hi Mary, And how do i configure this ? Is there any configuration change that i need to do ? Regards, Nirav On Fri, Sep 18, 2009 at 2:04 PM, Hu, Mary - ITG mary...@jpmorgan.comwrote: Try to use Weblogic native StAX parser. -- *From:* Nirav Shah [mailto:snirav.s...@gmail.com] *Sent:* Friday, September 18, 2009 5:01 PM *To:* axis-user@ws.apache.org *Subject:* Re: imcompatible issue between axis2 and weblogic 10 Hi, I am using Axis 2.1.5 which has axiom 1.2.8 on weblogic 9.2 and i still get a similar error.. java.lang.ClassCastException: com.ctc.wstx.stax.WstxInputFactory at javax.xml.stream.XMLInputFactory.newInstance(XMLInputFactory.java:136) at weblogic.servlet.internal.WebAppHelper.addListenerElements(WebAppHelper.java:244) at weblogic.servlet.internal.WebAppHelper$IOHelperImpl.parseXML(WebAppHelper.java:224) at weblogic.descriptor.DescriptorCache.parseXML(DescriptorCache.java:324) at weblogic.servlet.internal.WebAppHelper.registerTagLibListeners(WebAppHelper.java:174) at weblogic.servlet.internal.EventsManager.registerEventListeners(EventsManager.java:254) at weblogic.servlet.internal.WebAppServletContext.initContextListeners(WebAppServletContext.java:1591) at weblogic.servlet.internal.WebAppServletContext.prepare(WebAppServletContext.java:1036) at weblogic.servlet.internal.HttpServer.doPostContextInit(HttpServer.java:432) at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:407) at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:549) at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:284) at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176) Can someone help? Regards, Nirav This email is confidential and subject to important disclaimers and conditions including on offers for the purchase or sale of securities, accuracy and completeness of information, viruses, confidentiality, legal privilege, and legal entity disclaimers, available at http://www.jpmorgan.com/pages/disclosures/email.
RE: imcompatible issue between axis2 and weblogic 10
Just remove Woodstock stax parser from application classpath. _ From: Nirav Shah [mailto:snirav.s...@gmail.com] Sent: Friday, September 18, 2009 5:18 PM To: axis-user@ws.apache.org Subject: Re: imcompatible issue between axis2 and weblogic 10 Hi Mary, And how do i configure this ? Is there any configuration change that i need to do ? Regards, Nirav On Fri, Sep 18, 2009 at 2:04 PM, Hu, Mary - ITG mary...@jpmorgan.com wrote: Try to use Weblogic native StAX parser. _ From: Nirav Shah [mailto:snirav.s...@gmail.com] Sent: Friday, September 18, 2009 5:01 PM To: axis-user@ws.apache.org Subject: Re: imcompatible issue between axis2 and weblogic 10 Hi, I am using Axis 2.1.5 which has axiom 1.2.8 on weblogic 9.2 and i still get a similar error.. java.lang.ClassCastException: com.ctc.wstx.stax.WstxInputFactory at javax.xml.stream.XMLInputFactory.newInstance(XMLInputFactory.java:136) at weblogic.servlet.internal.WebAppHelper.addListenerElements(WebAppHelper. java:244) at weblogic.servlet.internal.WebAppHelper$IOHelperImpl.parseXML(WebAppHelpe r.java:224) at weblogic.descriptor.DescriptorCache.parseXML(DescriptorCache.java:324) at weblogic.servlet.internal.WebAppHelper.registerTagLibListeners(WebAppHel per.java:174) at weblogic.servlet.internal.EventsManager.registerEventListeners(EventsMan ager.java:254) at weblogic.servlet.internal.WebAppServletContext.initContextListeners(WebA ppServletContext.java:1591) at weblogic.servlet.internal.WebAppServletContext.prepare(WebAppServletCont ext.java:1036) at weblogic.servlet.internal.HttpServer.doPostContextInit(HttpServer.java:4 32) at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:407) at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java: 549) at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:284) at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModu leDriver.java:176) Can someone help? Regards, Nirav This email is confidential and subject to important disclaimers and conditions including on offers for the purchase or sale of securities, accuracy and completeness of information, viruses, confidentiality, legal privilege, and legal entity disclaimers, available at http://www.jpmorgan.com/pages/disclosures/email. This email is confidential and subject to important disclaimers and conditions including on offers for the purchase or sale of securities, accuracy and completeness of information, viruses, confidentiality, legal privilege, and legal entity disclaimers, available at http://www.jpmorgan.com/pages/disclosures/email.
securing client request with name and password in axis2
Hi,all: I am using axis2 as webservice server.I want to securing client request with name and password.Only user name and password correct ,the client request can be processed;else The request will be refused.Is there existing module or handler can do this?
Re: securing client request with name and password in axis2
Please have a look at [1]. Thanks regards. -Prabath [1]: http://blog.rampartfaq.com/2009/08/how-to-secure-web-service-with_18.html jonah wrote: Hi,all: I am using axis2 as webservice server.I want to securing client request with name and password.Only user name and password correct ,the client request can be processed;else The request will be refused.Is there existing module or handler can do this?
