unregister
We need to do firewall tunneling via a proxy server. This means we need
to tell the client what the proxy address is, in addition to the actual
server endpoint. We can't set it on the jvm because we need to change it
dynamically at runtime.
Does anyone know how to do this using Axis?
Thanks,
at the attached file.
And I have only engaged the module in my test service...
An idea ?
Thanks.
--
Ephemeris Lappis
De : Masin, Valerie [mailto:[EMAIL PROTECTED]
Envoyé : samedi 28 avril 2007 23:45
À : axis-user@ws.apache.org
Objet : RE: [AXIS2] Module
Hi,
I am the only one in my group doing web services. The others would like
to get on board in the most efficient way so we are looking for books
and/or articles that will explain the concepts starting at a high level
but moving quickly down to code. Any suggestions?
Thanks, Valerie
Make sure you haven't declared the module in your conf/axis2.xml
From: Ephemeris Lappis [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 26, 2007 2:30 AM
To: axis-user@ws.apache.org
Subject: [AXIS2] Module configuration and flows
Hello.
I'm trying to make
, it appears that it was
used to tell the app where to put the generated wsdl (I am taking over
someone else's code; that's why I am not sure) and that is probably
obsolete in Axis2
From: Masin, Valerie [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 24, 2007 5:11 PM
I am switching from Axis1 to Axis2. In Axis1 I have code that uses these
constants. However there don't seem to be Axis2 equivalents for them.
org.apache.axis.Constants.MC_SERVLET_ENDPOINT_CONTEXT
org.apache.axis.MessageContext.WSDLGEN_SERV_LOC_URL
Here's how I am trying to use the first
The instructions for setting up a module with handlers says to edit the
services.xml file. However, this is a generated file that gets
overwritten each time you run wsdl2java. Although it is true that I can
squirrel away the file I have edited, if I change my wsdl I will want to
regenerate the
To really know that you are using MTOM you should be looking at your soap
messages with tcpmon. If you are not using MTOM but are using base64Binary your
soap will look something like this. Notice the ns1:document tag contains an
encoded document directly embedded.
POST
Axis2-1.1.1
Thanks, Valerie
-Original Message-
From: Deepal Jayasinghe [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 19, 2007 12:43 AM
To: axis-user@ws.apache.org
Subject: Re: [Axis2] IllegalStateException from
axis2-web/Error/error500.jsp
Hi Masin,
What is the Axis2 version ?
On 4/18/07, Masin, Valerie [EMAIL PROTECTED] wrote:
I believe it is setProperty(), not set() on the options object
-Original Message-
From: Michele Amoretti [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 18, 2007 1:24 PM
To: axis-user@ws.apache.org
Subject: using MTOM in a AXIOM-based
My customer gets an error returned when they call my service. The error
is generated by Axis because they passed a soap message that does not
conform to the schema. But I don't see any errors in my logs. If I turn
up the logging level to show Debug messages then I see the message that
the customer
/stack trace.
thanks,
dims
On 4/19/07, Masin, Valerie [EMAIL PROTECTED] wrote:
My customer gets an error returned when they call my service. The
error is generated by Axis because they passed a soap message that
does not conform to the schema. But I don't see any errors in my logs.
If I
...
--
Ephemeris Lappis
De : Masin, Valerie [mailto:[EMAIL PROTECTED]
Envoyé : mardi 17 avril 2007 19:56
À : axis-user@ws.apache.org
Objet : RE: [Axis2] Attachment on client using generated stub
I'm no expert so I don't know if I am answering your question exactly
De : Masin, Valerie [mailto:[EMAIL PROTECTED]
Envoyé : mercredi 18 avril 2007 16:36
À : axis-user@ws.apache.org
Objet : RE: [Axis2] Attachment on client using generated stub
I realize that my wsdl showed xmime:base64Binary where presumably xmime is
http://www.w3.org
I believe it is setProperty(), not set() on the options object
-Original Message-
From: Michele Amoretti [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 18, 2007 1:24 PM
To: axis-user@ws.apache.org
Subject: using MTOM in a AXIOM-based WS
Hello,
I am trying to create a new version of
...
Thanks for your help...
--
Ephemeris Lappis
De : Masin, Valerie [mailto:[EMAIL PROTECTED]
Envoyé : mercredi 18 avril 2007 20:17
À : axis-user@ws.apache.org
Objet : RE: [Axis2] Attachment on client using generated stub
If you can enable MTOM
Every time I get a 500 error on the webserver which goes to the axis
error500.jsp I then get an IllegalStateException. Do I have to set
something up that I don't know about?
Here's what appears in my webserver's error log.
[18/Apr/2007:15:30:39] failure (21241): for host xx.xx.xx.xx trying to
I have no idea if this helps but we had trouble with large docs using Sun
Webserver and the solution was to set this on the client:
stub._getServiceClient().getOptions().setProperty(HTTPConstants.CHUNKED,
Constants.VALUE_FALSE);
From: Jorge Fernandez
I'm no expert so I don't know if I am answering your question exactly,
but I send attachments this way.
In my wsdl I have something like this:
wsdl:types
schema xmlns=http://www.w3.org/2001/XMLSchema; ...
element name=importDocument
complexType
sequence
element name=name
as references for
array of DataHandlers
Sounds like a bug to me... Please log a JIRA.. If possible include your
WSDL and a test case...
Thilina
On 4/12/07, Masin, Valerie [EMAIL PROTECTED] wrote:
One of my datatypes is an array of DataHandlers (DataHandler[]). (I
got the wsdl to generate
Hello,
I need to have some of my .class files live in the web-inf/classes
directory since other non-axis apps use them. I would prefer to not have
to put some of them there and the rest in the .aar so I would like to
put them all in web-inf/classes. I tried not using the .aar at all but
couldn't
One of my datatypes is an array of DataHandlers (DataHandler[]). (I got
the wsdl to generate this by setting my base64Binary's maxOccurs to
unbounded)
element name=documents nillable=false minOccurs=1
maxOccurs=unbounded type=base64Binary/
When I use MTOM I had expected to see each of these
Voila, you have answered my question. I didn't realize I needed to
create a directory with my servicename in the services directory with
the meta-inf under it. Thanks
-Original Message-
From: Alistair Young [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 11, 2007 4:07 PM
To:
:[EMAIL PROTECTED]
Sent: Wednesday, March 28, 2007 3:12 AM
To: axis-user@ws.apache.org
Subject: Re: Axis2 not putting binary attachment on the wire
Please log a Jira with enough information (a test case would be great)
to reproduce this..
thanks,
Thilina
On 3/28/07, Masin, Valerie [EMAIL PROTECTED
Can you tell me which of these bindings in Axis2 is JAXB? Thanks
C:\%AXIS2_HOME%/bin/wsdl2java
...
-d databinding Valid databinding(s) are adb, xmlbeans, jibx,
jaxme and jaxbri (Default: adb).
-Original Message-
From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]
Sent: Monday,
Hello,
I don't pretend to know a thing about xmlbeans but I was thinking I
might use them as my databinding when I discovered that adb doesn't
handle default values in the schema, and the castor databinding isn't
available in axis2. However, when I generate the code from wsdl2java
using xmlbeans
My understanding (from reading about this somewhere) is when MTOM
attachments are viewed with SOAPMonitor they show up embedded (and
encoded) directly in the soap message. Then when they are MTOMed (ie
optimized) just before sending, that data is rearranged into the
multipart mime where the binary
)
to reproduce this..
thanks,
Thilina
On 3/28/07, Masin, Valerie [EMAIL PROTECTED] wrote:
No it is not working fine with mtom, there is no data attached. Where
you said Hope you had your binary data here... there was no data.
There was just the 0.
I show the soapmonitor output to show that there had
FYI: You can get the skeleton interfaces with the command line wsdl2java
using the -ssi flag. The default is off.
-Original Message-
From: david2 [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 28, 2007 3:32 PM
To: axis-user@ws.apache.org
Subject: Re: Ant wsdl2java command line
My webservice returns a binary document which I declare in my wsdl as
base64Binary. Using SOAPMonitor I see my document in the returned soap
message. However, tcpmon shows that the document is empty. I have tried
this both with and without MTOM.
Without MTOM here is the soap from SOAPMonitor...
... Sounds like a bug to me.. Please log a JIRA with more details..
Some source code would be actually better...
Then in order to get through this you can try enablingMTOM in your
Axis2.xml..
Thanks,
Thilina
On 3/28/07, Masin, Valerie [EMAIL PROTECTED] wrote:
My webservice returns a binary
...
Then in order to get through this you can try enablingMTOM in your
Axis2.xml..
Thanks,
Thilina
On 3/28/07, Masin, Valerie [EMAIL PROTECTED] wrote:
My webservice returns a binary document which I declare in my wsdl as
base64Binary. Using SOAPMonitor I see my document in the returned
33 matches
Mail list logo
