XML spy shows this to be a valid WSDL file , though
the tns declaration is being done twice once at
definition level and once in schema with two different
URI's
--- babloosony <[EMAIL PROTECTED]> wrote:
> Hi All,
>
>
> Is there a problem with namespace prefix 'tns' in
> the schema
> declaratio
Hi All,
Is there a problem with namespace prefix 'tns' in the schema
declaration of the below wsdl. I am not that much comfortable with xml
schemas and namespaces and their usage in wsdl. Can anyone please tell
if there is problem in schema section of the below wsdl although I
used WSDL Validato
OK, thanks for the confirmation. Is there any workaround?
I thought about splitting the definition into two parts, like
... but I can't get that to work either. I think it's not proper XML
schema.
Gilles Devaux wrote
You are right... the wrapper / bare array behavior changes if you have
get/set methods for array elements (see mail below). However, the Axis
developers are going to change that behavior. (See
http://marc.theaimsgroup.com/?l=axis-dev&m=110904139408149&w=2)
Going forward, the only way to have
First -- your original WSDL was invalid becuase you specified
"document" style, but your message parts referenced types. When using
"document" style (or "wrapped" style -- which is document style using
a specific programming convention), your message part definition must
reference an element, and y
Thank you very much both of you :-)
I already use the dynamic invocation calls and wanted to try and see if I
could use stubs too. I started using the stub generator that comes with J2ME
Wireless Toolkit, but I'm getting errors. This however, is related to
ksoap2.serialization (the PropertyInfo cl
Hi,
The IBM WAS 5.1 webservices implementation (which appears to have
used Axis as a starting point) maps unknown / unsupported XML types to
javax.xml.soap.SOAPElement . A reading of the JAX-RPC 1.1 spec
indicates that this is what the spec specifies. Axis 1.2, however
seems to map everything
Adding mail.jar to the classpath will fix the problem.
Thanks
On Tue, 22 Feb 2005, Christopher Johnson wrote:
> All -
>
> when trying to connect to my service I get an axis fault the following..
>
> I did find a website that provides a solution for the problem but I'm
> having a hard time under
All -
when trying to connect to my service I get an axis fault the following..
I did find a website that provides a solution for the problem but I'm
having a hard time understanding the google translation any help would be
great (
http://translate.google.com/translate?hl=en&sl=ja&u=http://www.atm
Title: help with configuration
hi,
I am trying to get the echo test client working. I have successfully depoyed on solaris and can run the client properly. However, when I run the sample from my XP box I get the error below. Can anyone tell me what might be wrong with my configuration on t
MessageChristian,
I was reading in the AXIS documentation and found out how to use WRAPPED
style calls.
This explains my error message below.
is interpreted as an operation name. (should be the name of the
operation with all arguments as childs)
Thanks for your hints, i wouldn't have come that fa
Title: Message
Yup, same issue here Christian. The java2wsdl
generates a different WSDL than Axis does when it auto-generates the
WSDl.
- Original Message -
From:
Faucher, Christian
To: axis-user@ws.apache.org
Sent: Tuesday, February 22, 2005 12:42
PM
Subject: RE :
Title: Message
Thomas,
I
see.
I
generated my WSDL using java2wsdl, specifying the proper CLI argument for
WRAPPED. I do not use the auto-generated one, which is sligthly
different from the one generated with java2wsdl. I couldn't get the
auto-generated (?wsdl) to bet ".net friendly"
Title: Message
Christian,
Hm. No I didn't change anything in the WSDL file
since i don't know where to change from "document" to "wrapped" in the WSDL
file.
This relates to my question below where i didn't
know where to change to wrapped.
>>Thanks for your hint. Read it up in the
docume
Title: Message
Thomas,
iich.. Sorry for the silly question, but I guess you
regenarted your clietn stubs, from your new WSDL?
Otherwise, this one beats me. Sorry.
Christian
-Message d'origine-De : thomas willomitzer
[mailto:[EMAIL PROTECTED] Envoyé : mardi, février 22,
Title: Message
Christian,
thanks again. Changed the style to WRAPPED in the
.wsdd file (the one generated from wsdl2java as below) and am now getting an
error like:
(I'm attaching my wsdd file as well
below)
Do i have to change anything else to make it work
again? Sorry for the huge amount
yes, and don't you also need the array getter and setter?,
such as
public String[] getPhoneNumbers()
{
return phoneNumbers;
}
public void
setPhoneNumbers(String phoneNumberArray[])
{
phoneNumbers = phoneNumberArray;
}
From: Pra
Title: Message
Java2WSDL set the -y parameter to
WRAPPED
- Original Message -
From:
Faucher, Christian
To: axis-user@ws.apache.org
Sent: Tuesday, February 22, 2005 11:59
AM
Subject: RE : Is this a serious bug in
string parameter passing to AXIS 1.2RC2?
I
d
Or I think you can have get and set methods for the
getting setting corresponding array elements as follows:
class employee { String
name; String[] phoneNumbers;
public String getPhoneNumbers(index i) {
return phoneNumbers[i];
}
Title: Message
You
can specify the style="WRAPPED" attribute in the ..., in the WSDD. Remove the
provider="java:RPC" though!
Or you
can generate your own WSDL using java2wsdl, using a cli arg, which I dont
remember the name. Type "/?", shoudl give you more
info
Christian Faucher
--
Title: Message
I dont
know for auto-generated WSDL. We are a Java/Axis server, my client is
.NET, and we have a Java2WSDL WSDL file. We avoid the auto-generated
one.
Christian Faucher
-Message d'origine-De : Hollywood
[mailto:[EMAIL PROTECTED] Envoyé : mardi, février 22,
Title: Message
Christian,
Thanks for your hint. Read it up in the
documentation and understand that now.
How can i specify WRAPPED style parameters? Couldnt
find any info in there except hacking the deploy.wsdd after the
wsdl2java.
Thanks a lot
Thomas
- Original Message -
Fr
Title: Message
Since I had the same issue, and it wasn't responded
too, I'll piggy back this one. I noticed this same thing, so I switched to
using WRAPPED. However, when Axis auto-generates the WSDL, it inserts
bogus characters (bogus characters being >) into the element names; which
caus
sounds right.
as we discussed previously, .NET can use a
wrapper class in the same way, but doesn't need to.
From: Bill Keese
[mailto:[EMAIL PROTECTED] Sent: Monday, February 21, 2005
11:45 PMTo: axis-user@ws.apache.orgSubject: Re:
rpc/literal vs document/literal, and returning a list
Title: Message
Hi,
You WSDL defines a "document" style
WS. Documen-style WS are made to receive a bean, with all the parameters
in it e.g.
public class MyParamsBean
{
String
str1;
String
str2;
}
and
void
yourMethod(MyParamsBean params);
If you wish to keep the parameters
Hello!
I'm having problems with string parameters in AXIS 1.2RC2.
I created a simple WSDL to test parameter passing and AXIS doesn't process
the parameters correctly
on the Server side.
Only the first parameter gets set to the value in the request, the 2nd and
3rd are set to null in the
service me
Can anyone give me some pointers on how to deal with Faults when using XMLBeans
or any non-Axis Serializer/Deserializers?
__
Do you Yahoo!?
Meet the all-new My Yahoo! - Try it today!
http://my.yahoo.com
you don't !
Your service interfaces should be modelled as messages
specified in XML Schema. Not Java objects (or interfaces).
For your purposes, maybe you want to look into
WS-Security?
From: swetha Ranganathan
[mailto:[EMAIL PROTECTED] Sent: Tuesday, February 22, 2005 3:09
A
Anyone any thoughts on this?
- Original Message -
From: "Hollywood" <[EMAIL PROTECTED]>
To:
Sent: Saturday, February 19, 2005 9:15 AM
Subject: Wrapped/Literal WSDL issue.
Hello,
I'm generating a fairly simple web service in Axis 1.2RC2 (I've tried RC3
too) running under Tomcat 5.0X and
Rather than going to the dynamic invocation pattern, could you not
specify a webservices interface that accepted and replied with
XmlElement ?
Then any arbitrary XML could be accepted as an input and output message,
and you can use XMLBeans as the serializer/de-serializer in your
application lay
Hi Tom
I tried the way you said. I am enclosing the sample code also. But I am
getting this following error. Please help me how to proceed further from
here
org.xml.sax.SAXException: Bad types (class java.lang.String -> class
oasisNamesT
cSPML101.BatchRequest)
Regards
Deepak
-Original
Hi, I'm trying to send some custom HTTP headers using an Axis client. I
saw the following code in the HTTPSender class that processes a custom
table of headers, obtained from the MessageContext, which is just what I
want:
//process user defined headers for information.
Hashtable use
I looked for the same thing as we are using XMLBeans rather than the Axis
default, and someone had
posted to this list a while back with an example app which includes source.
--- Jay Glanville <[EMAIL PROTECTED]> wrote:
> Hello all.
>
> I need to write a custom serializer/deserializer. Unf
Hello all.
I need to write a custom serializer/deserializer. Unfortunately, the
Axis documentation on this subject is a little sparse ("go look at the
code").
I find that the code can be a little daunting, especially if the
serializer I need can be simple.
So, does anybody know of a guide that
That works! Thanks for your help.
--- Korhan Gülseven <[EMAIL PROTECTED]> wrote:
> Hi
>
> using xerces instead of what comes in weblogic.jar solved the problem
> for me with wls 8.1 sp3:
>
> -Put xml-apis.jar and xercesImpl.jar into /web-inf/lib
> -Go http://localhost:7001/axis/happyaxis.js
[EMAIL PROTECTED] wrote:
Hi Tom
Thanks a lot for the reply. Can you just explain a little bit further on
this.
1) How to I cast the bean to the autogenerated class
You don't - in fact, I'd avoid all autogenerated code other than your
XMLBeans, forget about the Axis tools in this case.
2) Can y
Hello,
I have recently completed a series of simple performance measurements
for Apache Axis. I wanted to share the results and see if I could get
any new insights on the data.
To check out the results you should go to the following URL:
http://www.atl.external.lmco.com/projects/QoS/compare/dist_oo
Hi Tom
Thanks a lot for the reply. Can you just explain a little bit further on
this.
1) How to I cast the bean to the autogenerated class
2) Can you provide some information on document style dynamic invocation
3) Can it be found out from the WSDL file that our service is document
style or no
Hi All,
I was trying to use Castor as AXIS 1.2 RC2 (De)Serializers and was
following the tutorials
http://www-106.ibm.com/developerworks/webservices/library/ws-castor/#getcastor.
When I register my service using below lines in
server-config.wsdd, the service is not deployed properly and I get
bel
Yves,
Thanks for the confirmation. I will cetainly file the
necessary report with details -- however, in the
meantime:
Problem-1 (primary concern):
* What would be the recommended workaround? Anyone has
nay other way in which we can achieve this without
having to invoke the XMLSignature-generatin
[EMAIL PROTECTED] wrote:
Hi
I am using apache axis to talk to a web service. To generate the message
I am using apace XMLBeans. But we I want to send this message to the
webservice, The java class generated by wsdl2java task doesn't accept
it. The classes generated by xmlbeans and Apache axis a
Hi
My webservice has to taken a org.ietf.jgss.GSSCredential object as input. How do I generate WSDL file for this webservice which has user defined object as input parameter.
Thanks
RegardsSwethaRegardsSwetha
Yahoo! India Matrimony: Find your life partner
online.
Title: Problem in talking to Web Service
Hi
I am using apache axis to talk to a web service. To generate the message I am using apace XMLBeans. But we I want to send this message to the webservice, The java class generated by wsdl2java task doesn't accept it. The classes generated by xmlb
Hello,
When we use Java2WSDL to generate a WSDL, Axis generates namespace
prefix in the form of tns1, tns2,
Can we choose this namespace prefix ourselves ?
I watch at the reference guide of Java2WSDL tool but I don-t find this
fonctionnality. Perhaps, I miss something ?
Joseph
Same thing here, it appears that AXIS interpret the element just
like the element.
-Message d'origine-
De : Bill Keese [mailto:[EMAIL PROTECTED]
Envoyé : mardi 22 février 2005 09:43
À : Axis-User
Objet : xsd:choice (and WSDL2Java)
It looks like WSDL2Java doesn't support xsd:choice for
Hi !
Is there any point in saving the Service and/or Call objects between
multiple SOAP calls ? say for example that I am going to send a number of
SOAP requests after each other, or should I create new Service and Call
objects for each request ?
Mikael
It looks like WSDL2Java doesn't support xsd:choice for Axis 1.2. Can
(Banyone confirm/deny this?
(B
(BI had a declaration like this:
(B
(B
(B
(B
(B
(B
(B
(B
(B
(B
(BI expected the generated java code to look like this:
(Bclass FilterList {
(BFilters[] filters;
(B}
(B
(BBut instea
47 matches
Mail list logo
