Hi,
I though about something like that, too, for the same reason. However,
there's two caveats to the idea:
- REST services do not expose an interface definition a la WSDL... there
would be WADL, but IMHO you currently seem to rather encounter a lion in
alaska than a WADL file in the real w
That's because there are by default two different SOAP bindings in a
Axis2 WSDL definition. One is a SOAP 1.1 binding, the other SOAP 1.2. So
one of the wrappers uses the SOAP1.1 binding, and the other uses SOAP1.2
/philipp
[EMAIL PROTECTED] schrieb:
I am generating a proxy client using adb be
Hi Sushant,
"thus i am trying to find a solution, that is common across."
I wonder how WSIF would help you with that problem? WSIF is based on a
rather old Axis1 version, which is iirc not exactly an interoperability
miracle. I think you would be better off using either Axis2, Codehaus
XFire
example, this issue with
> OMElement. Where could I find a deeper explanation about using Axis2
> and it's databinding capabilities, and maybe more examples?
>
> Thanks for your answers.
>
>
>
> Philipp Leitner <[EMAIL PROTECTED]> wrote:
>
> > &qu
and CPU usage
(OutOfMemoryError) on API call
if you transferring heavy data oevr the wire, consider using mtom.
On 31/01/2008, *Philipp Leitner* <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
Still not sure whether you expirience the exception on client or server
side.
hen in the long[] and return the long[] back to
the client.
Thanks
Raghu
-Original Message-
From: Philipp Leitner [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 31, 2008 5:05 AM
To: axis-user@ws.apache.org
Subject: Re: [Axis2] Webservices - 100% Memory and CPU usage
(OutOfMemoryError) o
How many elements are there in your long[] when you run out of memory?
When exactly does the exception happen (in your app logic, during
wrapping, during transmission, on client side?).
/philipp
Raghu Upadhyayula schrieb:
Hi,
I have a webservice API call which is using 100% of Memory & CP
Probably including XHTML document in a CDATA section helps, i.e. instead
of passing back
..
you pass back
(on client-side you would obviously have to strip the CDATA tags again).
On a sidenote, I am not sure if your design (Web service that returns a
XHTML response encoded as String) is
If you have a SOAP-based endpoint (i.e., either SOAP 1.1 or 1.2 binding)
then you just can't invoke the service using your browser. The service
expects a well-formed SOAP input, while your browser only sends a simple
HTTP GET request.
If you have deployed your service using Axis2 and the stand
java.util.Properties is a variant of a hashtable. It is very hard to
serialize something like a hashtable in an interoperable way to XML. You
should transform your properties file into something easier to handle.
As a general rule you should stay away from all java.util.Collections
data struct
With the help of this list I once came up with a client like this:
Options op = new Options();
op.setTo(new EndpointReference(endpoint));
op.setProperty(Constants.Configuration.ENABLE_REST,
Constants.VALUE_TRUE);
op.setProperty (Constants.Configuration.HTTP_METHOD,
Constants.Configuration.HTT
Seems strange to me. If I remember my XML basics course correctly then
'xmlns=""' is the same as having no namespace declaration at all
(supposing that you do not have a default namespace). If that is correct
then both SOAP requests that you mentioned are absolutely identical.
Personally I wou
Depending on the size of the text (!) file a simple String might do.
/philipp
Charitha Kankanamge schrieb:
feh wrote:
Hi folks.
I've got an Axis2 client that needs to send a text file to an Axis2
server.
What's the best way to accomplish this?
Thanks!
MTOM (SOAP message transmission an
yes, doc/lit with wrapped parameters is WS-I conform. See
http://www.ibm.com/developerworks/webservices/library/ws-whichwsdl/ for
details on the different variants of WSDL encodings.
/philipp
Michael Imhof wrote:
The only types of SOAP bindings supported is document/literal and
rpc/literal.
I
System.setProperties(systemSettings);
now I'm getting Server did not recognize the value of HTTP Header SOAPAction.
I'm trying to figure out the problem though I have the impression I'm doing
something wrong somewhere
- Original Message
From: Philipp Leitner <[EMA
: Philipp Leitner <[EMAIL PROTECTED]>
To: axis-user@ws.apache.org
Sent: Thursday, October 4, 2007 3:24:30 PM
Subject: Re: new to axis
are you connected to the internet when you run the example?
/philipp
loredana loredana wrote:
Hy guys, I'm new to axis and I am having a small problem underst
are you connected to the internet when you run the example?
/philipp
loredana loredana wrote:
Hy guys, I'm new to axis and I am having a small problem understanding even the begining example...ok, so i took the most simple web service from w3 schools: http://www.w3schools.com/webservices/tempcon
AFAIK == as far as I Know :) don't look for that
/philipp
at4david wrote:
Thank you again, I will look for AFAIK in Internet and I will try it on.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail:
Not sure about that, but AFAIK Apache Axis (2?) has something like an
Interceptor (as in the POSA pattern) interface (is it called Handler
Chain interface, or something?) ... using this interface you might be
able to hook these WSS4J events and do your measures. At the moment I
cannot provide d
yes, the content-length specifies the size of the message in bytes
/philipp
at4david schrieb:
Thank you very much for your response, but I have a another question, Octects
= Number of bytes of the body message???
Thank you in advance
--
see http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html, 14.13,
Content-Length:
"The Content-Length entity-header field indicates the size of the
entity-body, in decimal number of OCTETs, sent to the recipient or, in
the case of the HEAD method, the size of the entity-body that would have
First of all, thanks a lot for this information (although I think it
should go somewhere onto the online documentation).
However, now I am getting some errors while deploying the doc/lit bare
service. The root seems to be:
INFO: Deploying Web service version.aar
org.apache.axis2.deployment.D
Hi all,
just a quick question: how can I tell Axis2 to deploy a POJO service as
defined for instance in http://ws.apache.org/axis2/1_3/pojoguide.html
using the 'bare' parameter style for doc/lit (instead of the default
'wrapped')? I have not yet found any documentation on this, and can't
seem
The code you are using is Axis 1, not Axis 2. Either switch your code to
Axis 2 or deploy the old Axis 1.4 (?) jars instead of the Axis 2 ones.
In general it is desirable to use the newer Axis 2. For a tutorial on
how to do stubless invocations look at
http://today.java.net/pub/a/today/2006/12
AFAIK Axis 2 does not support RPC/encoded at all since it is not WS-I
compliant.
/philipp
alpatino2 schrieb:
Hi!
I have a slightly different requirement: I received wsdl's from a service
provider that implements the TR-069 spec, this spec define the use of
rpc/encoded style. I need to invoke
Most probably it is :) I was just suggesting a quick workaround that
should reliably work :)
/philipp
Jochen Zink wrote:
Thanks,
but is it not possible to use addNamespace() Methode?
regards.
Jochen
-Ursprüngliche Nachricht-
Von: axis-user@ws.apache.org
Gesendet: 25.07.07 12:03:3
Hi,
you can try to get around this problem by changing the XPath expression:
For instance you can rewrite the query
//ex:TITLE (with xmlns:ex="http://www.example.com/cds";)
as
//*[local-name(.) = 'TITEL' and namespace-uri(.) =
'http://www.example.com/cds']
Not exactly the most pretty XPa
dacoss/eval/doc/";>
...
...
...
thank you,
philipp
keith chapman schrieb:
can u post the schema for the operation getString please.
Thanks,
Keith.
On 7/11/07, *Philipp Leitner* < [EMAIL
Hi all,
I have a service deployed with Axis2 with a couple of operations in it.
As it is default the service has 3 bindings, SOAP1.1, SOAP1.2 and HTTP
(REST).
Now I am trying to invoke this service using WSDL2java generated stubs.
I use
java -cp $CP org.apache.axis2.wsdl.WSDL2Java -d xmlbea
ublic XMLStreamReader getReader() throws XMLStreamException {
// not implemented since I figured that I don't need this method
return null;
}
}
/philipp
Philipp Leitner wrote:
Still having problems with that ... as you suggested I changed my AXIOM
processing and created a DataS
k/modules/axiom/modules/axiom-tests/src/test/java/org/apache/axiom/om/impl/llom/OMSourcedElementTest.java
thanks,
dims
On 7/2/07, Philipp Leitner <[EMAIL PROTECTED]> wrote:
OK, so it actually is that much quicker to use XMLStreamWriter and
writeStartElement(), writeEndElement() instead of
mWriter and you can write
out the xml directly to the output stream. On the other side, you can
get a XMLStreamReader using getXMLStreamReaderWithoutCaching on the
returned OMElement. using that you can read whatever pieces you need
from the response.
thanks,
dims
On 7/2/07, Philipp Leitner &l
perfomance gets into the generated code :)
thanks,
dims
On 7/2/07, Philipp Leitner <[EMAIL PROTECTED]> wrote:
Hi list,
I have a question rg. performance of the ServiceClient compared to the
OperationClient interface.
Personally, I would expect the performance* to be roughly the same for
both in
Hi list,
I have a question rg. performance of the ServiceClient compared to the
OperationClient interface.
Personally, I would expect the performance* to be roughly the same for
both interfaces since ServiceClient is just a more convenient wrapper
for simple tasks.
But now I have measured
Well, in my opinion very few of the typical 'Programmable Web' REST
interfaces (see for instance Flickr or Google) actually support REST,
but only what Anne calls POX over HTTP. To me (and I know that most will
disagree) the REST architecure is a little bit unpractical for many
applications (se
ted contains methods to add the HTTPHeader. For the
client it will be just another parameter passed into the operation.
The stub will retrive this parameter and stick it in as a HTTP header.
But there is no easy method such as above to retrive an HTTP response
header.
Thanks,
Keith.
On 5/29/
Hi all,
I have two question on the Axis2 client-side API:
I know that there are quite simple convenience methods for adding SOAP
header fields when using the client-side API (like
ServiceClient.addStringHeader(...) ), but is it also possible to get a
map or so of the headers that the /respons
You are not missing SchemaTypeSystem, but rather
schemaorg_apache_xmlbeans.system.sCBF8B98FA2E75865F9C83C43E1056B1A.TypeSystemHolder
. This is a file that gets generated by XMLBeans when it compiles XML
Schemata. You have to add all class files in the directory
"schemaorg_apache_xmlbeans" (they
Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117
Philipp Leitner wrote:
> Hi all,
>
> I just did a few experiements with an Axis2 service that I
deployed. I
> am using the doc/wrapped style, and have an operation that looks
> somet
sulting
http://www.sosnoski.com - http://www.sosnoski.co.nz
Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117
Philipp Leitner wrote:
Hi all,
I just did a few experiements with an Axis2 service that I deployed.
I am using the doc/wrapped style, and have an operation that looks
someth
will just concatenate the parameters and return them as
String.
Now I discovered that a SOAP request like this
14
Sperrgasse
Philipp Leitner
111
bears a different result then a request like
Sperrgasse
14
111
Philipp Leitner
(note the different order of the parameters).
Meanwhile
. MESSAGE_TYPE)
Thanks,
Keith.
On 4/16/07, *Philipp Leitner* <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
I am currently at version 1.1.1 . Do you think that I should upgrade to
a more recent version?
/philipp
keith chapman schrieb:
you are using the nightlies or the 1.2 Release
candidate.
Hope I answered your question...
See comments inline
On 4/16/07, *Philipp Leitner* <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
Hi folks,
I am wondering if there is support for REST over HTTP GET for Java
Hi folks,
I am wondering if there is support for REST over HTTP GET for Java
clients in Axis2?
I know that there is the configuration parameter
Constants.Configuration.ENABLE_REST_THROUGH_GET , but so far I could
not make it work.
I tried something like
Options options = new Options();
I think what Anne wanted to say was not so much that it is not
/possible/ to use SOAP to exchange Swing components (I see no general
problem with that), but that it frankly is against the idea of Web
Services to mis-use it like a distributed object middleware. There might
be much better (read:
ere to put the
changes so that they are 'semantically equivalent'. I daresay this is in
general impossible.
/philipp
Anil VVNN schrieb:
I couldn't able to find the solution yet. Could somebody shed light on this.
Thanks.
Philipp Leitner-2 wrote:
Hmm, I might be wrong, but I th
ects of complex types are still writing to "com.myprj.webservice"
folder.
Did I miss anything. Thanks.
Philipp Leitner-2 wrote:
The thing is, you should let these files be generated into a /different/
package :-)
Try
This should do the trick.
/philipp
Anil VVNN schrieb:
Phili
ransporter ) created by wsdl2java, so I did but when I
run wsdl2java again, it creates new wrapper objects of Transporter and
ABCTransporter and I loose my changes.
Any ideas how would I do to not to override these wrapper objects. Thanks.
Philipp Leitner-2 wrote:
you should pass a target
you should pass a target package as argument to wsdl2java to prevent it
from overriding existing source files.
/philipp
Anil VVNN schrieb:
Hi,
Any option to not to override files if they are already present. As I have
modified few classes (wrapper objects of complex types) and skeleton code.
binding and SOAP 1.2.
With best regards
From
Vikas R. Khengare
- Original Message -
From: "Philipp Leitner" <[EMAIL PROTECTED]>
To:
Sent: Tuesday, April 10, 2007 4:58 PM
Subject: Re: why 3 different tags present in WSDL file?
you don't "need" thre
you don't "need" three different bindings, but these examples provide
bindings for the 3 most common WS bindings. 1 is the standard SOAP
binding, 2 is a SOAP 1.2 (hence the "12") binding, and three is a
REST-style binding.
/philipp
Vikas schrieb:
Hi Friends,
Axis2 provides some sample code
what do you mean with "turn my xml into DOM" ? The Document Object Model
(if this the meaning of DOM that you are referring to, since there are a
few different ones) is just one possibility to represent XML, and afaik
not one used by Axis. I guess what you mean with "DOM" is actually Axiom.
If
;. :-)
As my service takes an complex type element as input, I need to pass
SOAPElement and to receive SOAPElement. I don't know how to fill SOAPElement. I
will try to use XFire for the client.
Thank you very much for your help,
Milan
- Original Message
From: Philipp Leitne
most probably you are missing the axiom jar in the classpath when
running your servlet. try to copy the Axis2 jars into the "lib"
directory of your application server.
/philipp
Vikas schrieb:
Hi Friends,
I have written a simple web service which returns "Hello World" string
using AXIOM. I
/philipp
Christian Poecher schrieb:
Philipp Leitner schrieb:
There's an XML compressor called XMill around since 1999
(http://sourceforge.net/projects/xmill).
Interessting! Does anyone have experience in combining Axis and XMill?
Cheers,
There's an XML compressor called XMill around since 1999
(http://sourceforge.net/projects/xmill).
/philipp
Xinjun Chen schrieb:
Differential encoding indeed has better performance. But it is not
really compressing SOAP message. Instead, it reduces both payload data
and overhead in the SOAP me
Although I have to confess that I lack any idea of what you mean by
"takes an XSD element and returns an XSD element"* I think that the
easiest way of testing a Web Service is to create client stubs using
wsdl2java (comes along with your Axis2 distribution) and use this stubs
to test the servic
if it is just a small chunk of binary data you can think about transferring it
as byte[] ? Axis2 wil then encode it as xsd:base64binary, and you can stay
completely POJO ...
/philipp
Original-Nachricht
Datum: Thu, 29 Mar 2007 13:39:58 +0100
Von: "Raghupathy, Gurumoorthy" <[EMA
://issues.apache.org/jira/browse/AXIS2-2408
Wait and see...
Philipp Leitner-2 wrote:
Hi all,
let me apologize in advance for asking a very simple question on this
list:
I am using the Axis2 ServiceClient interface to do a blocking IN-OUT
call to a Web Service:
ServiceClient sender = new
Marcos Vilela
msn: [EMAIL PROTECTED]
googletalk: [EMAIL PROTECTED]
Philipp Leitner-2 wrote:
Hmm, I currently have a similar problem. I would be interested in what
communication style you are using in your client (assuming you are
speaking from an Axis2 client). Do you use the "sendRe
ment. Probably there are other ways to do
the client. I'm looking to use OMElement.
Do you have any suggest?
thanks and best regards
Marcos Vilela
Philipp Leitner-2 wrote:
Returning an array or a list of objects is surely the more natural way
to go, but may in some cases inflict a
Returning an array or a list of objects is surely the more natural way
to go, but may in some cases inflict a performance penalty.
I would go for the list of objects, and only if you run into severe
performance troubles go for optimizing the solution.
/philipp
Marcos Vilela schrieb:
Hello,
Hi all,
let me apologize in advance for asking a very simple question on this list:
I am using the Axis2 ServiceClient interface to do a blocking IN-OUT
call to a Web Service:
ServiceClient sender = new ServiceClient();
sender.setOptions(axis2Options);
OMElement result = sender.sendRec
63 matches
Mail list logo
