I figured out. I need to override setChildValue in my custom serializer and in that
routine I need to convert between int and Intger
__Hari
-Original Message-
From: Hari Lakshmanan
Sent: Thu 3/18/2004 4:54 PM
To: [EMAIL PROTECTED]
Cc
Hi,
I have a custom class like this
Public class XX {
private int ID;
...
...
}
Now I wanted to expose the member variable ID as Integer type on the
consumer side but on the provider side I would like to keep it as int. I
am using custom serializer on the provider side where as I use
BeanSeriali
: SimpleDeserializer encountered
a child element, which is NOT expectedI'm not an expert
on this stuff, but I believe that the beanserializer only works with SOAP
encoding.At 05:57 PM 3/18/2004, Hari Lakshmanan wrote:
Hi Anne,The name space in the SOAP envelop works as you had
desc
Title: Message
Hi
Anne,
The
name space in the SOAP envelop works as you had described. However I am still
having problem and my guess is it has to-do with the MapSerializer and
BeanSerializer (I use Doc/literal web service). When I add a complex type to
hashMap, the value element has two ch
Title: Message
Thanks
a lot for the detailed explanation, I will give it a go and let you
know.
__Hari
-Original Message-From: Anne Thomas
Manes [mailto:[EMAIL PROTECTED] Sent: Thursday, March 18, 2004 6:35
AMTo: [EMAIL PROTECTED]Subject: RE:
SimpleDeserializer encount
Title: Message
I get
the same error and it happens only in a particular scenario. I have a class
like this
public
class BPEvent {
private String processName;
private HashMap attributes;
...
...
}
When I
add a String object to atts everythign works fine. However when I add my
customized
While using java2wsdl with proper switches (DOCUMENT / LITERAL), I get proper wsdl.
The only problem I am seeing is axis lack of support in auto generating the WSDL file
when the service is deployed. To overcome this, I use wsdlFile tag in my WSDD file.
Please let me know if I am missing somet
Thanks Anne,
I have another related question. When I tried Java2WSDL with WRAPPED
style, it generates a WSDL file which does not follow WS-I specification
(Rules R2110 to R2113) I had a LinkedList as one of the Object type. So
my question is does AXIS1.1 support WS-I specification? If not, are
the
Thanks a lot
__Hari
-Original Message-
From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 10, 2004 11:23 AM
To: [EMAIL PROTECTED]
Subject: Re: AXIS support for RPC literal
Axis supports the "wrapped" programming convention. It's
document/literal,
but is supports
Hi
I am using Axis1.1 and I wanted to know whether AXIS supports RPC
literal? If so are there known limitations / issues?
TIA
__Hari
:[EMAIL PROTECTED]
Sent: Friday, March 05, 2004 3:52 PM
To: [EMAIL PROTECTED]
Subject: RE: Document-style web services
>From: "Hari Lakshmanan" <[EMAIL PROTECTED]>
>Reply-To: [EMAIL PROTECTED]
>To: <[EMAIL PROTECTED]>
>Subject: RE: Document-style web servic
Title: Message
Try
using document / literal instead of RPC / literal (if it is OK to use document /
literal)
HTH
-Original Message-From: Wei Hsu
[mailto:[EMAIL PROTECTED] Sent: Friday, March 05, 2004 5:19
PMTo: [EMAIL PROTECTED]Subject: generating stubs
with wsdl2java
, Hari Lakshmanan wrote:
> I mention in my wsdd file as given
>
>
> ...
> doc-literal.wsdl
>
/doc-literal.wsdl
I have a / in mine, but I'm not sure it matters.
>
> I get 500 Error when I access the wsdl page
> (http://localhost:8080/axis/services/NotificationPo
nnnot find the
resource
i.e., WSDL.
Can we use the param element to specify a custom WSDL as follows in
deployment descriptor?
Any pointers?
Thanks,
Vivek
>From: "Hari Lakshmanan" <[EMAIL PROTECTED]>
>Reply-To: [EMAIL PROTECTED]
>To: <[EMAIL PROTECTED]>
I mention in my wsdd file as given
...
doc-literal.wsdl
I get 500 Error when I access the wsdl page
(http://localhost:8080/axis/services/NotificationPort?wsdl)
Is the above syntax correct? If so where should the wsdl file go?
Thanks
__Hari
-Original Message-
From: [EMAIL PROTECTED
Title: Message
Hi
All,
This is axis
specific
Basically there are
three variants to define a service style and they are style, provider and use
attribute in your deploy.wsdd file.
1. style="rpc"
or provider="java:RPC" and use="encoded" maps to RPC with
encoding
2. style="rpc"
or provi
Can you verify your deploy.wsdd contains these attributes?
style="document" and use="literal"
This should preserve the wsdl on the fly (as document based)
HTH
__Hari
-Original Message-
From: Vivek Nagulapati [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 04, 2004 5:29 PM
To: [EMAIL PRO
Title: Message
Hi,
I have deployed a
service which follows document based literal encoding. Now I have a standalone
client and when I use the standalone client, I get the following stack
trace.
=
AxisFault faultCode:
{http://schemas.xmlsoap.org/soap/envelope/}Server.userExcepti
With JDK1.4+, you need to use Endorsed Standards Override Mechanism.
Please refer this link
http://java.sun.com/j2se/1.4.2/docs/guide/standards/
-Original Message-
From: Parley, Thunder Jon [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 04, 2004 1:35 PM
To: [EMAIL PROTECTED]
Subject: Use
PROTECTED] Sent: Thursday, March 04, 2004
11:35 AMTo: '[EMAIL PROTECTED]'Subject: RE: EJB
Authentication
I
use the default BeanDeserializer. I am attaching the Client code and also the
generated code for this bean.
Thanks,
Ramesh.
-Original Message-
can you post your client code and deserializer code?
-Original Message-
From: Bobba, Ramesh [mailto:[EMAIL PROTECTED]
Sent: Thu 3/4/2004 11:01 AM
To: '[EMAIL PROTECTED]'
Cc:
Subject: RE: EJB Authentication
H
Title: Message
Make
sure your org.waterford.util.logging.* classes is available in classpath
__Hari
-Original Message-From: Oleg Lebedev
[mailto:[EMAIL PROTECTED] Sent: Wednesday, March 03, 2004
12:02 PMTo: [EMAIL PROTECTED]Subject:
ClassNotFoundException when using
Does the custom serialization / de-serialization need to be different if
I choose document/literal style rather than RPC/encoded style? The
reason for my question is the doc says that document based service does
not support multi-ref object serialization
Thanks a bunch for your time
__hari
Title: Message
Though I read lot of
postings about this, I am still confused while selecting the style. Are there
any guidelines which one to choose?
Specifically I have
following questions
1. Is axis message
based specific to AXIS?
2. If I want my web
service to be consumed by differen
Make sure the namespace declaration on your deploy.wsdd matches with the
name space you use in your custom de-serializer.
-Original Message-
From: Bobba, Ramesh [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 02, 2004 3:33 PM
To: '[EMAIL PROTECTED]'
Subject: RE: error while deserializing
Title: Message
Hi,
If I
have implemented web service provider using AXIS and also used custom
serialization / deserialization (based on AXIS specific serialization) does the
client always needs AXIS specific serialization / deserialization? How does this
work with a .NET client or client us
Title: Message
Never
mind. It was a case sensitivity problem while registering the Data
class.
__Hari
-Original Message-From: Hari Lakshmanan
Sent: Thursday, February 26, 2004 3:04 PMTo:
[EMAIL PROTECTED]Subject: RE: Deserialization
question
Sorry it should read as namespace instead of qname
mailto:[EMAIL PROTECTED]
Sent: Thursday, February 26, 2004 4:11 PM
To: [EMAIL PROTECTED]
Subject: No serializer found for class
Hello all,
My web service client seems to not register my class with the
BeanSerializer
correctly...I keep getting
Title: Message
-Original Message-From: Hari Lakshmanan
Sent: Thursday, February 26, 2004 2:46 PMTo:
'[EMAIL PROTECTED]'Subject: Deserialization
question
Hi
All,
I am trying
different things with custom serialization. In this process I created a
s
I had similar problem
Make sure qname under typeMappings in your deploy.wsdd is
urn:SearchCategoryService. If not, change it and redeploy and run the
client
Hope this helps
-Original Message-
From: christopher justin [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 26, 2004 4:11 PM
T
30 matches
Mail list logo
