You are viewing a plain text version of this content. The canonical link for it is here.

Posted to java-user@axis.apache.org by Cristian Bullokles <cr...@gmail.com> on 2008/06/07 00:09:47 UTC

Include a jar library in .aar file

All,
    Could  I include a jar file with a library in the aar file?
    I like to create self-contained services without depends on
libraries in the WEB-INF/lib folder.
    I'm using axis2 1.4 in tomcat 6.0.14

Regards
Cristian

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org

Re: [Axis2:v1.4] WSDL / SOAP Attachment question

Posted by Deepal Jayasinghe <de...@opensource.lk>.


Marc Lefebvre wrote:
> So, in a JAVA class, which JAVA data type in a method call generates this xmime:base64Binary WSDL data type when using JAVA2WSDL?  
Both datahandler and byte[]

-Deepal
>  I could n



---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org

RE: [Axis2:v1.4] WSDL / SOAP Attachment question

Posted by Raghu Upadhyayula <ru...@responsys.com>.

Use javax.activation.DataHandler 

-Raghu

-----Original Message-----
From: Marc Lefebvre [mailto:mlefebvre@akimeka.com] 
Sent: Tuesday, June 10, 2008 10:26 AM
To: axis-user@ws.apache.org
Subject: RE: [Axis2:v1.4] WSDL / SOAP Attachment question

So, in a JAVA class, which JAVA data type in a method call generates
this xmime:base64Binary WSDL data type when using JAVA2WSDL?   I could
not ascertain that from the examples I have seen.  Most of these seems
to start from a WSDL and generate the Java.  I'm starting with JAVA and
need to generate the WSDL for this.

__
Marc Lefebvre, Principle Software Engineer
Akimeka, 1305 N. Holopono Street, Kihei, HI 96753 
Phone: (808)442-7168, Email: mlefebvre@akimeka.com
echo '16i[q]sa[ln0=aln100%Pln100/snlbx]sbA0D4D465452snlbxq' | dc

________________________________

From: Enaganti M Naidu [mailto:emadhav@hotmail.com]
Sent: Fri 6/6/2008 5:58 PM
To: axis-user@ws.apache.org
Subject: RE: [Axis2:v1.4] WSDL / SOAP Attachment question

There should be no difference between SWA and MTOM. MTOM is backward
compatiable with SWA, at least in Axis2.

The dataType for binary in Axis2 is DataHandler. So you may have to use 
<element name="documentBinaryData" type="xmime:base64Binary"
 xmlns:xmime="http://www.w3.org/2005/05/xmlmime>
 in the XML schema. I might have shared a sample MTOM eclipse Project
recently which you can refer to.

________________________________

	Subject: [Axis2:v1.4] WSDL / SOAP Attachment question
	Date: Fri, 6 Jun 2008 14:05:52 -1000
	From: mlefebvre@akimeka.com
	To: axis-user@ws.apache.org

	If I use POJO for my WebService class and I use Java2WSDL for
auto-generation of the WSDL, what data type should I use to indicate in
the WSDL that the operation expects a soap with attachment?  Any
difference between SwA and MTOM for this?
	__
	Marc Lefebvre, Principle Software Engineer
	Akimeka, 1305 N. Holopono Street, Kihei, HI 96753 
	Phone: (808)442-7168, Email: mlefebvre@akimeka.com
	echo '16i[q]sa[ln0=aln100%Pln100/snlbx]sbA0D4D465452snlbxq' | dc

________________________________

Instantly invite friends from Facebook and other social networks to join
you on Windows Live(tm) Messenger. Invite friends now!
<https://www.invite2messenger.net/im/?source=TXT_EML_WLH_InviteFriends>

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org

RE: [Axis2:v1.4] WSDL / SOAP Attachment question

Posted by Marc Lefebvre <ml...@akimeka.com>.

So, in a JAVA class, which JAVA data type in a method call generates this xmime:base64Binary WSDL data type when using JAVA2WSDL?   I could not ascertain that from the examples I have seen.  Most of these seems to start from a WSDL and generate the Java.  I'm starting with JAVA and need to generate the WSDL for this.
 
