You can add JAX-RPC handlers by configuring the WSDD using the handlerInfo and handlerInfoChain elements. Here is a link to some docs
http://www.osmoticweb.com/axis-wsdd/handlerInfo.htm
Programmatically, you can add handlerInfo and handlerInfo chain to a WSDDService. Here is a sample code snip
,
Shantanu Sen
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Friday, November 19, 2004 9:05 AM
To: [EMAIL PROTECTED]
Subject: RE: Bug about array of beans in 1.2RC2 (wrapped/literal)
I have encountered this same situation with .NET. To fix the problem we had
Actually I found a couple of other past threads with
similar issue:
http://marc.theaimsgroup.com/?l=axis-user&m=109108873418937&w=2
http://marc.theaimsgroup.com/?l=axis-user&m=109224171621865&w=2
Is there any open bug on this?
Thanks,
Shantanu Sen
--- Shantanu Sen <[EMAI
s.
Error: Unable to import binding 'SoapBinding' from
namespace
---
Changing the tns5 namespace to 2001 fixes this.
Anyone seen this before. Any ideas why the anyType is
generated with 1999 namespace?
Thanks,
Shantanu Sen
uses
the ArrayOf* classes as the default typemapping for
arrays of beans.
I have not found any solution to this yet. Any inputs
from anyone on this?
Thanks,
Shantanu Sen
--- Grenier Nicolas <[EMAIL PROTECTED]>
wrote:
> Hello,
>
> I have a Web Services that use JavaBean as In/O
do
not want the arrays be mapped to any new classes. Is
there any
switch that I can use with Java2WSDL to ensure this?
Thanks for any help.
Shantanu Sen
I have a question regarding the following scenario.
I start of with a set of java classes. The main class
is listsvc.ListService:
public interface ListService extends java.rmi.Remote {
public ListPropertyBean[] getListProperties(
String listId)
throws RemoteException, BadIdException
While I understand that the BP recommends
document-literal, in reality most of the vendors use
the 'wrapped' style when generating document-literal
service. I do not know of any vendor to generate pure
doc-lit when configuring a web service using an IDE
(e.g. WebLogic 8.1). Possibly this is because
If you use JAX-RPC handlers, then the handleFault is
called when you throw a SOAPFaultException from your
handler and the runtime walks back the handler chain
calling the handleFault method on each. So there is a
fault response chain on JAX-RPC handlers.
You need to pick up the latest CVS build th
I tried to use client side JAX-RPC handlers and saw
the following problem.
I had 2 handlers handler1 and handler 2. If I use the
happy path everything is fine - handler1.handleRequest
is first called and then handler2.handleRequest and
then the corresponding handleResponse methods in
reverse order
What is the preferred way of adding client side handlers given the following constraints: I only have the generated stub class - I instantiate it using reflection and invoke the relevant method. So, I cannot do a ServiceFactory.createService and then set the handlerinfochain etc as shown in the jax
the
handlers before making the call?
Thanks,
Shantanu Sen
igTicket100" in your
> WSDL. If your web service
> is either rpc/encoded or rpc/literal, then you need
> to use
> type="MyDataTypes:BigTicket100".
>
> - Junaid
>
>
>
>
>
)
If I change this to the following, WSDL2Java works fine
Any ideas if this is a WSDL2Java bug? The schema that causes the error looks legit to me.
Thanks,
Shantanu---Shantanu Sen <[EMAIL PROTECTED]> wrote:
Yes, using both the suggested o
t; To: [EMAIL PROTECTED]
> Subject: Re: WSDL and schema include question
>
>
> You need to mention the relative path of the xsd in
> the WSDL (may be
> ./BigTicket.xsd)
>
>
>
> Shantanu Sen <[EMAIL PROTECTED]>
> 06/29/2004 02:05 PM
> Please respo
the following trace:
java.io.IOException: Type {urn:BigTicket}BigTicket100 is referenced but not defined. at org.apache.axis.wsdl.symbolTable.SymbolTable.checkForUndefined(SymbolTable.java:522)
Am I making some mistake in defining the namespace in the WSDL? If so, what is it?
Thanks for any help.
Shantanu Sen
minOccurs="0"/>
>
>
>
>
>
>
> And you need to add element to your
> input message
> definition:
>
> part="header" use="literal"/>
>
> Note: when using WRAPPED style, there must be only
> one message part
I am enclosing a WSDL at the end of the mail. This is
a typical doc-lit wrapped WSDL.
Basically, the issue is with the following section of
the WSDL
When the WSDL with the above section is used with
WSDL2Java (both in Axis 1.1 and 1.2beta), the
generated i
I noticed that tools such as WebLogic 8.1 workshop
automatically uses the wrapped approach when using the
'document' mode is selected. I did not see any way you
can use 'pure' doc-lit with this toolkit. I did not
check WASP 6.0.
Does this suggest that some vendors think that
'wrapped' is the way
That may be a good enhancement request, but Java2WSDL
gives you more flexbility in the sense that you can
specify doc/lit or wrapped based on your need. So it
assumes that you know what you need.
I was playing with BEA WebLogic 8.1 workshop and when
I create a method and choose to expose it as a
hat has to be a
> known bug.
>
> - dave
>
>
> -Original Message-
> From: Shantanu Sen [mailto:[EMAIL PROTECTED]
> Sent: Monday, April 26, 2004 5:20 PM
> To: [EMAIL PROTECTED]
> Subject: RE: Have doubts about Doc/Lit with axis
>
> I think it will be a great help
I think it will be a great help to all of us if you
could file a bug with your specific test-case.
I disagree with your statement that 'it appears to be
totally broken'. I have successfully used doc-lit -
both wrapped and non-wrapped - with the current axis
src code. But clearly my test cases do n
For correct doc-literal, you cannot use 'type' in your
part definiton. Try changing your message definition
to contain a single part element with an element
attribute (instead of a type attribute).
E.g.
This should cause axis'
Does axis support the Solicit-Response and Notification operations? If so, how?
Weblogic 8 seems to support these by the way of 'callbacks'. I was wondering if anyone has used axis to provide these functionality.
Thanks,
Shantanu Sen
Are you using the rpc-encoded or doc-lit? If you used
doc-lit, you may need to use the wrapped style option.
Shantanu Sen
--- Rosén_Håkan <[EMAIL PROTECTED]> wrote:
> Hi,
> I have written an interface :
> public interface Myervice {
> public boolean logonTest(String userna
,
Shantanu Sen
--- Ricky Ho <[EMAIL PROTECTED]> wrote:
> There is a nice separation between application
> processing and
> infrastructure processing. WSDL describes the
> former and WS-Policy
> describe the later.
>
> If you are writing application code, you shouldn't
&
in the header/body of the SOAP envelope.
If this is true, how does a client know how to send
the correct SOAP message to the service i.e. how does
it know to add the required security info?
Thanks for any info regarding this.
Shantanu Sen
.
Is this a bug in Utils.java? Or is my WSDL incorrect?
Thanks for any help.
Shantanu Sen
PS. Here is the complete WSDL
http://MyService" targetNamespace="http://MyService" xmlns:tns="http://MyService"
jar files?
Thanks,
Shantanu Sen
Chris,
Even then, don't you think that the private method
createMessageContext specified in AxisServlet should
be protected? This may save a lot of code duplication
for applications requiring some control on the
properties of MessageContext.
Currently, the call in buried deep inside both doGet
accordance with
> Unicode
> > > > 2.0, section 5.14).
> > > > * Character #x00B7 is classified as an
> extender, because the
> property
> > > > list so identifies it.
> > > > * Character #x0387 is added as a name
> character, because
name.
>
>
> /Chris
>
>
> -- Original Message
> ------
> From: Shantanu Sen <[EMAIL PROTECTED]>
> Reply-To: [EMAIL PROTECTED]
> Date: Wed, 13 Aug 2003 14:05:55 -0700 (PDT)
>
> >Now if the service name has spaces e.g. "My
> Service",
> >I see a problem
work around this, I do not
see any other option other than overrifing the
AxisServlet doGet and doPost. Ideally if the
createMessageContext method in AxisServlet is
protected instead of private, I could override that to
fix it. Any ideas why this is not protected?
I am using axis 1.1
Thanks for any help.
Shantanu Sen
.
Shantanu Sen
If I want to expose a web service in wsdl, I will need
to publish a WSDL to all potential clients describing
my service. This wsdl will also contain the service
uri.
Now if I want to run my service in a clustered
environment for load balancing, how to I publish this
service uri in the wsdl? Do I
in
> the WSDD and checking if that works? for example,
> 'My%0A%0DService'
>
>
>
>
> /Chris
>
>
> ------ Original Message
> --
> From: Shantanu Sen <[EMAIL PROTECTED]>
> Reply-To: [EMAIL PROTECTED]
&g
as
org.apache.axis.client.Call.addAttachmentPart. I want
to avoid this if I can.
Any help would be appreciated.
Thanks,
Shantanu Sen
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
.
Any ideas?
Thanks,
Shantanu Sen
But CapeClear does not validate this unless I add a name attribute to the soap:fault. Is the name attribute required in soap:fault? I looked at the WSDL spec. section 3.6, but I am still not clear if it is mandatory.Shantanu Sen Shantanu Sen <[EMAIL PROTECTED]> wrote:Anne, Thanks. But even wi
mlsoap.org/soap/encoding/";
> />
>
> Regards,
> Anne
>
> - Original Message -
> From: "Shantanu Sen" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Tuesday, July 29, 2003 7:05 PM
> Subject: soap fault and WSDL2Java question
&
e, as you can
see. But with Axis 1.1 I get the above error. It runs
fine with Axis 1.0, which, I believe ignores the name
attribute in a soap fault declaration.
Any ideas what I am missing?
Thanks,
Shantanu Sen
http://MyService";
targetNamespace="http://MyService";
I could not get the code sample that you said was
attached. Can you please re-send it? It would give me
an idea how to programmatically deploy the mappings.
Thanks,
Shantanu Sen
--- Rodrigo Ruiz <[EMAIL PROTECTED]> wrote:
> RE: interfaces as params?In my experience, you can
> use i
43 matches
Mail list logo