Final followup, FYI.
In the end, the problem turned out to be java2wsdl of wsdl2java of the
following type of xsd fragment:
It appears that it cannot handle the anonymous complexType when
referenced by a subelement. For instance, the approximate equi
pping beans had an infinite recursion in it's equals() method.
I believe that the equals was being called as part of the auto-WSDL
generation. I found out which bean was causing the problem by removing
all beanMapping and typeMapping entries, and then adding them back one
by one.
So, the p
d be nice to know
> that something else isn't wrong.
> - what is it that "?wsdl" is doing that is different than java2wsdl?
I recently had to deal with a similar problem. It turns out that one of
my beanMapping beans had an infinite recursion in it's equals() method.
I've got a deployed service which is perfectly functional, but for which
the ?wsdl option fails with a simple "Exception -
java.lang.StackOverflowError" message (without a stack dump or any other
information). The tomcat/catalina logs are similarly unhelpful. Also
interesting is that java2wsd
Discovered how to do this in Axis: pluggable
providers.
Axis's pluggable provider architecture permits you to
specify that a service should use your provider rather
than the Axis provider. The only doc I found on how
to do this was in the code.
Here's what I did:
Basically you'll need to create
I'm trying to figure out how to implement a service
(actually, a bunch of services) and I'd like to hear
(informed) opinions from the list on two questions.
I'm attempting to expose the reporting portion of an
XML-based ERP system via web services. The ERP system
has a mechanism that permits user
Greetings.
I have a web service, which I successfully deployed on a running Axis server.
Now I am trying to get it to work without a running Axis server by deploying
Axis as a part of webapp.
I updated my webapp's web.xml and server-config.xml files to match those used
on the Axis server. I also
I am trying to change our webservice from type RPC encoded to
Doc/Literal. =3D20
We are running AXIS 1.2 RC2. ...I was hoping all I would need to do is
change in the deployment the attributes on the service. However when I
do this the wsdl generation fails with an error " Please regis
Title: Message
Tony,
you
were right about IWSState not conforming to Java Bean conventions. I was missing
one of the setter methods. Now it's working fine.
Thanks.
-Original Message-From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent:
Wednesday, October 06, 2004 1:24 AM
It may be related to IWSState not following
Java Bean conventions (get and set methods for each property). I don't
know why a section wasn't generated, though, to define the
types in the tns1 namespace.
Tony
Greetings.
I am using java2wsdl to generate
wsdl for my web service.
I have a getN
Title: Message
Greetings.
I am
using java2wsdl to generate wsdl for my web service.
I have a getNextActivity() method which returns IWSActivity, so wsdl2java
correctly generates the following:
I also have a getState() method, which returns IWSState, but
wsdl2java uses anyType as shown
Hello Axis-people,
Am currently looking at a deployed system for a client with a secure
website and an https SOAP interface to a WebService. This app. has
recently been extended to serve two additional domains and after some
reconfiguration have got the 3 websites working on the app. server. The
Is it possible to generate wsdl files on the fly from a webapplication (using AdminClient and Java2wsdl) without restarting the server (in this case tomcat)?
Do you Yahoo!?Friends. Fun. Try the all-new Yahoo! Messenger
he
request instead, Axis will clobber whatever you put there.
Having now spent the better part of two days trying to override WSDL
generation via a Handler in Axis, it seems Axis doesn't make this very
easy. There are lots of details about how Axis generates WSDL that a
Handler writer needs to
tituting a static file.
> Following a tip from Tom J I've been doing this via Hander.generateWSDL().
> I've learned that WSDL generation happens in
> org.apache.axis.providers.BasicProvider.generateWSDL()
>
> What surprises me is that the work this method does doesn't
I've been experimenting with overriding the WSDL that Axis provides in
a dynamic fashion. Doing more than just substituting a static file.
Following a tip from Tom J I've been doing this via Hander.generateWSDL().
I've learned that WSDL genera
Sent: Thursday, April 15, 2004 3:28 PM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: RE: WSDL generation problem
i don't have a ejb container so i tried to strip down the class and did
not see any problem. see
the java and build.xml enclosed.
-- dims
--- Rob Jellinghaus <[EMAIL PROT
o do in your Java code* (or even in your
> java2wsdl target) to fix this error, given the wording of the error
> itself.
>
> Cheers!
> Rob
>
> -Original Message-
> From: Davanum Srinivas [mailto:[EMAIL PROTECTED]
> Sent: Thursday, April 15, 2004 2:28 PM
> To:
ic message?)
There's no way to know *what to do in your Java code* (or even in your
java2wsdl target) to fix this error, given the wording of the error
itself.
Cheers!
Rob
-Original Message-
From: Davanum Srinivas [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 15, 2004 2:28 PM
To: [EMA
d a
> campaign object (via any of the campaign.set*() methods).
> * @param campaign
> * @throws NFNoSuchEntityException if no campaign with that ID exists
> */
>public void updateCampaign(
> com.nimblefish.core.domain.campaign.Campaign campaign )
> throws com.nimblefis
PROTECTED]
Sent: Thursday, April 15, 2004 2:24 PM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: RE: WSDL generation problem
Rob, Jagannath,
you should not get this problem in Axis 1.2 Beta. If you do, then please
open a bug report.
thanks,
dims
--- Rob Jellinghaus <[EMAIL PROTECTED]> wr
nt: Thursday, April 15, 2004 7:20 AM
> To: [EMAIL PROTECTED]
> Subject: WSDL generation problem
>
> Hi,
>
> I am unable to generate the wsdl for my web service using the
> AxisServlet. The below exception gets thrown. Am I missing something
> during the configuration of
Original Message-
From: jagannath [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 15, 2004 7:20 AM
To: [EMAIL PROTECTED]
Subject: WSDL generation problem
Hi,
I am unable to generate the wsdl for my web service using the
AxisServlet. The below exception gets thrown. Am I missing something
during
Hi,
I am unable to generate the wsdl for my web service using the
AxisServlet. The below exception gets thrown. Am I missing something
during the configuration of the web service?
I am using Axis 1.1
Please help.
[INFO] enterprise - -Mapping Exception to AxisFault http://management.javax'.
Thank you Thomas. Is there any documentation about this?
> -Original Message-
> From: Thomas Bayer [mailto:[EMAIL PROTECTED]
> Sent: Thursday, November 06, 2003 2:59 PM
> To: [EMAIL PROTECTED]
> Subject: AW: WSDD question - parameters that control WSDL
> generation ??
Hallo Mark,
yes these parameters control the WSDL generation using the WSDL Querystring.
I don't know where documentation can be found. Perhaps that helps:
wsdlPortType = name for the port type
wsdlServiceElement = name for service element
wsdlServicePort = name for the port
wsdlTargetName
In looking through some of the sample and test cases related to the JAXRPC
implementation (e.g., /samples/jaxrpc/hello, /test/wsdl/jaxrpchandler), I notice that
some of the deployment files (.wsdd files) define services with parameter sub-elements
having names like:
wsdlServiceElement
wsdlServi
Hi all,
we provide some services for vb.net users with simple
data structures as in- and output. Some other services only
for java clients with complex data structures. How can I deploy the
services so that the vb client can not view the
services provided for the java client ? Is there
Hi,
I've a problem with SimpleAxisServer,
I've a simple WebService, when run Axis from Jetty
and then refer to http://localhost:9090/services/adder?wsdl
I get WSDL , but when I test this with SimpleAxisServer
and when getting wsdl it sends AxisFault, such as this:
http://schemas.xmlsoap.org/soap
Separate WSDL files proabably. Unless you can get away which
services are valid for which client type.
-Original Message-From: Doss Markus
[mailto:[EMAIL PROTECTED]Sent: Monday, August 11, 2003
10:03 AMTo: [EMAIL PROTECTED]Subject: WSDL
generation
Hi
all,
we
I cant help but I have a similar issue. If I have an interface
with a Map parameter and run Java2WSDL followed by WSDL2Java
the Map is converted into a HashMap.
Im therefore not sure if AXIS is completely happy with interface
types used as parameters.
My bit.
Stuart.
Shantanu Sen wrote:
I have the
I have the following interface that I want to expose
as a web service.
public interface MyOperation extends java.rmi.Remote {
public MyComplex testOperation(java.util.Map map,
MyDoc[] docs)
throws java.rmi.RemoteException;
}
where MyDoc is an interface:
public interface MyDoc {
public Str
t needs to. Similarly for any client code that
reads the wsdl. The human reader has to find it manually and look at it.
Jeff
- Original Message -
From: "remko de knikker" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, July 30, 2003 8:56 AM
Su
at it.
Jeff
- Original Message -
From: "remko de knikker" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, July 30, 2003 8:56 AM
Subject: Axis wsdl-generation with
> Problem/Question:
> when Axis generates the wsdl for my webservice, whose wsdl cont
Problem/Question:
when Axis generates the wsdl for my webservice, whose wsdl contains an
it doesn't 'expand'/or import the reference, but merely
reprints the import statement.
Am I doing something wrong, or is this the (in my opinion, if so, not
very practical) preferred method??
I am using an
Hi Remko and George!
Thank you for you help! By doing some testing and tries, I
figure out that leaving the comment in the following line
AdminServlet
/servlet/AdminServlet
would prevent the wsdl to be generated. So I comment it out and now it
works! Thanks for you suppo
1. How about all the rest of your service, is that all working fine?
2. Did you follow the deployment steps using
java org.apache.axis.client.AdminClient deploymentfile.wsdd
?
r
Sochea Meas (LMC) wrote:
automatic wsdl generation
Hi all,
When I
Title: automatic wsdl generation
In
coldfusion's implementation of axis I have seen this occur if there is a wsdl
generation error. Almost seems like the proper errors are not being thrown and
instead you get a page cannot be found error.
Try
running java2wsdl from the command promp
Title: automatic wsdl generation
Hi all,
When I append "?wsdl" at the end of my service, I get a page not found error. What do I need to activate in order to make it work properly? I am using Axis 1.1 Final.
Thank you for your support!
-
Sochea MEAS
LMC/JG/A
You can also add the newer wsdl4j.jar to the servers classpath. Go to the
"Paths" tab of the server configuration and at the bottom of the page you
can add jars to the classpath. I ran into the same problem trying to use
the newest version of xerces, xalan and jdom. If you add the jars here they
a
Axis users, be warned that WSAD (Version 5) includes an older version of the
wsdl4j.jar file under its "runtimes\aes_v4\lib" directory. This file gets
included in the boot classpath for the WAS 4.0 test environment server and
you will run into NoSuchMethodErrors when trying to run the "?wsdl" get
m
I have written and deployed a web service that returns a fairly complex
javabean object (complex meaning lots of aggregate javabeans). I have
successfully called the web service method from a standalone client that I
wrote by following the user guide example. I would now like to use the WSDL
to g
mailto:[EMAIL PROTECTED]
Sent: Thursday, March 06, 2003 1:21 PM
To: [EMAIL PROTECTED]
Subject: RE: EchoAttachmentsService wsdl generation error
Can you copy and paste the WSDL into an email for us?
At the very least can you show us the WSDL statements where
"urn:EchoAttachmentsService&quo
achdeploy.wsdd to deploy it.
>
>
> -Original Message-
> From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]
> Sent: Thursday, March 06, 2003 10:09 AM
> To: [EMAIL PROTECTED]
> Subject: RE: EchoAttachmentsService wsdl generation error
>
>
> Paul,
>
> Can yo
PROTECTED]
Sent: Thursday, March 06, 2003 10:09 AM
To: [EMAIL PROTECTED]
Subject: RE: EchoAttachmentsService wsdl generation error
Paul,
Can you give us a pointer to the WSDL?
It appears that the system views urn: as a namespace prefix, and it can't
find a namespace declaration for th
mailto:[EMAIL PROTECTED]
> Sent: Thursday, March 06, 2003 12:05 PM
> To: '[EMAIL PROTECTED]'
> Subject: EchoAttachmentsService wsdl generation error
>
>
>
> I get the following error when I select the (wsdl) link from the service
> listing page. The EchoAttachmentsServ
I get the following error when I select the (wsdl) link from the service
listing page. The EchoAttachmentsService actual is running and the client
can connect and everything works fine. I tried deploying without the "urn:"
namespace but it didn't make any difference when trying the wsdl link.
LS.
I have the following problem with the generation of WSDL for a serializer:
The targetNamespace of the schema stays empty as you can see in the
attachements.
This appears not to be a problem for calling the webservice. It works fine.
It is just that other programs like xmlSpy cannot create a SO
AMTo: '[EMAIL PROTECTED]'Subject:
Namespace getting dropped from WSDL generation
Hello
All-
Can someone shed some light on
what I am doing wrong here?
In a nut shell...I have a complex
type that inherits from "Exception"...
In the WSDL that Axis1.
Hello All-
Can someone shed some light on what I am doing wrong
here?
In a nut shell...I have a
complex type that inherits from "Exception"...
In
the WSDL that Axis1.1 generates (which a stub is below), Axis added the "tns4"
namespace to the type attribute.
The
I deployed a service, apparently without problems, but when requesting the
?wsdl for it, there is a problem with namespaces in the WSDL generator
(as shown in the stack trace below).
Is there something that can be added to the .wsdd file to make this problem
disappear? Is there a chance that the
You might want to upgrade to Mozilla 1.2.1. For 1.2.1 the Mozilla crew
implemented direct rendering of plain XML (including WSDL returned by
the ?wsdl query), with a note at the top that "This XML file does not
appear to have any style information associated with it. The document
tree is shown
02:54 PM
Please respond to axis-user
To: [EMAIL PROTECTED]
cc:
Subject:Re: Mozilla and automatic ?wsdl generation with
Axis 1.0
thanks, that worked! :) :) :)
On Mon, 2002-12-16 at 08:48, Jess Sightler wrote:
> Have you tried hitting the View Source button i
thanks, that worked! :) :) :)
On Mon, 2002-12-16 at 08:48, Jess Sightler wrote:
> Have you tried hitting the View Source button in your browser?
>
> A lot of times, Mozilla doesn't display formatted XML.
>
> ---
> Jess Sightler
>
>
> On Mon, 2002-12-16 at 14:47, Eric Jahn wrote:
> > Does anyon
CTED]>
Sent: Monday, December 16, 2002 8:47 PM
Subject: Mozilla and automatic ?wsdl generation with Axis 1.0
> Does anyone have this working with Mozilla and Axis 1.0? Axis seems
> properly configured according to the happyaxis.jsp test page, and tomcat
> now reports no errors (I f
Have you tried hitting the View Source button in your browser?
A lot of times, Mozilla doesn't display formatted XML.
---
Jess Sightler
On Mon, 2002-12-16 at 14:47, Eric Jahn wrote:
> Does anyone have this working with Mozilla and Axis 1.0? Axis seems
> properly configured according to the hap
Does anyone have this working with Mozilla and Axis 1.0? Axis seems
properly configured according to the happyaxis.jsp test page, and tomcat
now reports no errors (I fixed the wsdd server-config error), but I
still can't automatically generate wsdl (even for the sample services).
The Mozilla brow
something similar using Apache SOAP 2.x and our own WSDL generation
mechanism, but we would like to migrate to Axis. I'll do some more digging.
-Original Message-
From: Dennis Sosnoski [mailto:dms@;sosnoski.com]
Sent: Monday, November 11, 2002 8:56 PM
To: [EMAIL PROTECTED]
Subjec
prefer that the clients of the webservice not know about
the server-side parameter (in the WSDL). I will probably try to subclass
the WSDL generation classes to exclude the offending 'server-side supplied'
arguments from the input message. However, I'm concerned that the change
mig
ethod'
method in the RPCProvider to inject the objects into the method argument
array before invoking the method. That seems like it would work ok.
However, I would prefer that the clients of the webservice not know about
the server-side parameter (in the WSDL). I will probably try to subclas
Hi,
I am using Axis 1.0 with JDK 1.4.1/Tomcat 4.1.10-LE-jdk14 on my Win2K
box.
I am trying to view the WSDL of the AddressBook example from the browser
by pointing the URL :
http://localhost:8080/axis/services/AddressBook?wsdl
It throws the following exceptions. Am I missing anything?
- Exception
There is a problem with WSDL generation in axis beta3 and the latest nightly build
under resin-2.1.1. Some namespace declarations on the wsdl:definitions element are
missing the names, i.e. xmlns:="http://...";.
The workaround for this is to remove the Caucho XML parser and add
PROTECTED]'
Subject: FW: Bug with AxisFault and WSDL generation
Hi Axis Developers,
there hasn't been a response on axis-user. I think it surely is a bug
because Axis is not able to generate a proxy (with WSDL2Java) out of a
WSDL definition created by itself.
Do you have any hints
Hi everybody,
I'm trying to use my own SOAP fault codes instead of the default
"Server.userException". My idea was to let my Web Service class throw a
AxisFault. I can set the faultcode etc. within the AxisFault
constructor. I've set up such a web service that does nothing but throw
a new AxisFau
Hi all,
Does someone test the server side wsdl generated
code?
I try to use some toolkit ( SOPA:Net from www.soaptoolset.com , XML Spy (soap
debugger)) and none of them succeed in parsing wsdl ...
i use the lastnightly build ...
Some help will be welcome
Jean Marc
this question applies to beta1 rc2
when i try to generate the WSDL from the ?wsdl query, the namespaces that
get generated for the targetNamespace, intf, and impl all includes a
complete URL that includes the location of the machine that hte axis servlet
is running on.
also, all namespace="" val
; To: [EMAIL PROTECTED]
> Subject: RE: Performance of WSDL generation (benchmark
> program included)
>
>
> HI!
>
> I have extracted the latest bcel and tt-bytecode
> implementation from ClassRep.java and put in a little
> benchmark program. Plase find it attached.
>
t; From: Glen Daniels [mailto:[EMAIL PROTECTED]]
> Sent: Dienstag, 26. Februar 2002 14:13
> To: [EMAIL PROTECTED]
> Subject: Re: Performance of WSDL generation
>
>
> Hi Thomas!
>
> I haven't seen this, but I'll take a look into it when I get
> a chance. As
002 14:13
> To: [EMAIL PROTECTED]
> Subject: Re: Performance of WSDL generation
>
>
> Hi Thomas!
>
> I haven't seen this, but I'll take a look into it when I get
> a chance. As it
> stands, BCEL was not working for JWS files because of
> classloader issues
--Glen
- Original Message -
From: "Thomas Börkel" <[EMAIL PROTECTED]>
To: "Axis User Mailinglist" <[EMAIL PROTECTED]>
Sent: Tuesday, February 26, 2002 4:53 AM
Subject: Performance of WSDL generation
HI!
Since the switch from bcel.jar to tt-bytecode.jar
HI!
Since the switch from bcel.jar to tt-bytecode.jar for analyzing Java .class files in
the WSDL generation process, performance has become unacceptable. What was 1-2 seconds
is now 30 seconds with some .class files. Am I the only one experiencing this?
I have attached the .class file of a
cc:
Subject: WSDL generation before deployment
Hi All
I have few doubt regarding wsdl generation:
1.how do i get WSDL of my service withou deploying me service and
getting it from url???
2.to b more specific,can i get it by using my deploy.wsdd or with
applcation class going to b deployed
3.It
Hi All
I have few doubt regarding wsdl generation:
1.how do i get WSDL of my service withou deploying me service and
getting it from url???
2.to b more specific,can i get it by using my deploy.wsdd or with
applcation class going to b deployed
3.It will do if my wsdl does not contain port info
pha3 in WSDL generation: New problems
with .NET 1.0 (bugs found and fixes
prov
Title: Changes in current build vs. alpha3 in WSDL generation: New problems with .NET 1.0
Since
we checked the fix in on 2002-02-07, it would appear in today's (2002-02-08)
nightly build.
--
Tom
Jordahl
Macromedia
-Original Message-From: Thomas Börkel
[mailto:[EMAIL PROT
Title: Changes in current build vs. alpha3 in WSDL generation: New problems with .NET 1.0
HI!
I
tested the latest build from 2002-02-07 and there the problem is not
fixed.
Please
let me know how Russell want to deal with the appended "Service"
problem.
Regar
Title: Changes in current build vs. alpha3 in WSDL generation: New problems with .NET 1.0
Hi
Thomas!
I'm
going to let Russell deal with your first problem, but I think Tom and I
resolved the second one with our last fix. Can you check to see if the
current CVS works for you? T
Title: Changes in current build vs. alpha3 in WSDL generation: New problems with .NET 1.0
OK, I
found both problems I mentioned below by myself after a debug session (I don't
like this very much):
1.
"Service" is being appended to the name
Title: Changes in current build vs. alpha3 in WSDL generation: New problems with .NET 1.0
If I
change the Response definition of the current build, then .NET is
happy:
Normal
output from the current build:
Manuelly changed WSDL to:
Why is
this
Title: Changes in current build vs. alpha3 in WSDL generation: New problems with .NET 1.0
HI!
Why does the current build always append "Service" at the service name? Alpha3 did not do that and that was good.
Also, .NET issues an error now on the WSDL file:
Unable to impo
80 matches
Mail list logo