__
Marc Lefebvre, Principle Software Engineer
Akimeka, 1305 N. Holopono Street, Kihei, HI 96753 
Phone: (808)442-7168, Email: mlefebvre@akimeka.com
echo '16i[q]sa[ln0=aln100%Pln100/snlbx]sbA0D4D465452snlbxq' | dc


________________________________

From: Enaganti M Naidu [mailto:emadhav@hotmail.com]
Sent: Fri 6/6/2008 5:58 PM
To: axis-user@ws.apache.org
Subject: RE: [Axis2:v1.4] WSDL / SOAP Attachment question


There should be no difference between SWA and MTOM. MTOM is backward compatiable with SWA, at least in Axis2.
 
The dataType for binary in Axis2 is DataHandler. So you may have to use 
<element name="documentBinaryData" type="xmime:base64Binary"
 xmlns:xmime="http://www.w3.org/2005/05/xmlmime>
 in the XML schema. I might have shared a sample MTOM eclipse Project recently which you can refer to.






________________________________

	Subject: [Axis2:v1.4] WSDL / SOAP Attachment question
	Date: Fri, 6 Jun 2008 14:05:52 -1000
	From: mlefebvre@akimeka.com
	To: axis-user@ws.apache.org
	
	
	If I use POJO for my WebService class and I use Java2WSDL for auto-generation of the WSDL, what data type should I use to indicate in the WSDL that the operation expects a soap with attachment?  Any difference between SwA and MTOM for this?
	__
	Marc Lefebvre, Principle Software Engineer
	Akimeka, 1305 N. Holopono Street, Kihei, HI 96753 
	Phone: (808)442-7168, Email: mlefebvre@akimeka.com
	echo '16i[q]sa[ln0=aln100%Pln100/snlbx]sbA0D4D465452snlbxq' | dc


________________________________

Instantly invite friends from Facebook and other social networks to join you on Windows Live(tm) Messenger. Invite friends now! <https://www.invite2messenger.net/im/?source=TXT_EML_WLH_InviteFriends>  

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org

Re: [Axis2:v1.4] WSDL / SOAP Attachment question

Posted by Thilina Gunarathne <cs...@gmail.com>.

Axis2 does not support SwA using pojo deployment or java2wsdl..

You can use javax.activation.DataHandler data type to generate a
base64Binary(MTOM compatible) WSDL...

thanks,
~Thilina

On Mon, Jun 9, 2008 at 1:50 PM, Marc Lefebvre <ml...@akimeka.com> wrote:

> So, in a JAVA class, which JAVA data type in a method call generates this
> xmime:base64Binary WSDL data type when using JAVA2WSDL?   I could ascertain
> that from the examples I have seen.  Most of these seems to start from a
> WSDL and generate the Java.  I'm starting with JAVA and need to generate the
> WSDL for this.
>
> __
> Marc Lefebvre, Principle Software Engineer
> Akimeka, 1305 N. Holopono Street, Kihei, HI 96753
> Phone: (808)442-7168, Email: mlefebvre@akimeka.com
> echo '16i[q]sa[ln0=aln100%Pln100/snlbx]sbA0D4D465452snlbxq' | dc
>
>
> ________________________________
>
> From: Enaganti M Naidu [mailto:emadhav@hotmail.com]
> Sent: Fri 6/6/2008 5:58 PM
> To: axis-user@ws.apache.org
> Subject: RE: [Axis2:v1.4] WSDL / SOAP Attachment question
>
>
> There should be no difference between SWA and MTOM. MTOM is backward
> compatiable with SWA, at least in Axis2.
>
> The dataType for binary in Axis2 is DataHandler. So you may have to use
> <element name="documentBinaryData" type="xmime:base64Binary"
>  xmlns:xmime="http://www.w3.org/2005/05/xmlmime>
>  in the XML schema. I might have shared a sample MTOM eclipse Project
> recently which you can refer to.
>
>
>
>
>
>
> ________________________________
>
>        Subject: [Axis2:v1.4] WSDL / SOAP Attachment question
>        Date: Fri, 6 Jun 2008 14:05:52 -1000
>        From: mlefebvre@akimeka.com
>        To: axis-user@ws.apache.org
>
>
>        If I use POJO for my WebService class and I use Java2WSDL for
> auto-generation of the WSDL, what data type should I use to indicate in the
> WSDL that the operation expects a soap with attachment?  Any difference
> between SwA and MTOM for this?
>        __
>        Marc Lefebvre, Principle Software Engineer
>        Akimeka, 1305 N. Holopono Street, Kihei, HI 96753
>        Phone: (808)442-7168, Email: mlefebvre@akimeka.com
>        echo '16i[q]sa[ln0=aln100%Pln100/snlbx]sbA0D4D465452snlbxq' | dc
>
>
> ________________________________
>
> Instantly invite friends from Facebook and other social networks to join
> you on Windows Live(tm) Messenger. Invite friends now! <
> https://www.invite2messenger.net/im/?source=TXT_EML_WLH_InviteFriends>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>



