gt; Axiom jar?
If I'm not wrong this is caused by a wrong API definition in
stax-api-1.0.0. Make sure you upgrade to version 1.0.1.
--
Javier Kohen <[EMAIL PROTECTED]>
ICQ: blashyrkh #2361802
Jabber: [EMAIL PROTECTED]
signature.asc
Description: Esta parte del mensaje está firmada digitalmente
r homework reading the corresponding
documentation, make sure to check out the "target" compiler option. You
can use it to ask the Java 5 compiler to produce code a Java 1.4 VM can
understand.
Yours truly,
your alien overlord.
--
Javier Kohen <[EMAIL PROTECTED]>
ICQ: blashyrkh #2
>
> > options.setTo(targetEPR);
Check the line where EndpointReference is constructed in your code.
You'll see that there is an extra space between " and http:. You can
also see it in some of the previous posts in this thread.
Cheers,
--
Javier Kohen
espond to those messages. I am unable to write
it myself properly, although I've written a large amount of correct WSDL
that didn't reference faults.
Please see Message-Id: <[EMAIL PROTECTED]> by
myself where I explain in more detail why I'm stuck.
Thanks,
> Javier Kohen wrote
El vie, 02-02-2007 a las 21:04 -0500, Davanum Srinivas escribió:
> Yes please with sample code/wsdl/schema to recreate the problem.
I created JIRA AXIS2-2113 for this issue.
Thanks,
> On 2/2/07, Javier Kohen <[EMAIL PROTECTED]> wrote:
> > El mié, 31-01-2007 a las 20:23 -08
m using bindings (XMLbindings in my case), I expect to
be able to use those instead of having to write the code by hand.
Moreover, when using sync. calls, the exception is used, so I'm pretty
sure that this is a bug. Should I open a JIRA? I'm using Axis2 1.1.1.
Thanks,
--
Javier
age with a
non-standard faultcode, as is the case in my second sample. Or is that
not an issue and Axis2 will parse it alright as long as I define the
fault message with a NewChallenge element? Somehow this didn't work for
me in the past, but I could be wrong.
Thanks,
> On 2/2/07, Javier K
n get more help with this.
Thanks for your time,
--
Javier Kohen <[EMAIL PROTECTED]>
ICQ: blashyrkh #2361802
Jabber: [EMAIL PROTECTED]
signature.asc
Description: Esta parte del mensaje está firmada digitalmente
0
>
>
> Runtime: Axis1.4 run on Weblogic815.
That's a direct consequence of using chunked encoding and is a standard
part of HTTP.
--
Javier Kohen <[EMAIL PROTECTED]>
ICQ: blashyrkh #2361802
Jabber: [EMAIL PROTECTED]
signature.asc
Description: Esta parte del mensaje está firmada digitalmente
x27;t recall
the details).
I found little to no examples online involving non-standard fault codes,
so I'm pretty lost. I have written a few large WSDLs from message-data
and this is the last remaining itch.
Thanks for your time,
> On 1/17/07, Javier Kohen <[EMAIL PROTECTED]> wrote:
, but it doesn't qualify
MyElement properly, as it ends up with an empty namespace:
Then:
Thanks for your attention,
--
Javier Kohen <[EMAIL PROTECTED]>
ICQ: blashyrkh #2361802
Jabber: [EMAIL PROTECTED]
signature.asc
Description: Esta parte del mensaje e
.][__n_n_|DD[ _ | |
> >(____|__|_[_]_||
> _/oo O oo` ooo ooo 'o!o!o o!o!o`
> -+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
--
Javier Kohen <[EMAIL PROTECTED]>
ICQ: blashyrkh #2361802
Jabber: [EMAIL PROTECTED]
signature.asc
Description: Esta parte del mensaje está firmada digitalmente
t; > >
> > > This method returns a String object.
> > >
> > >
> > >
> > > When I convert it to wsdl using the java2WSDL tool the wsdl method
> > gets
> > > generated with a getEligibleIVRPromotionsRequest Object as input and
> > > getEligibleIVRPromotionsResponse Object as the return
> > > object.
> > >
> > >
> > >
> > > How do I prevent this and make the method return a String object and
> > not a
> > > wrapper object getEligibleIVRPromotionsResponse? Attached
> > > is the wsdl. Please help.
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > Thanks
> > >
> > > Harish
> > >
> > >
> > > -
> > > To unsubscribe, e-mail:
> > > [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> > >
> > >
> > >
> > >
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
--
Javier Kohen <[EMAIL PROTECTED]>
ICQ: blashyrkh #2361802
Jabber: [EMAIL PROTECTED]
signature.asc
Description: Esta parte del mensaje está firmada digitalmente
de with Axis2
1.1.1? I'm accessing a .NET webservice with a WSDL2Java generated stub
(both with adb and xmlbindings, depending on the complexity of the WSDL)
and I couldn't figure out how to access unwrapped fault details and, in
one case, an unwrapped response (all other messages have just
step indicated in the userguide.
They are generated along the XSB files when you run WSDL2Java.
--
Javier Kohen <[EMAIL PROTECTED]>
ICQ: blashyrkh #2361802
Jabber: [EMAIL PROTECTED]
signature.asc
Description: Esta parte del mensaje está firmada digitalmente
nfusion to Eclipse users (and users of other IDEs).
Cheers,
--
Javier Kohen <[EMAIL PROTECTED]>
ICQ: blashyrkh #2361802
Jabber: [EMAIL PROTECTED]
signature.asc
Description: Esta parte del mensaje está firmada digitalmente
The ADB binding seems
to handle this gracefully, as I use it for another webservice with no
problems.
I guess the workaround would be to use synchronous calls for now and
wrap them myself in a Runnable.
Thanks,
--
Javier Kohen <[EMAIL PROTECTED]>
ICQ: blashyrkh #2361802
Jabber: [EMAIL PROTE
MD64, compared to
i386); etc.
You can expect the 64-bit version of a vendor's compiler to generate the
exact same bytecode (.class, .jar, whatever) than its 32-bit
counterpart. The compiler just turns your source code into platform
*independent* bytecode.
> On 1/8/07, Javier Kohen <
> On 1/8/07, Javier Kohen <[EMAIL PROTECTED]> wrote:
> El lun, 08-01-2007 a las 15:47 -0600, vamsee movva escribió:
> > Hello all,
> > I am new to axis, i have to work on 64-bit linux
> machine,
> &g
no 64-bit version, it just works
on a 64-bit platform, assuming there is a Java VM for it.
--
Javier Kohen <[EMAIL PROTECTED]>
ICQ: blashyrkh #2361802
Jabber: [EMAIL PROTECTED]
signature.asc
Description: Esta parte del mensaje está firmada digitalmente
L PROTECTED]>
> To:
> Sent: Friday, December 29, 2006 10:40 AM
> Subject: WSDL2Java
>
>
> > Does anyone know if it is possible to use WSDL2Java to process two WSDL
> > files into one application? If I have to build a single server and have
> > multipe WSDL t
hat character if you want to keep your XML "human-readable."
Greetings,
--
Javier Kohen <[EMAIL PROTECTED]>
ICQ: blashyrkh #2361802
Jabber: [EMAIL PROTECTED]
signature.asc
Description: Esta parte del mensaje está firmada digitalmente
.SOAPFaultImpl.getCode(SOAPFaultImpl.java:101)
> at
> org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:312)
> at example.BankServiceStub.withdraw(BankServiceStub.java:173)
> at example.BankClient.main(BankClient.java:59)
T
= new MessageContext();
> MessageContext resp =
> opClient.getMessageContext(WSDLConstants.MESSAGE_LABEL_IN_VALUE);
Given that you have an out-only operation, and by looking at the Javadoc
for the WSDLConstants class, I'd think you need to pass
MESSAGE_LABEL_OUT_VALUE instead.
Greetings,
--
Javi
SAGE_LABEL_IN_VALUE);
} catch (AxisFault f) {
// TODO handle faults here
}
> Javier Kohen wrote:
> > El jue, 14-12-2006 a las 23:09 +0200, Schalk Neethling escribió:
> >
> >> Hi there everyone,
> >>
> >> My apologies beforehand for the large amou
te
the whole envelope and use the OperationClient interface instead to run
the operation. I can give you skeleton code to do that, in case you need
it, it's only slightly more complex than the above.
Greetings,
--
Javier Kohen <[EMAIL PROTECTED]>
ICQ: blashyrkh #2361802
Jabber: [EMAIL PROTECTED]
signature.asc
Description: Esta parte del mensaje está firmada digitalmente
;
AuthenticationFailed
Authentication Failed
the content
Here follow the parts of the WSDL that deal with the fault:
First the XSD:
Then the WSDL itself:
roduces the result I need. So far my attempts haven't
been successful, so I'm pleading here for help.
> > -Original Message-
> > From: Javier Kohen [mailto:[EMAIL PROTECTED]
> > Sent: Tuesday, December 05, 2006 8:16 PM
> > To: axis-user@ws.apache.org
>
ting the WSDL on top of the messages, so I have some
freedom in how I do it.
Thanks for your suggestion, it seems I'll end up following it.
> -Original Message-
> From: Javier Kohen [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, December 05, 2006 8:16 PM
> To: axis-user@ws.
it's usually nice enough to allow
us puny humans to reformat it to our will in order to be able to scan
through it more easily.
Greetings,
--
Javier Kohen <[EMAIL PROTECTED]>
ICQ: blashyrkh #2361802
Jabber: [EMAIL PROTECTED]
signature.asc
Description: Esta parte del mensaje está firmada digitalmente
s no way I
can have them change the definition or the implementation.
Thanks in advance,
--
Javier Kohen <[EMAIL PROTECTED]>
ICQ: blashyrkh #2361802
Jabber: [EMAIL PROTECTED]
signature.asc
Description: Esta parte del mensaje está firmada digitalmente
, so I can't work from there either.
Thanks in advance,
--
Javier Kohen <[EMAIL PROTECTED]>
ICQ: blashyrkh #2361802
Jabber: [EMAIL PROTECTED]
signature.asc
Description: Esta parte del mensaje está firmada digitalmente
32 matches
Mail list logo