Hi All,
We have enabled JMS transportreceiver and JMS transportsender on axis2 v1.5.1
with JMS transport v1.0.0 to connect to IBM Websphere MQ v7.0.1.2. My
application is deployed on Tomcat v6.0.28. Below are the parameters defined in
the services.xml for our service:
true
true
MyConnectionFac
p2n [,, wrote:
Hi Haipeng
We are all busy and no-one has any obligation to respond, so posting several
times in a row isn't productive (and often considered rude).
I am changing the namespace reported by using a schema tag in my service
definition (services.xml), specifically using the sch
hi,
I am plaining to do an axis2 training[1] at forth coming Apache Con at
Atlanta.
If you wish to attend you can register now.
Here is a list of thing I am plaining to do. If anyone coming and wants to
add a certain part please let me know.
Part 1 (Using Axis2)
Introduction
(Demo : Adm
I have done that, and I didn't have problem with name space from the
service. Basically, here's what I did:
1) Created Java classes/interfaces all in a same package
2) Generates WSDL with namespace mapping options. There are several
mappings there, not just one.
You can check the WSDL to make sur
If you think that is rude, I gave my appology for this. Because I need to
fix this problem as soon as possible. And I search internet for several days
and can not get any answer for this.
I read that article several times . It just works for service class. Inside
service, I use some pojos which are
Dear All,
We were facing this problem since a month and today finally we got
solution. I just registered to share resolution with communicty.
We simply set "javax.xml.soap.SOAPFactory" property to
"org.apache.axis.soap.SOAPFactoryImpl" and kepr axis-saaj-1.x.jar into
classpath. Below is ar
