Hi Demetris,
Part of the problem is that J2ME compatibility is not the easiest thing
to determine - it's not like you can just set a compiler option and have
any compatibility problems reported during the build.
JiBX used to work on mobile devices, though I think the J2ME
compatibility for
You need the StAX API and a StAX implementation. This is already
included in Java 6. For Java 1.4 and 5, you can take the corresponding
JARs from the Axiom binary distribution.
Andreas
On Wed, Jun 24, 2009 at 18:45, Chris
Mannionchris.mann...@nonstopgov.com wrote:
Maybe I've misunderstood then
Good morning,
the Problem is, that i need to get the content-type from the
DataHandler-Object, as
the method should be an image-upload that should support various image-types
like gif, png, jpeg
and so on.
The next idea I have, is rerender the image on the server to jpeg using
ImageMagicks
Got it, thanks.
2009/6/25 Andreas Veithen andreas.veit...@gmail.com:
You need the StAX API and a StAX implementation. This is already
included in Java 6. For Java 1.4 and 5, you can take the corresponding
JARs from the Axiom binary distribution.
Andreas
On Wed, Jun 24, 2009 at 18:45, Chris
It looks like your Java runtime environment (GCJ/GNU classpath?) is
incomplete. I would recommend to install Sun's JRE for Linux.
Andreas
On Thu, Jun 25, 2009 at 02:12, Vadim
Letitchevskivletitchev...@teledyne.com wrote:
wsdl2java in axis2-1.5 did not work for me reporting exceptions like
Please note that Axis2 (as well as other Web service frameworks) use
the DataHandler class as a convenient way of representing data of type
base64binary. DataHandler is an existing class from the Java
Activation Framework and indeed has properties for content type and
(file) name. However, this
Could you share your code-snippet?
Chinmoy
On Thu, Jun 25, 2009 at 12:45 PM, Moritz Maedler m...@moritz-maedler.dewrote:
Good morning,
the Problem is, that i need to get the content-type from the
DataHandler-Object, as
the method should be an image-upload that should support various
Hello!
i posted the code snippet in my first post. If this isn't enough, pls
tell me which part you need.
Greetings!
Andreas,
I noticed the content-type info is preserved for SwA but MTOM does not
preserve the info you mentioned. I guess the file can be sent as an
attachment? Whats your opinion on this?
Chinmoy
On Thu, Jun 25, 2009 at 2:28 PM, Chinmoy Chakraborty cch...@gmail.comwrote:
Could you share your
Indeed. Since SwA uses MIME, the content type is sent over the wire in
a well defined way and Axis2/Axiom should be able to preserve it. Not
sure though for the (file) name. MTOM also uses MIME and a content
type is sent over the wire, but since MTOM is defined as an
alternative representation of
Hi all,
currently I'm using POJO deployment with a single service class.
I'd like the generated WSDL to contain proper fault definitions, but when I'm
using classes like the following then the WSDL contains far too much type
definitions for all sort of Axis-internal classes.
Service class:
Hello,
My Axis2 1.4.1 web service throws a NoSuchElementException only on the Test
Server (windows 2003) box.
The same aar works perfectly fine on my local machne(XP machine).
Looking at the stack trace, it complains about
MessageContextgetEnvelope()
But the wierdness is that this is fine
j...@ersl.ie writes:
Hi
I am developing an AXIS 1.4 client for a remote server (AXIS 1.3). The
axis guide:
http://ws.apache.org/axis/java/user-guide.html#ServiceStylesRPCDocumentWra
pp edAndMessage details a message structure (which is similar to what I
want):
soap:Body
Hi,
I am trying to call a web service that was written using some Oracle
Framework. I am using axis 1.4.1 with ADB binding and Java 1.4
When I call the service from my client I am getting below exception message
from the other side
?xml version = '1.0' encoding = 'UTF-8'?
SOAP-ENV:Envelope
Hi there,
I hope I am right here.
I´ve got a problem with client-server communication. I want to send more
than one requests to a server (WPS) which should be handled in an
asynchronized way. With axis2-1.4.1 I was able to send more requests to
the server, where the requests were handled and
Just to complete this thread here is how this problem was solved.
Our aar file used to contain the wsdls for the services and apparently this is
a problem with axis1.5. Note however that axis1.3 was fine with the wsdls being
part of the aar file. This is perhaps a bug in axis1.5 ?
When the
Hi Dennis,
finally a good response - I appreciate it.
I concur with you on the J2ME compatibility issues, in fact I did
experience that first hand in
my current implementations. I am looking into JiBX now, I knew a few
things about it but not
at the level that I can comfortably say
One more note - I was able to get Axis 1.4 to run on a CDC device using
Jalimo and
Knopflerfish OSGi as the container but as expected it is fairly slow ...
So yes, such
options are out of the question.
Dennis Sosnoski wrote:
Hi Demetris,
Part of the problem is that J2ME compatibility is
Dennis - sorry for the multiple postings - do you have any experience
with kSOAP/kSOAP2 and
do you think that could also be a viable solution for hosting WS on J2ME
devices?
Thanks
Dennis Sosnoski wrote:
Hi Demetris,
Part of the problem is that J2ME compatibility is not the easiest
thing
hi,
i would like to ask you a question about the wsdl.
when i devloped a (java) web service in .aar data, the address location in
wsdl ist something like http://localhost.;.
then i copied this .aar file to three different Host, each Host has
different IP Address. in each Host, the .aar
20 matches
Mail list logo
