Hi,
We are using .NET client with Axis Java Service.
It is a simple test service having some methods for
mathematical calculations.
One of the method is returning int as response.
This is working fine with Axis Java Client.
Now the problem is with .NET client. As on client
side, we are getti
Thank you
Pedro Salgado
On 04/05/21 13:19, "Anne Thomas Manes" <[EMAIL PROTECTED]> wrote:
> This capability is built into the SOAP processing model -- no need to use a
> separate controller framework. You should use a handler chain to check
> authentication/authorization.
>
> Anne
>
> -
Yep :) you need to set the classloader in your code and invoke
java2wsdl (org.apache.axis.wsdl.Java2WSDL's main method) from your
code. If you run into problems, hop onto the axis-dev mailing list.
-- dims
On Fri, 4 Jun 2004 13:00:22 -0700, Sagar Pidaparthi
<[EMAIL PROTECTED]> wrote:
>
> I think
I think I understand better. Please confirm if the following is
correct:
Once the class loader is set to my class loader, java2wsdl command
internally invokes my Class loader and so it should be able to generate
wsdl for my classes.
Is this correct?
Regards
Sagar
-Original Message-
F
Thanks. I am new to Axis and so here is my understanding of your
message.
1. Write a class loader that uses my factory and loads the classes into
memory.
2. set the class loader to be my class loader using
ClassUtils.setClassLoader.
3. At run time, invoke the class loader to load all my cla
One way to do this is as follows...Write your own class loader for
your classes, then try to use ClassUtils.setClassLoader to set the
custom classloader and then invvoke java2wsdl as usual.
-- dims
On Fri, 4 Jun 2004 11:39:15 -0700, Sagar Pidaparthi
<[EMAIL PROTECTED]> wrote:
>
> Thanks for the
Thanks for the reply on customizing Java2WSDL. Here is a further
question.
I am assuming that java2wsdl instantiates a java object and introspects
the object and generates wsdl for this class. If this is true, my plan
is to customize java2wsdl and use a factory to instantiate my java
object and
see samples\integrationGuide\example1 and samples\integrationGuide\example2
- Original Message -
From: Sagar Pidaparthi <[EMAIL PROTECTED]>
Date: Fri, 4 Jun 2004 11:01:34 -0700
Subject: Customizinf java2wsdl
To: [EMAIL PROTECTED]
In the documentation I find a plug-in p
In the documentation I find a plug-in point for customizing
wsdl2java. Is it possible to customize java2wsdl?
sagar
Never mind. I got it working after some trial and error sequences of the
deployments.
I wish to convey my sincere appreciations for your support in this issue.
-Original Message-
From: Guha, Suteertha [IE] [mailto:[EMAIL PROTECTED]
Sent: Friday, June 04, 2004 12:57 PM
To: '[EMAIL PROTE
see the generated client-config.wsdd
On Fri, 4 Jun 2004 12:00:45 -0400, Jose M. Selman <[EMAIL PROTECTED]> wrote:
>
> Hi:
> I used org.apache.axis.client.AdminClient to register a client-side
> handler that takes care of Signing outgoing SOAP Envelopes. Everything is
> working smoothly :-
David Gandy wrote:
Hi,
I found out the reason for the "org.xml.sax.SAXException: No event
recorder inside element" error; it was down to having put streaming="on"
in my server-config.wsdd file (I believe this was part of the fix for
bug AXIS-1323).
I've done a build from the latest source snapshot
Yes, look at test\wsdl\jaxrpchandler\JAXRPCHandlerTestCase.java search
for ClientHandler
-- dims
- Original Message -
From: Jose M. Selman <[EMAIL PROTECTED]>
Date: Fri, 4 Jun 2004 10:17:52 -0400
Subject: Re: How to get the SOAP Envelope from msg Context without invocation
To: [EMAIL PROT
you hit the cause of the problem :) Yes, we will have to come up with
a flag for the dynamic client for the same thing.
-- dims
On Fri, 04 Jun 2004 15:28:41 +0100, Nils-Helge Garli
<[EMAIL PROTECTED]> wrote:
>
> I will do that. Just one small observation first. If I use the flag nowrapped="true"
I think you should try to use WSS4J's handlers. All the dirty work
regarding implementation of the OASIS specs for Web Services Security
is already taken care of in WSS4J:
-
http://ws.apache.org/ws-fx/wss4j/apidocs/org/apache/ws/axis/security/package-summary.html
- http://ws.apache.org/ws-fx/wss4
Thanks a lot. I am able to deploy and test successfully. I want to make a
WAR file out of these classes. I made a WAR file with a server-config.wsdd
under WEB-INF in WebLogic 8.1. I can see the service in the browser, but the
wsdl is not getting generated, and I see a 500 error on the URL :
http://
David,
Is it possible to file a bug report with sample code, that will help
me nail down and fix the problem.
thanks,
dims
On Fri, 4 Jun 2004 17:41:31 +0100, David Gandy <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I found out the reason for the "org.xml.sax.SAXException: No event
> recorder inside
Well, I am working on a project where I
plan to implement an Agent-based implementation for Web Services. It is my
advisor who wants me to avoid Tomcat reason being performance issues. I think
that exception could be due to some configuration settings on my laptop.
Perhaps, I must try that
It
looks pretty straight-forward. Is there any reason why you are not using
TomCat?
-Original Message-From: Sandeep
[mailto:[EMAIL PROTECTED]Sent: Friday, June 04, 2004 12:35
PMTo: [EMAIL PROTECTED]Subject: RE: processing
deploy.wsdd
Hi
John
Deploy.wsdd is as
Hi,
I found out the reason for the "org.xml.sax.SAXException: No event
recorder inside element" error; it was down to having put streaming="on"
in my server-config.wsdd file (I believe this was part of the fix for
bug AXIS-1323).
I've done a build from the latest source snapshot (having also got
Hi John
Deploy.wsdd is as follows
xmlns:java="http://xml.apache.org/axis/wsdd/providers/java">
This is from the samples directory coming
from userguide\example3 directory.
Thanks
Sandeep Advani
Grid Research Lab., Binghamton Univers
Please
post the deploy.wsdd file...
-Original Message-From: Sandeep
[mailto:[EMAIL PROTECTED]Sent: Friday, June 04, 2004 11:42
AMTo: [EMAIL PROTECTED]Subject: processing
deploy.wsdd
Hi
there,
I have been trying to use
AdminClient to run the deploy.wsdd files
Hi:
I used org.apache.axis.client.AdminClient to register a client-side
handler that takes care of Signing outgoing SOAP Envelopes. Everything is
working smoothly :-). I want to know though what the AdminClient does in
order to configure my webservice client to be used in a production
environme
Hi there,
I have been trying to use
AdminClient to run the deploy.wsdd files from the samples directory. In ths
process of doing so, I get an exception as
java -cp %classpath%
org.apache.axis.client.AdminClient
-lhttp://localhost:8080/axis/services/AdminService
deploy.wsdd
Proc
wjc> Here's a pretty good explanation of linger time and the TIME_WAIT
wjc> state.
Curious. In my original, there is a URL right after that. Here's
another try.
http://marc.theaimsgroup.com/?l=log4j-user&m=108326596313116&w=2
I will do that. Just one small observation first. If I use the flag nowrapped="true"
in the wsdl2java ant task, I get QNames that are similar to the ones I'm experiencing
with the dynamic client. Are there any ways to customize the parser options used by
the dynamic client?
Nils-H
- Origin
Hi,
I am using a messaging service. And i get the SOAPBodyElement in my service
method.now i want to validate this XML document against schema.
Any inputs on how do i validate the document...do i have to convert this
document to an InputSource and try to parse this source turning on the
valida
Dims:
I did, but that example uses a service with no parameters. In my case I
need to include a String as a parameter. I have been trying to use XMLUtils
to generate the SOAP Body (with one parameter) myself, just like the sample,
but I haven't been able to get it right. I appreciate your help.
Is it possible to programatically set
client-side handlers? That way my problem would be solved.
Cheers,
Jose M. Selman
- Original Message -
From:
Dhanush
Gopinath
To: [EMAIL PROTECTED]
Sent: Thursday, June 03, 2004 11:50
PM
Subject: Re: How to get the SO
Nils-Helge,
Please try a nightly build, if you still see the problem, open up a bug report.
thanks,
dims
On Fri, 04 Jun 2004 14:41:43 +0100, Nils-Helge Garli
<[EMAIL PROTECTED]> wrote:
>
> The correct WSDL should be:
>
> http://www.myns.com/ws";>
>
> targetNamespace="http://www.myns.
The correct WSDL should be:
http://www.myns.com/ws";>
http://www.myns.com/ws";>
- Original Message -
From: "Nils-Helge Garli" <[EMAIL PROTECTED]>
Date: Fri, 04 Jun 2004 14:34:26 +0100
To: [EMAIL PROTECTED]
Subject: RE: Dynamic client/WSDL problems
> Thanks for the quick answer.
Thanks for the quick answer.
The top of the WSDL document looks like this:
http://www.myns.com/ws";>
http://www.superoffice.net/ws";>
The WSDL file has been automatically generated by .NET, and since I'm not the "owner"
of the WSDL file, I can't modify it easily.
Sincererly,
Nils-Helge
The Microsoft Reporting Services uses an application-defined mechanism to
manage sessions (i.e., specifying the SessionID in a header block), so it
doesn't depend on the Web service implementations to use compatible session
management mechanisms. It should work just fine as long as you implement
su
The Microsoft Reporting Services uses an application-defined mechanism to
manage sessions (i.e., specifying the SessionID in a header block), so it
doesn't depend on the Web service implementations to use compatible session
management mechanisms. It should work just fine as long as you implement
su
One question: what is the value of the elementFormDefault attribute?
If it's "qualified", then you are correct that the proper QName for the
element is {http://www.myns.com}departmentId. But if it's "unqualified" (or
not specified), then the element is a local element, and it has no QName --
only
One question: what is the value of the elementFormDefault attribute?
If it's "qualified", then you are correct that the proper QName for the
element is {http://www.myns.com}departmentId. But if it's "unqualified" (or
not specified), then the element is a local element, and it has no QName --
only
please take a look at the samples/security/* for an example that does xml-dsig.
thanks,
dims
- Original Message -
From: Dhanush Gopinath <[EMAIL PROTECTED]>
Date: Fri, 4 Jun 2004 09:20:21 +0530
Subject: Re: How to get the SOAP Envelope from msg Context without invocatio
n
To: [E
Thanks... I appreciate all the help! I will look into a deployment
descriptor.
I did read an article last night that stated: "There are not yet any
solutions to ensure interoperability in terms of session management between
Axis and other Web Service implementations." This is from an article (
David,
See of this patch
(http://marc.theaimsgroup.com/?l=axis-dev&m=108635075801815&w=2) fixes
your problem.
thanks,
dims
On Fri, 4 Jun 2004 10:24:40 +0100, David Gandy <[EMAIL PROTECTED]> wrote:
>
> I should probably have said before that the error is ocurring in an
> Applet that is using SOA
Hi!
I have a problem trying to access a .NET web service with the Axis (1.2 beta) dynamic
proxy client. The QNames of the WSDL are parsed incorrectly. For instance, parsing
this part (from the WSDL file):
results in a qname like:
{http://www.myns.com}>GetDepartmentPhon
The following section:
ComputedKey <-> ComputedKeyOpenEnum <-> ComputedKeyEnum combination
below throws off wsdl2java. Please open a bug report in jira.
thanks,
dims
- Original Message -
From: Asanka Priyanjitih <[EM
Takenori,
This is a good point. I have checked that and the Reference.cs has the
following.
///
[System.Xml.Serialization.SoapTypeAttribute("order",
"http://com.express_scripts.sds.demo.ejb/randy/test";)]
public class order {
///
public order_detail detail;
/
Hi Team
I also face same thing, I don’t know
what a problem is.
Please help to us.
G J Asanka Priyanjith
-Original Message-
From: Malinda
[mailto:[EMAIL PROTECTED]]
Sent: Friday, June 04, 2004 3:44 PM
To: [EMAIL PROTECTED]
Subject: wsdl2java - got t
You need a deployment descriptor on the client side if you want to configure
the client to use JAX-RPC handlers or to use a custom serializer.
-Original Message-
From: Dorner Thomas [mailto:[EMAIL PROTECTED]
Sent: Friday, June 04, 2004 3:21 AM
To: '[EMAIL PROTECTED]'
Subject: AW: Axis cli
You need a deployment descriptor on the client side if you want to configure
the client to use JAX-RPC handlers or to use a custom serializer.
-Original Message-
From: Dorner Thomas [mailto:[EMAIL PROTECTED]
Sent: Friday, June 04, 2004 3:21 AM
To: '[EMAIL PROTECTED]'
Subject: AW: Axis cli
Suteertha,
I suggest that you define two separate elements -- one for input and one for
output. (Right now Axis interprets your document as an in/out parameter.)
Like this:
Anne
-Original Message-
From: Guha, Suteertha [IE] [mailto:[EMAIL PR
Suteertha,
I suggest that you define two separate elements -- one for input and one for
output. (Right now Axis interprets your document as an in/out parameter.)
Like this:
Anne
-Original Message-
From: Guha, Suteertha [IE] [mailto:[EMAIL PR
ComputedKeyEnum is defined only once in the XSD: :element name='ComputedKey' type='wst:ComputedKeyOpenEnum' /> :simpleType name='ComputedKeyEnum' > :restriction base='xs:anyURI' > :enumeration value='http://schemas.xmlsoap.org/ws/2004/04/security/trust/CK/PSHA1' />
ComputedKeyEnum is defined only once in the XSD: :element name='ComputedKey' type='wst:ComputedKeyOpenEnum' /> :simpleType name='ComputedKeyEnum' > :restriction base='xs:anyURI' > :enumeration value='http://schemas.xmlsoap.org/ws/2004/04/security/trust/CK/PSHA1' />
Hi All,
Im
using wsdl2java to generate server side components for Security Token Service in
WS-Trust (http://schemas.xmlsoap.org/ws/2004/04/trust/ws-trust.wsdl ) using the following
command:
%java org.apache.axis.wsdl.WSDL2Java --server-side --skeletonDeploy true
ws-trust.wsdl
I hav
I should probably have said before that the error is ocurring in an
Applet that is using SOAP (exclusively) to communicate with the server;
the server being WebLogic 7 SP4 (on Windows 2000). The applet is running
under JRE 1.3.1_09 (Windows XP).
David.
-Original Message-
From: Davanum Sri
Hi again,
I tried the latest nightly build (04-Jun-2004 00:05), but still get the
NoSuchMethodError at
org.apache.axis.transport.http.HTTPSender.writeToSocket(HTTPSender.java:
404).
The NoSuchMethodError seems to be related to the fact that the AXIS
build is done with JDK 1.4 while my application
It is possible to define a Deployment Des. on the client side
(I read so) and set the Handlers also there. But you dont need
in my way - i haven´t use it! :(
Tomi
-Ursprüngliche Nachricht-
Von: Davy Crocket [mailto:[EMAIL PROTECTED]
Gesendet: Donnerstag, 3. Juni 2004 16:16
An: [EMAIL PRO
53 matches
Mail list logo
