Hi Jennifer and Sumit,
thanks for your advise: this is exactly what I have already suspected. So my
question shifts a little bit : if a client wants to issue several requests
concurrently, is it sufficient to create a separate Call object for each
thread ? HAs anybody tried that before ?
Thanks,
Title: RE: Character Encoding other than UTF-8 with SwA
Hallo Peter,
I have just done a very ugly quick fix by rebuilding
Axis with changed encoding constants in the below
mentionend classes and it worked correctly.
I am quite new to Axis therefore I don't know how a
more configurable
Daniel,
I assume you are saying that process the incoming request in a Handler
(pre-process) and insert the SOAP Header in the Message Context and then
access the Message Context in the end point or the service implementation.
To start with my question was exactly the same. How do I access SOAP
I've the same problem using tomcat, but i think it depends on my port of java to OpenVMS. I've no solution at this time.
On Mon, 2003-06-30 at 20:57, Jackson, Jen (CCI-Atlanta) wrote:
I'm running an axis client under tomcat testing some soap calls, and I"m having an extremely high CPU usage t
Santosh,
After you extracted the header info you can store the stuff you need in
message context properties.
These properties are available everywhere where you can access the message
context.
Hope this helps.
Cheers, Dan
On Monday 30 June 2003 22:34, [EMAIL PROTECTED] wrote:
> Albert,
>
> I ha
Hi all,
I should thank Toshi for his help in getting my test
ejb to work as webservice. In this, I used tcpmon to
know the SOAP request and response listening in a
different port and the webserver running in a
different port. So, always my TargetEndpointAddress
points to the listening port.
OK,
Hi,
I am trying to make a web service which takes XML Document as Input and
after some manipulation .XML Document will return back to user.
But axis is not allowing in doing this when i am giving java2wsdl command it
is saying that XML Document should have default
Constructor.Which is not supp
Dear all,
I am new to Axis. Now I have a question related SOAP Header element in Axis. As we
know, we can use WSDL2Java tool to generate Java classes based on existing WSDL stuff.
However, we I add SOAP Header element, say authentication info, I cannot see any
difference b/t header existing and
Hi,
When I
try to deploy a WSDD file in JBoss 3.0.4, AXIS 1.1, I am getting the following
error,
Error
for /PublishWS/services/AdminService
java.lang.LinkageError: loader constraints violated
when linking javax/xml/namespace/QName class
Has
anybody ran into this issue. What is the s
Hi,
When I
try to deploy a WSDD file in JBoss 3.0.4, AXIS 1.1, I am getting the following
error,
Error
for /PublishWS/services/AdminService
java.lang.LinkageError: loader constraints violated
when linking javax/xml/namespace/QName class
Has
anybody ran into this issue. What is the s
GLUE is very easy to use. The standard edition is
free for commercial use.
Anne
- Original Message -
From:
Jan Agermose
To: [EMAIL PROTECTED]
Sent: Monday, June 30, 2003 4:38 PM
Subject: Axis vs Glue
Does anyone have any pros/cons on the two? If
this is an all
You don't *need* to define the SOAP faults, but you
*should* do so if you want to ba able to support non-Java clients. If you don't
define the faults, Axis will simply return the Java exception, and a VB.NET
client has no idea what to do with a Java exception.
You define the SOAP fault
in
Thanks for the analysis.
However, has anyone tested AXIS with large messages (> 0.1 MB)?
It seems that RPC data argument streaming has larger impact on the performance when
you have large size messages because it allows overlap between
AXIS communication and deserialization that would otherwise
Thanks for the analysis.
However, has anyone tested AXIS with large messages (> 0.1 MB)?
It seems that RPC data argument streaming has larger impact on the performance when
you have large size messages because it allows overlap between
AXIS communication and deserialization that would otherwise
Is there any plans to implement WS-Security as part of AXIS 1.2?
I believe the OASIS WS-Security spec will be a committee spec
next month?
"Kellogg, Richard" <[EMAIL PROTECTED]> wrote:
Agreed WSE might make it into the .NET Framework. Ultimately, I feel the time frame for that is a year away u
Is there any plans to implement WS-Security as part of AXIS 1.2?
I believe the OASIS WS-Security spec will be a committee spec
next month?
"Kellogg, Richard" <[EMAIL PROTECTED]> wrote:
Agreed WSE might make it into the .NET Framework. Ultimately, I feel the time frame for that is a year away un
I can't answer any empirical performance questions. Here's what I can say.
When you talk about document-style vs. RPC-style, I'm assuming you're talking
about the following, as specified in the WSDL document:
* document binding style combined with literal use vs.
* RPC binding style combined with
Agreed
WSE might make it into the .NET Framework. Ultimately, I feel the time
frame for that is a year away unfortunately. They just finalized
1.1.
According to the web site:
As these advancements gain broad adoption
and mature, they will be absorbed into the .NET Framework and Visual St
Yes, I used on the .NET Framework 1.1 the .NET WSE package which comes
with WS-Security support. Inspecting the WS-Security headers produced
by the .NET WSE, it was similar to the OASIS WS Security specification.
I only tested PasswordToken however which is simple enough. WSE is
supposedly goin
Yes, I used on the .NET Framework 1.1 the .NET WSE package which comes
with WS-Security support. Inspecting the WS-Security headers produced
by the .NET WSE, it was similar to the OASIS WS Security specification.
I only tested PasswordToken however which is simple enough. WSE is
supposedly going
Hi,
How can I tell the server not to send response with "Transfer-Encoding:
chunked".
I deployed AXIS webservice on Tomcat 4.1.24 server. When I send the message
the response comes back is chunked.
Thanks
-Chandra Talluri
NetNumber.com, Inc.
650 Suffolk Street
Suite 307
Lowell, MA 01854
Tel: 9
I am not a 100% sure, but as far as I understand it now, you don't need to
specify the SOAP Faults in your xsd, these are SOAP specific, not part of
your response message.
r
Tony Opatha wrote:
>Therefore you need to define a fault message for each of your
exceptions, and then tell >Axi
Praveen,
When you use session management in Web Services, especially with WSDL(1.1),
SOAP(1.1), then you are on your own, because there is nothing in specs about
Session Management.
Although HTTP Session is supported by both .NET and AXIS. See closely the
process of generation of deployment des
Hello,
I wrote a simple web service client in .NET 1.1 (using Visual Studio .NET 2003)
that consumed a document-style SOAP Web Service in AXIS 1.1. The document
size that was transmitted ranged from 0.1 - 0.5 MB.
I also tested a simple web service client in .NET 1.1 that consumed a RPC-sty;e S
Hello,
I wrote a simple web service client in .NET 1.1 (using Visual Studio .NET 2003)
that consumed a document-style SOAP Web Service in AXIS 1.1. The document
size that was transmitted ranged from 0.1 - 0.5 MB.
I also tested a simple web service client in .NET 1.1 that consumed a RPC-sty;e SO
Does anyone have any pros/cons on the two? If this
is an allowed question :-) Glue looks a bit simpler to get started with - might
just be better documented :-D but then the prof. edition is somewhat
expensive...
Jan Agermose
Albert,
I have indicated that one can write a AXIS Handler, but that is
dis-connected processing. i.e. Handler is invoked after or before the end
point is called, hence the SOAP header or Body or Message viewing ability is
part of pre-processing or post processing, which is not what is intended.
The
basic web services includes with the Microsoft .NET Framework 1.1 does NOT
include support for WS-Security. I believe the the recently announced
Web
Services Enhancements for Microsoft .NET does include support. Please see
http://microsoft.com/downloads/details.aspx?FamilyId=06255A94-
.NET 1.1 Web services supports WS-Security which means that you also
have the option of passing from AXIS client a WS-Security
as part of the SOAP Security header.
However, AXIS does not support the ability for applications to set the Password
token and add it to the SOAP header.
I believe IB
.NET 1.1 Web services supports WS-Security which means that you also
have the option of passing from AXIS client a WS-Security
as part of the SOAP Security header.
However, AXIS does not support the ability for applications to set the Password
token and add it to the SOAP header.
I believe IBM
>Therefore you need to define a fault message for each of your exceptions, and then tell >Axis to map the exceptions to the faults accordingly.
So, this means that AXIS supports application-specific Faults for both document-style
and RPC-style so long as the .xsd schema for the custom Fault mess
>Therefore you need to define a fault message for each of your exceptions, and then tell >Axis to map the exceptions to the faults accordingly.
So, this means that AXIS supports application-specific Faults for both document-style
and RPC-style so long as the .xsd schema for the custom Fault messa
Where can I find some samples related to session
management. I looked at the samples shipped with Axis but they didn't have many
samples related to session management.
Praveen
I'm running an axis client under tomcat testing some soap calls, and I"m having an
extremely high CPU usage that is coming from the tomcat
class org.apache.tomcat.util.net.DefaultServerSocketFactory.acceptSocket, up to
70-80%. Has anyone run into this problem? I've tested on both tomcat 331 and
Is there any way to implement session management in
the soap services w/o using any axis specific classes.
The requirement is that all my soap services should
be independent of the soap tool kit.
To get the access to HttpSession, I think I need to
use axis specific classes (org.apache.axis.
When I hit http://localhost:8080/axis, I get an
option "View the list of deployed Web services".
In looking at the AxisServlet code, this list is
returned as an iteration of ServiceDesc objects.
Can I write my own Axis client program to get
this list myself? If so, how?
(I'm aware of the "list"
I am quoting my own message.
http://marc.theaimsgroup.com/?l=axis-user&m=105650439419684&w=2
this should work.
Quoting [EMAIL PROTECTED]:
> All,
>
> I have recently started to use AXIS and need help on How to access the SOAP
> Message or SOAP body or SOAP Header, with which a end point was inv
I am sending a request that contains an inout param called docID. The
response contains the docID, but it also contains an attachment.
1.What response type needs to be set for this? If i set it as anything other
that the inout param I seem to get cast errors.
2. I can retrieve the attachment par
All,
I have recently started to use AXIS and need help on How to access the SOAP
Message or SOAP body or SOAP Header, with which a end point was invoked in
the first place.
e.g. I have a interface definition in terms of an WSDL. How do I access the
actual SOAP message delivered on the wire in the
To put it precisely, the ultimate solution is attachment.
Before that, i used to Gzip the payload, but it does not scale too well.
Quoting "Agarwal, Naresh" <[EMAIL PROTECTED]>:
> Hi
>
> Does AXIS support sending SOAP payload with size more than 2 MB?
> If not, what is the way to exchange SOA
Never mind. I seem to have done something to web.xml. When I restored it,
the problem went away.
Thanks anyway.
Ralph
> -Original Message-
> From: LeVan,Ralph [mailto:[EMAIL PROTECTED]
> Sent: Monday, June 30, 2003 9:37 AM
> To: Axis Users Mailing List (E-mail)
> Subject: Error using A
When I run AdminClient on the deploy.wsdd that WSDL2Java generated, I get
the error:
Processing file deploy.wsdd
Exception:: (400)HTTP method POST is not supported by this URL
I don't see how I can control this behavior.
I'm using Axis 1.1 and Tomcat 4.1
Any help would be appreciated.
Thanks!
I need some help with regard to deploying my service on apache tomcat with axis.
I have to create a process that takes raw xml from axis and parses the message
appropriately as well as calls some services in a separate class file based on the
message. Now I want to deploy the services such that i
Hello Thomas,
You will have to call 'clearOperation' method between requests to use
the same call object. You can do something like this:
Service service = new Service();
Call call = (Call) service.createCall();
call.setTargetEndpointAddress(url);
call.setOperationName(new QName("urn"
Hi Thomas. My understanding is that the Call object is a stateful object, containing
the soap request and response. The Serializer and Deserializers contains the request
and response data within the call object. So I would say you need to create a call
per soap request.
Anyone else?
Jennife
Hi everbody,
I have a question regarding the org.apache.axis.client.Call class. Is it
possible that a client creates only one Call instance and than issues
serveral requests through this object concurrently or is this kind of usage
illegal ?
Thanks,
Thomas
I think we were using a
slightly older version of JBOSS, cant remember the exact version. We tried
replacing the old Axis jars with the new and just running like that, but we
would get 'method does not exist' errors at JBOSS startup. Not exactly
sure as to the cause of this.
-Orig
I tried Axis rc1 on JBOSS
3.2.4,
All I did was, changed the
classpath to use the new AXIS.jar(s), and it worked fine.
May be I should look close,
Thanks
Balaji .T
-Original Message-From: Jim Poulsen
[mailto:[EMAIL PROTECTED]Sent: Monday, June 30, 2003 8:03
AMTo: '[EMAIL P
This was allso my first idea, but in the Servlet it's running fine. But i will not loose it out of eyes.
thanks
Harry
On Mon, 2003-06-30 at 13:35, Keith Hatton wrote:
Hi Harald,
Do you think this might be a security problem? I've had problems loading native code in Tomcat befor
You will probably have to
'modify' the standard JBOSS installation kit to get Axis 1.1 to work with
it. It seems that there are some issues if you simply install JBOSS (whose
kit includes an old version of JBOSS) and drop an Axis web services application
based on Axis 1.1 on top of it.
As long as the server supports
servlets, AXIS 1.1 is a good kid.
It should work with all these
servers.
-Balaji.T
-Original Message-From: Agarwal, Naresh
[mailto:[EMAIL PROTECTED]Sent: Monday, June 30, 2003 3:34
AMTo: Axis (E-mail)Subject: Application/Web Servers
support
Hi
Harald,
Do you
think this might be a security problem? I've had problems loading native code in
Tomcat before.
You
might try making sure your JNIDate class is loaded by the system classloader,
rather than the application classloader. I'm not familiar with the versions of
Hy everybody!
I try to use JNI within a Axis-Service. I try since weeks to bring it to work, but my result is every time the same:
soapenv:Server.userException
java.lang.reflect.InvocationTargetException
my enviroment:
Linux:
Hi
Does AXIS support sending SOAP
payload with size more than 2 MB?
If not, what is the way to
exchange SOAP messages of size bigger than 2 MB -
attachments?
thanks &
regards,
Naresh
Agarwal
hi,
I need to use Mail transport with Axis 1.1. The Java doc is present in
Axis 1.1 Final but not the classes in the Jar files and sources.
Why ?
Thanks for your help.
Didier
Post-scriptum La Poste
Ce message est confidentiel. Sous réserve de tout accord conclu par
écrit entre vous et La
Hi
Which of the following are supported by AXIS
1.1?
Apache Web Server
JBoss
IBM Web Sphere Application
Server
BEA Web logic
Sun One
IIS
thanks &
regards,
Naresh
Agarwal
56 matches
Mail list logo
