On Wed, Jul 21, 2010 at 7:20 PM, Dan Wang wrote:
> Thanks Deepal for your quick response.
>
> Here is the message receiver part of my services.xml file,
>
>
> http://www.w3.org/ns/wsdl/in-out";
> class="com.xxx.www.MyServiceMessageReceiverInOut"/>
>
>
> And I DO have
Thanks Deepal for your quick response.
Here is the message receiver part of my services.xml file,
http://www.w3.org/ns/wsdl/in-out";
class="com.xxx.www.MyServiceMessageReceiverInOut"/>
And I DO have it in the compiled class.
I have searched over web, and read som
Hi Dan,
When you generate the code it generates services.xml file and it has entry
for one or more Message receivers, check whether you have all of them in the
compiled class before you create the aar, if you have all the classes then
we can go to next step to solve the problem.
Deepal
On Wed, J
Hi Andreas,
Thanks! That worked.
Regards,
Eric
Sent via BlackBerry from T-Mobile
-Original Message-
From: Eric Borisow
Date: Wed, 21 Jul 2010 11:16:14
To:
Reply-To: [email protected]
Subject: Re: Question about using byte array
Thanks Andreas, let me try that.
Eric
--- On
Hi,
I have struggled with the deploy exception for more than a week. Here is my
development environment, Axis2 1.4.1, JDK 1.6, Tomcat 6. I have generated the
skeleton, message receiver and related java files using WSDL2Java tool (adb
binding). I have tried to deploy the service in standalon
Thanks Andreas, let me try that.
Eric
--- On Wed, 7/21/10, Andreas Veithen wrote:
> From: Andreas Veithen
> Subject: Re: Question about using byte array
> To: [email protected]
> Date: Wednesday, July 21, 2010, 1:28 PM
> On Wed, Jul 21, 2010 at 19:18, Eric
> Borisow
> wrote:
> > Hi,
>
Hi,
WSDL2Java doesn't seem to work for SSL enabled wsdl urls..
I tried a couple of things to fix this:
1)Tried creating a custom SSL factory with a dummy trust manager and setting
it as the default SSL factory..
2) Tried setting javax.net.ssl.trustStore property..
both of them didn't work.
could y
A little more information about the difference in the byte array.
On the service side, the first value is:
0
On the client side, the values are:
1
0
From there until line 201, all of the values are the same. Then, on line 201,
the server side has:
-128
and the client side has an empty
On Wed, Jul 21, 2010 at 19:18, Eric Borisow wrote:
> Hi,
>
> I am trying to pass an LDAP cookie in a byte array from my web service using
> Axis2 1.4.1. In my wsdl, I have this entry:
>
> type="xs:byte"/>
That is not a good way to model binary data. A much better way is to
use a single instanc
Hi,
I am trying to pass an LDAP cookie in a byte array from my web service using
Axis2 1.4.1. In my wsdl, I have this entry:
Using ADB, a setCookie method is generated for me that takes a byte array as a
parameter. I pass in the byte array directly from the LDAP code. It all looks
good wh
Abhishek,
Section 3.2.2.1 of the XML schema specs says this:
"An instance of a datatype that is defined as boolean can have the
following legal literals {true, false, 1, 0}."
If your service doesn't allow 0, then it must not declare the element
as xsd:boolean.
Andreas
On Mon, Jul 19, 2010 at 2
Hi,
I have a wsdl with the following byte[] defined:
Using ADB, the generated code correctly has a byte array. I am basically
trying to send a cookie from JLDAP over the wire. However, it seems that
something is getting lost in the conversion. On the server side, I get the
following outpu
http://ws.apache.org/commons/transport/download.cgi
On Wed, Jul 21, 2010 at 09:38, dcausevic wrote:
>
> This problem was fixed when I added $ACTIVEMQ_HOME/activemq-all-5.3.2.jar to
> Axis2 classpath, but that was not all.
> Appearently this had also to do with version 1.5.1... Namely I discovered
This problem was fixed when I added $ACTIVEMQ_HOME/activemq-all-5.3.2.jar to
Axis2 classpath, but that was not all.
Appearently this had also to do with version 1.5.1... Namely I discovered
that both org.apache.axis2.transport.jms.JMSListener, and JSMSender are
removed from lib/axis2-kernel-1.5.1.
14 matches
Mail list logo
