object graph.
If you feed it an unexpected XML structure, it will barf. That's not
the same a validation, though. Is it appropriate to check for valid
nulls during data binding? Enumerations? Regular expression formatting
constraints? Maybe. But where do you draw the line?
Anne
On 7/12/06, Doug B
Do you get OOM on a single request? Or only eventually after handling
many requests? Are you on the latest fixpacks of WebSphere? Axis
should run fine under it as far as I know.
Doug
On 7/12/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Hello,
what can we do to run Axis on Websphere 5.1.
. They will not be Java.
Best Regards,
Benjamin Fam
On 7/10/06, Doug B [EMAIL PROTECTED] wrote:
warning: long, best practice questions to follow
Interesting to hear you say that, Anne. I've been on a
multi-year
quest to get automatic, fast validation out of a Web
sending only one message to Axis.
Axis 1.2 works fine on Axis but Axis 2.0 doesn't work (wsdl4j conflict).
Tanks in advance
- Original Nachricht
Von: Doug B [EMAIL PROTECTED]
An: axis-user@ws.apache.org
Datum: 12.07.2006 21:19
Betreff: Re: Axis on Websphere (Out of memory error
warning: long, best practice questions to follow
Interesting to hear you say that, Anne. I've been on a multi-year
quest to get automatic, fast validation out of a Web Services engine.
Conceptually, it always seemed like the right approach (especially
for Document-Literal). If you're having to
/28/06, Doug B [EMAIL PROTECTED] wrote:
Sigh. I changed our WSDL Schema to use a naming convention that I
thought would work with Axis' current default behaviour on the server
side, and it caused its own issues. Namely, apparently 4 of my 5
operation signatures now meet all Axis' criteria
Sigh. I changed our WSDL Schema to use a naming convention that I
thought would work with Axis' current default behaviour on the server
side, and it caused its own issues. Namely, apparently 4 of my 5
operation signatures now meet all Axis' criteria for wrapped style,
but one does not. So
uses the WSDD (not the WSDL) to figure out how to dispatch the request. If the information isn't in there, Axis can't figure it out.
AnneOn 6/26/06, Doug B
[EMAIL PROTECTED] wrote:
Hmmm... so it turns out the options he can specify in his JBoss environment correspond to those on the java2wsdl tool. -T
.
SOAPAction isn't particularly useful, and it actually goes away in SOAP 1.2.Anne
On 6/27/06, Doug B
[EMAIL PROTECTED] wrote:Interesting. So does the java2wsdl -A option do anything at all? Sorry if I'm just being thick here, but something just doesn't seem right when the only artifact required for defining
the
intent of a message is carried in the envelope.
Regards,AnneOn 6/27/06, Doug B
[EMAIL PROTECTED] wrote:
But I'm trying to go the other direction. I don't want to have to run java2wsdl at all. I want to handwrite the WSDL and use that as the contract for both the client and the server. I want
,
Doug B [EMAIL PROTECTED] wrote:
Thanks again, Anne. I had read that first BP section, but not really understanding the implications until some of this discussion. It makes more sense now. I did try with Axis 1.3, and it does the same thing, so it must be something I'm just not quite grasping. But I'm
not quite right.
Anne
On 6/27/06, Doug B [EMAIL PROTECTED] wrote:
Thanks again, Anne. I had read that first BP section, but not really
understanding the implications until some of this discussion. It makes more
sense now.
I did try with Axis 1.3, and it does the same thing, so it must
://atmanes.blogspot.com/2005/03/wrapped-documentliteral-convention.htmlAnneOn 6/25/06,
Doug B
[EMAIL PROTECTED] wrote:Thanks, Anne. That makes sense and looks like a simple solution.
Best I can tell, the WS-I Basic Profile does not recommend or even mention wrapped Document-Literal, does it? Plus, from reading
doi:SuccessfulCompletionRequest QName maps to the method SuccessfulCompletionOperation, Axis doesn't know how to handle the request and returns an error of No such operation.
You haven't supplied any information about the .NET environment, so I can't tell you why it miraculously worked.Anne
On 6/26/06, Doug B
[EMAIL
, but some of it doesn't.
Thanks again for your patient instruction.DougOn 6/26/06, Doug B [EMAIL PROTECTED] wrote:
I'm also discovering that my Axis customer is having to do some intermediate step where he generates code from our WSDL but can't find any deployable artifacts until he takes some other steps
We're doing a contract-first implementation with a customer, using Document-Literal from handwritten WSDL and Schema. We are the client and our customer the server. The Schema has elements (and types) defined for each request and response message, and the WSDL uses single elements for each message
=doi:SuccessfulRenewalRequest/Anne
On 6/25/06,
Doug B [EMAIL PROTECTED] wrote:
We're doing a contract-first implementation with a customer, using Document-Literal from handwritten WSDL and Schema. We are the client and our customer the server. The Schema has elements (and types) defined for each request
17 matches
Mail list logo
