Re: WSDL Aware Runtime

Do you have some idea of the overhead of making the runtime WSDL aware? Maybe the additional function is worth *some* performance overhead, but clearly we don't want to cripple performance, e.g. by introducing file I/O into service requests where there was none previously, for a small functional i

RE: WSDL Aware Runtime

IMO, the Axis engine desperately needs a "service metadata" abstraction, which I've been making noises about for a long time. I don't think this should be tightly bound to WSDL, though I do think we should clearly be able to read WSDL into a ServiceDescription (assuming that's what it gets ca

[GUMP] Build Failure - Axis

This email is autogenerated from the output from: Build results exceed maximum length. Please see URL above for details. Last

Re: [GUMP] Build Failure - Axis

Ouch! Do we have a multithreading problem? Has anyone else seen this failure? I suppose we should debug this if we find the time. Russell Butek [EMAIL PROTECTED] Sam Ruby/Raleigh/IBM@IBMUS on 02/20/2002 07:46:32 AM Please respond to [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: [

RE: WSDL Aware Runtime

Glen wrote: >... we can do a good job with defining clean abstractions around what we want, >and then map that to whichever version of WSDL we're using in the future ... +1 Glyn

RE: Clash test

> I'm still not sure I understand the problem with the clash test. The > testcase is calling "void sharedName(int)". That method DOES > exist on all > the generated files: the interface, the skeleton, the impl. It is > overloaded: "void sharedName(int)", "int sharedName()", "void > sharedNa

RE: [GUMP] Build Failure - Axis

> Trying to override old definition of task runaxisfunctionaltests Anyone have a clue about this? I see this all the time, and haven't dived in to figure it out yet. --Glen

RE: WSDL Aware Runtime

I agree with Glen that you should use an abstraction: at the very least you want to support both WSDL and XML Schema. Anne > -Original Message- > From: Glen Daniels [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, February 20, 2002 8:37 AM > To: '[EMAIL PROTECTED]' > Subject: RE: WSDL Aware

cvs commit: xml-axis/java/src/org/apache/axis/wsdl/toJava JavaStubWriter.java

butek 02/02/20 05:55:20 Modified:java/src/org/apache/axis/client Stub.java java/src/org/apache/axis/wsdl/toJava JavaStubWriter.java Log: Added set/getTimeout to stubs since we've got those methods on Call. Revision ChangesPath 1.4 +15 -0 xml-ax

RE: WSDL Aware Runtime

+1 for "service metadata" abstraction It will also resolve this concern R J Scheuerle Jr wrote: >So everything is fine if all services send arrays over with type >="soapenc:Array". But if a service >sends over a more specific type="ns:ArrayOfFoo", then the client

RE: WSDL Aware Runtime

+1 to all of the comments. I don't have the bandwidth to start doing any work. I just want some comments. So what I am hearing is: 1) The runtime (client and server) should be "xml" aware. This would be a good improvement. 2) This modeling should be an abstraction that does not directly depen

cvs commit: xml-axis/java/test/wsdl/multithread MultithreadTestCase.java

glyn02/02/20 07:07:28 Modified:java/test/wsdl/multithread MultithreadTestCase.java Log: Capture stack trace for multithreaded testcase failures. Revision ChangesPath 1.5 +10 -0 xml-axis/java/test/wsdl/multithread/MultithreadTestCase.java Index: Multith

cvs commit: xml-axis/java/src/org/apache/axis/client Service.java

butek 02/02/20 06:11:17 Modified:java/src/org/apache/axis/client Service.java Log: These fields are made transient for Serializable use. Revision ChangesPath 1.43 +3 -3 xml-axis/java/src/org/apache/axis/client/Service.java Index: Service.java =

Re: [GUMP] Build Failure - Axis

I can't tell where the IllegalStateException originates from as the Gump log doesn't show the stack trace of that exception. However, I came across some non-threadsafe code in AddressBookSOAPBindingStub: if (firstCall) { firstCall = false; (generated by org.apache.axis.wsdl.toJava.JavaStubW

RE: Heads-up / opinions? - BCEL -> tt-bytecode

HI! I tested the latest build and the tt-bytecode library seems to be extremely slow. It takes about 30 seconds to read information from some bigger classes on my machine (500 MHz). During this time, java.exe consumes all available CPU time. This wasn't the case with bcel. The class was comp

RE: [GUMP] Build Failure - Axis

Wile I have had my problems with the multi-thread test (sinced fixed), I have never seen this error. What does it mean: "ava.lang.IllegalStateException"? -- Tom Jordahl -Original Message- From: Russell Butek [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 20, 2002 8:49 AM To: [EM

cvs commit: xml-axis/java/test/wsdl/interop3/groupE - New directory

glyn02/02/20 05:40:31 xml-axis/java/test/wsdl/interop3/groupE - New directory

cvs commit: xml-axis/java/test/wsdl/interop3/groupE/client - New directory

glyn02/02/20 05:40:58 xml-axis/java/test/wsdl/interop3/groupE/client - New directory

Re: [GUMP] Build Failure - Axis

I'll fix this stub code. Thanks, Glyn. Hopefully that's the problem, but I wouldn't be surprised if there are more. Russell Butek [EMAIL PROTECTED] Glyn Normington/UK/IBM@IBMGB on 02/20/2002 09:09:48 AM Please respond to [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: [GUMP] Bui

cvs commit: xml-axis/java/test/wsdl/interop3/groupE/client InteropTestDocLitServiceTestCase.java InteropTestListServiceTestCase.java InteropTestRpcEncServiceTestCase.java

glyn02/02/20 05:46:09 Modified:java build.xml java/test/wsdl Wsdl2javaTestSuite.xml Added: java/test/wsdl/interop3/groupE Interop3GroupE.xml InteropTestDocLit.java InteropTestDocLitImpl.java InteropTestList.j

typemapping on service rather than Call (was: Re: [GUMP] Build Failure- Axis)

This bit of code brings up an issue we've talked about, but I don't think resolved. The type mapping registration should really be done on the service, not on the call object. There could be many call objects created from a service that all use the same registry and it's a lot of overhead to reg

Re: [GUMP] Build Failure - Axis

Oops, I guess that's my fault. I re-organized my build.xml and I do now create the xmlsec.jar in a new location: OLD: xml-security/xmlsec.jar NEW: xml-security/build/xmlsec.jar > dropping /home/rubys/jakarta/xml-security/xmlsec.jar from path as it > doesn't exist Guess that's the problem. Chr

RE: [GUMP] Build Failure - Axis

Glen, Could it just be that build.xml does two ant calls to build_functional_tests and the second one sees that particular ant task is already defined? Glyn

RE: typemapping on service rather than Call (was: Re: [GUMP] Build Failure - Axis)

A big +1 to putting the type mapping registry on the service -- Tom Jordahl -Original Message- From: Russell Butek [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 20, 2002 10:40 AM To: [EMAIL PROTECTED] Subject: typemapping on service rather than Call (was: Re: [GUMP] Build Failure

RE: WSDL Aware Runtime

Glen wrote: >> IMO, the Axis engine desperately needs a "service metadata" abstraction, which I've been making noises about for a long time. I don't think this should be tightly bound to WSDL, though I do think we should clearly be able to read WSDL into a ServiceDescription (assuming that's wha

RE: [GUMP] Build Failure - Axis

That exception is thrown in hundreds of places inside the JDK and can mean any number of things. The message in the exception (which doesn't appear in the Gump log) would tie down the reason the exception was thrown except when it is empty, which it is in a number of cases when it is thrown by it

cvs commit: xml-axis/java/src/org/apache/axis/wsdl/toJava JavaStubWriter.java

butek 02/02/20 08:49:53 Modified:java/src/org/apache/axis/client Stub.java java/src/org/apache/axis/wsdl/toJava JavaStubWriter.java Log: Make type mapping registration in the stubs thread safe. Revision ChangesPath 1.5 +16 -0 xml-axis/java/src/

cvs commit: xml-axis/java/test/wsdl Java2WsdlAntTask.java Wsdl2javaAntTask.java Wsdl2javaTestSuite.xml

scheu 02/02/20 09:17:36 Modified:java/src/org/apache/axis/utils resources.properties java/src/org/apache/axis/wsdl Java2WSDL.java WSDL2Java.java java/src/org/apache/axis/wsdl/toJava Emitter.java JavaWriterFactory.java WriterFactory

cvs commit: xml-axis/java/test/session TestSimpleSession.java

gdaniels02/02/20 10:59:22 Modified:java build.xml java/samples/echo TestClient.java java/samples/proxy ProxyService.java java/samples/security ClientSigningHandler.java LogHandler.java java/samples/u

FW: WSDD for a Stateful EJB

It was mentioned that Axis doesn't yet support Stateful EJB's. This would be a nice feature, one that Apache SOAP 2.2 already had. Thanks, Paul -Original Message- From: Carl Woolf [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 20, 2002 1:30 PM To: '[EMAIL PROTECTED]' Subject: RE:

Re: [AXIS - PATCH] More logging changes

Looks great! Thanks Richard. Could you explain why the extra jar file is needed. I can't seem to view diffs.txt. I am assuming that only the src tree is affected. (?) Russell or I will commit the patch once we get some +1's from the rest of the community. Thanks Rich Scheuerle XML & Web Ser

RE: [AXIS - PATCH] More logging changes

+1 These changes look good. I am a bit dubious about checking the comments for System.out.println's, but it might catch some cruft that shouldn't be checked in. -- Tom Jordahl -Original Message- From: Richard Sitze [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 20, 2002 12:28

+1 Make Richard Sitze A Committer

+1 to making Richard Sitze a committer. He just recently added the Axis logging api, and he will be working on additional Axis improvements (including performance monitoring). Rich Scheuerle XML & Web Services Development 512-838-5115 (IBM TL 678-5115)

Re: cvs commit: xml-axis/java/test/session TestSimpleSession.java

all-tests and functional-tests are both broken! Concerning: | 5. Remove the code which attempted to map an element QName as a type | QName - if we need to do type mapping via elements, there should be | a better way. I added this code. Seems reasonable to comment it out for now. Rich

cvs commit: xml-axis/java/src/org/apache/axis/message RPCElement.java

gdaniels02/02/20 12:22:07 Modified:java/src/org/apache/axis/message RPCElement.java Log: Make sure we set things up when not using introspected types! Revision ChangesPath 1.33 +3 -1 xml-axis/java/src/org/apache/axis/message/RPCElement.java Index: RPCEleme

RE: cvs commit: xml-axis/java/test/session TestSimpleSession.java

Sorry, tests should work now (I moved a clause and forgot to copy a couple of lines). --G > -Original Message- > From: R J Scheuerle Jr [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, February 20, 2002 3:13 PM > To: [EMAIL PROTECTED] > Subject: Re: cvs commit: xml-axis/java/test/session >

cvs commit: xml-axis/java/test/wsdl/roundtrip InvalidCompanyId.java InvalidTickerSymbol.java InvalidTradeExchange.java RoundtripPortType.java RoundtripTestServiceTestCase.java RoundtripTestSoapBindingImpl.java

scheu 02/02/20 12:41:14 Modified:java/src/org/apache/axis/wsdl/fromJava ClassRep.java Emitter.java MethodRep.java java/test/wsdl Wsdl2javaTestSuite.xml java/test/wsdl/roundtrip RoundtripPortType.java Roundtr

RE: [AXIS - PATCH] More logging changes

+1. I'm concerned about checking for System.out.println, too, but I've been talking with Richard Sitze about it and he's almost won me over. It's a philosophy thing. When I'm debugging, I use System.out.printlns all the time. I'd hate a test to fail while I'm debugging because of them. But in

RE: determination programmatically

Rich, Me and Chris are on the same team :). I have once suggested to reconcile Emitter and SOAP pipeline as far as handling default bean mappings (http://marc.theaimsgroup.com/?l=axis-dev&m=101320802717644&w=2) for making it simple to deploy a set of well defined java classes (those not result

RE: [AXIS - PATCH] More logging changes

Close.. :-) Actually, what I said was to use log.debug and leave log.info alone. The updated (soon to be checked in by Russell) integration guide spells out how to configure Log4J to turn debugging on/off by individual class (or package or...). IFF you can assure the community that your log.i

RE: +1 Make Richard Sitze A Committer

+1 -- Tom Jordahl -Original Message- From: R J Scheuerle Jr [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 20, 2002 2:52 PM To: [EMAIL PROTECTED] Subject: +1 Make Richard Sitze A Committer +1 to making Richard Sitze a committer. He just recently added the Axis logging api, and

cvs commit: xml-axis/java/src/org/apache/axis/message MessageElement.java

gdaniels02/02/20 20:01:48 Modified:java/src/org/apache/axis/message MessageElement.java Log: In case there isn't a deserialization context available when trying to string-ize a MessageElement (for instance, when the MessageElement has been dynamically created), just use whatever

cvs commit: xml-axis/java/test/encoding TestDOM.java TestSer.java

gdaniels02/02/20 20:28:27 Modified:java/src/org/apache/axis/encoding SerializationContextImpl.java java/src/org/apache/axis/message MessageElement.java RPCElement.java java/test/encoding TestDOM.java TestSer.j

RE: cvs commit: xml-axis/java/test/encoding TestDOM.java TestSer.java

Sorry about all the whitespace stuff in there, guys - I must have hit something inappropriate on my IDE. > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, February 20, 2002 11:28 PM > To: [EMAIL PROTECTED] > Subject: cvs commit: xml-axis/java/t