-- 
Thilina Gunarathne - http://thilinag.blogspot.com

RE: Invalid UTF-8 character encoding in SOAP response

Posted by Amandeep Singh <as...@quark.com>.

Posting solution.

The issue is with UTF8Encoder class of axis. The class does not consider
surrogate characters. The solution is to override that class to handle
surrogates.

Is this fixed in latest version of axis? Just curious.

Thanks,
Aman

-----Original Message-----
From: Amandeep Singh [mailto:asingh@quark.com] 
Sent: Monday, June 09, 2008 3:09 PM
To: axis-user@ws.apache.org
Subject: RE: Invalid UTF-8 character encoding in SOAP response

Thanks Andreas. 

My bad. The entity being produced is &#xD869;&#xDE1A;

So, anyone who has axis 1 experience, any suggestions as to how to force
axis to output correct entity?

Thanks,
Aman

-----Original Message-----
From: Andreas Veithen [mailto:andreas.veithen@skynet.be] 
Sent: Monday, June 09, 2008 2:59 PM
To: axis-user@ws.apache.org
Subject: Re: Invalid UTF-8 character encoding in SOAP response

Aman,

D869 DE1A is actually the surrogate pair for the character with code  
point 2A61A, which is encoded as F0AA989A in UTF-8 (see
http://www.cogsci.ed.ac.uk/~richard/utf-8.cgi) 
. The two other character references (&#xD858;&#xDF4C;) correspond to  
another character. I'm not an expert, but the XML specs don't mention  
surrogate pairs and I think that the correct way of encoding the  
character as a character reference should be &#x2A61A; in this case.  
This definitely looks like a bug in the XML parser. I would try to  
replace the XML parser by a new version of the same parser or by  
another parser. I'm not familiar with Axis 1, so I don't know what  
kind of parser (SAX or StAX) it uses. Maybe somebody else on the list  
can give a hint?

Andreas

On 9 juin 08, at 22:18, Amandeep Singh wrote:

> Hi All,
>
> I am using axis 1.3. If the response contains a CJK character in  
> UTF-8, axis converts it into an xml entity. On the receiver side,  
> xml parsing fails saying that it is an invalid xml entity.
>
> The character used has UTF-8 value F0AA989A. And axis converts it  
> into &#xD869;&#xDE1A;&#xD858;&#xDF4C;. And parser fails at first  
> entity.
>
> Any ideas/hints would be greatly appreciated?
>
> Thanks,
> Aman

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org

RE: Invalid UTF-8 character encoding in SOAP response

Posted by Amandeep Singh <as...@quark.com>.

Thanks Andreas. 

My bad. The entity being produced is &#xD869;&#xDE1A;

So, anyone who has axis 1 experience, any suggestions as to how to force
axis to output correct entity?

Thanks,
Aman

-----Original Message-----
From: Andreas Veithen [mailto:andreas.veithen@skynet.be] 
Sent: Monday, June 09, 2008 2:59 PM
To: axis-user@ws.apache.org
Subject: Re: Invalid UTF-8 character encoding in SOAP response

Aman,

D869 DE1A is actually the surrogate pair for the character with code  
point 2A61A, which is encoded as F0AA989A in UTF-8 (see
http://www.cogsci.ed.ac.uk/~richard/utf-8.cgi) 
. The two other character references (&#xD858;&#xDF4C;) correspond to  
another character. I'm not an expert, but the XML specs don't mention  
surrogate pairs and I think that the correct way of encoding the  
character as a character reference should be &#x2A61A; in this case.  
This definitely looks like a bug in the XML parser. I would try to  
replace the XML parser by a new version of the same parser or by  
another parser. I'm not familiar with Axis 1, so I don't know what  
kind of parser (SAX or StAX) it uses. Maybe somebody else on the list  
can give a hint?

Andreas

On 9 juin 08, at 22:18, Amandeep Singh wrote:

> Hi All,
>
> I am using axis 1.3. If the response contains a CJK character in  
> UTF-8, axis converts it into an xml entity. On the receiver side,  
> xml parsing fails saying that it is an invalid xml entity.
>
> The character used has UTF-8 value F0AA989A. And axis converts it  
> into &#xD869;&#xDE1A;&#xD858;&#xDF4C;. And parser fails at first  
> entity.
>
> Any ideas/hints would be greatly appreciated?
>
> Thanks,
> Aman

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org

Re: Invalid UTF-8 character encoding in SOAP response

Posted by Andreas Veithen <an...@skynet.be>.

Aman,

D869 DE1A is actually the surrogate pair for the character with code  
point 2A61A, which is encoded as F0AA989A in UTF-8 (see http://www.cogsci.ed.ac.uk/~richard/utf-8.cgi) 
. The two other character references (&#xD858;&#xDF4C;) correspond to  
another character. I'm not an expert, but the XML specs don't mention  
surrogate pairs and I think that the correct way of encoding the  
character as a character reference should be &#x2A61A; in this case.  
This definitely looks like a bug in the XML parser. I would try to  
replace the XML parser by a new version of the same parser or by  
another parser. I'm not familiar with Axis 1, so I don't know what  
kind of parser (SAX or StAX) it uses. Maybe somebody else on the list  
can give a hint?

Andreas

On 9 juin 08, at 22:18, Amandeep Singh wrote:

> Hi All,
>
> I am using axis 1.3. If the response contains a CJK character in  
> UTF-8, axis converts it into an xml entity. On the receiver side,  
> xml parsing fails saying that it is an invalid xml entity.
>
> The character used has UTF-8 value F0AA989A. And axis converts it  
> into &#xD869;&#xDE1A;&#xD858;&#xDF4C;. And parser fails at first  
> entity.
>
> Any ideas/hints would be greatly appreciated?
>
> Thanks,
> Aman

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org

Invalid UTF-8 character encoding in SOAP response

Posted by Amandeep Singh <as...@quark.com>.

Hi All,

 

I am using axis 1.3. If the response contains a CJK character in UTF-8,
axis converts it into an xml entity. On the receiver side, xml parsing
fails saying that it is an invalid xml entity.

 

The character used has UTF-8 value F0AA989A. And axis converts it into
&#xD869;&#xDE1A;&#xD858;&#xDF4C;. And parser fails at first entity.

 

Any ideas/hints would be greatly appreciated?

 

Thanks,

Aman

RE: [Axis2:v1.4] WSDL / SOAP Attachment question

Posted by Marc Lefebvre <ml...@akimeka.com>.

So, in a JAVA class, which JAVA data type in a method call generates this xmime:base64Binary WSDL data type when using JAVA2WSDL?   I could ascertain that from the examples I have seen.  Most of these seems to start from a WSDL and generate the Java.  I'm starting with JAVA and need to generate the WSDL for this.
 
__
Marc Lefebvre, Principle Software Engineer
Akimeka, 1305 N. Holopono Street, Kihei, HI 96753 
Phone: (808)442-7168, Email: mlefebvre@akimeka.com
echo '16i[q]sa[ln0=aln100%Pln100/snlbx]sbA0D4D465452snlbxq' | dc


________________________________

From: Enaganti M Naidu [mailto:emadhav@hotmail.com]
Sent: Fri 6/6/2008 5:58 PM
To: axis-user@ws.apache.org
Subject: RE: [Axis2:v1.4] WSDL / SOAP Attachment question


There should be no difference between SWA and MTOM. MTOM is backward compatiable with SWA, at least in Axis2.
 
The dataType for binary in Axis2 is DataHandler. So you may have to use 
<element name="documentBinaryData" type="xmime:base64Binary"
 xmlns:xmime="http://www.w3.org/2005/05/xmlmime>
 in the XML schema. I might have shared a sample MTOM eclipse Project recently which you can refer to.






________________________________

	Subject: [Axis2:v1.4] WSDL / SOAP Attachment question
	Date: Fri, 6 Jun 2008 14:05:52 -1000
	From: mlefebvre@akimeka.com
	To: axis-user@ws.apache.org
	
	
	If I use POJO for my WebService class and I use Java2WSDL for auto-generation of the WSDL, what data type should I use to indicate in the WSDL that the operation expects a soap with attachment?  Any difference between SwA and MTOM for this?
	__
	Marc Lefebvre, Principle Software Engineer
	Akimeka, 1305 N. Holopono Street, Kihei, HI 96753 
	Phone: (808)442-7168, Email: mlefebvre@akimeka.com
	echo '16i[q]sa[ln0=aln100%Pln100/snlbx]sbA0D4D465452snlbxq' | dc


________________________________

Instantly invite friends from Facebook and other social networks to join you on Windows Live(tm) Messenger. Invite friends now! <https://www.invite2messenger.net/im/?source=TXT_EML_WLH_InviteFriends>

RE: [Axis2:v1.4] WSDL / SOAP Attachment question

Posted by Enaganti M Naidu <em...@hotmail.com>.

There should be no difference between SWA and MTOM. MTOM is backward compatiable with SWA, at least in Axis2.
 
The dataType for binary in Axis2 is DataHandler. So you may have to use 
<element name="documentBinaryData" type="xmime:base64Binary"
 xmlns:xmime="http://www.w3.org/2005/05/xmlmime>
 in the XML schema. I might have shared a sample MTOM eclipse Project recently which you can refer to.


Subject: [Axis2:v1.4] WSDL / SOAP Attachment questionDate: Fri, 6 Jun 2008 14:05:52 -1000From: mlefebvre@akimeka.comTo: axis-user@ws.apache.org


If I use POJO for my WebService class and I use Java2WSDL for auto-generation of the WSDL, what data type should I use to indicate in the WSDL that the operation expects a soap with attachment?  Any difference between SwA and MTOM for this?
__
Marc Lefebvre, Principle Software Engineer
Akimeka, 1305 N. Holopono Street, Kihei, HI 96753 
Phone: (808)442-7168, Email: mlefebvre@akimeka.com
echo '16i[q]sa[ln0=aln100%Pln100/snlbx]sbA0D4D465452snlbxq' | dc

_________________________________________________________________
Instantly invite friends from Facebook and other social networks to join you on Windows Live™ Messenger.
https://www.invite2messenger.net/im/?source=TXT_EML_WLH_InviteFriends

[Axis2:v1.4] WSDL / SOAP Attachment question

Posted by Marc Lefebvre <ml...@akimeka.com>.

If I use POJO for my WebService class and I use Java2WSDL for auto-generation of the WSDL, what data type should I use to indicate in the WSDL that the operation expects a soap with attachment?  Any difference between SwA and MTOM for this?
__
Marc Lefebvre, Principle Software Engineer
Akimeka, 1305 N. Holopono Street, Kihei, HI 96753 
Phone: (808)442-7168, Email: mlefebvre@akimeka.com
echo '16i[q]sa[ln0=aln100%Pln100/snlbx]sbA0D4D465452snlbxq' | dc