DO NOT REPLY [Bug 10193] - re: attributes in inherited classes should not be included

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_b

DO NOT REPLY [Bug 10193] - re: attributes in inherited classes should not be included

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_b

Re: SOAP 1.2, GET, and Axis

Actually, let me put this another way ... On Wed, Jul 03, 2002 at 05:49:43AM -0400, Sam Ruby wrote: > I just want to note that at some point, many developer don't want to > think in terms of HTTP or SOAP, but rather in terms like > getQuantityInStock(PartNumber="123"). Are you sure it's that a

RE: [PATCH] RE: Is this a bug in serialization? Fixed And Committed

John, John Thanks for the patch! I committed the code to fix the problem. I used a different approach than your patch. Please read the commit and verify. I also added your testcase. Thanks for your help identifying and fixing this problem. Rich 'Shirley' Scheuerle IBM WebSphere & Axis We

cvs commit: xml-axis/java/test/wsdl/multiref Main.java

scheu 2002/07/03 15:28:13 Modified:java/src/org/apache/axis/encoding SerializationContextImpl.java java/test/encoding PackageTests.java java/test/wsdl/multiref Main.java Added: java/src/org/apache/axis/utils IdentityHashMap

RE: cvs commit: xml-axis/java/src/org/apache/axis/description Ser viceDesc.java

Really? Static's are OK? Who knew? :-) OK, then we should back out my fix and filter for the Skeleton interfaces. I am going on vacation now... -- Tom Jordahl -Original Message- From: Glen Daniels [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 03, 2002 5:12 PM To: '[EMAIL PROTECTE

RE: cvs commit: xml-axis/java/src/org/apache/axis/description ServiceDesc.java

Hm - static methods are perfectly fine to include in a Web Service... A better fix would be to notice the Skeleton class while introspecting, and skip it. I've made this fix in my sandbox, and can check it in if desired. --Glen > -Original Message- > From: [EMAIL PROTECTED] [mailto:[

cvs commit: xml-axis/java/src/org/apache/axis/components/bytecode Builtin.java ParamReader.java

tomj2002/07/03 14:08:11 Added: java/src/org/apache/axis/components/bytecode Builtin.java ParamReader.java Log: A first cut at a built-in bytecode reader to remove dependancies on external jar files (tt-bytecode, BCEL, etc).. This isn't turned on

cvs commit: xml-axis/java/src/org/apache/axis/description ServiceDesc.java

tomj2002/07/03 13:57:14 Modified:java/src/org/apache/axis/description ServiceDesc.java Log: Fix a problem with Skeletons and WSDL generation: The getOperationDescs() and getOperationDescByName() APIs were showing up in WSDL when skeletons were turned on. Fix: Filter o

Tom Jordahl on vacation

FYI - I will be on vacation till July 17, 2002. -- Tom Jordahl Macromedia

Re: WSDL Ant Tasks

They're not, but I'd sure like 'em to be. Or at least in a separate tools jar file - James M Snell/Fresno/IBM Web services architecture and strategy Internet Emerging Technologies, IBM 544.9035 TIE line 559.587.1233 Office 919.486.0077 Voice Mail [EMAIL PROTECTED] Progr

cvs commit: xml-axis/java/src/org/apache/axis/wsdl/fromJava Types.java

gdaniels2002/07/03 13:22:42 Modified:java/src/org/apache/axis/wsdl/fromJava Types.java Log: Merge fix from beta-3 - don't write Holder types to schema, write the held type. Revision ChangesPath 1.43 +6 -3 xml-axis/java/src/org/apache/axis/wsdl/fromJava/Types.

cvs commit: xml-axis/java/samples/attachments attachdeploy.wsdd

gdaniels2002/07/03 13:21:43 Modified:java/src/org/apache/axis/deployment/wsdd WSDDDeployableItem.java java/test/functional TestJAXRPCSamples.java java/samples/stock ComInfoService.java java/samples/attachments attachde

Re: WSDL Ant Tasks

That's a much better idea ;-) ... at the very least, I'd like the ant tasks to become a more official part of the code. - James M Snell/Fresno/IBM Web services architecture and strategy Internet Emerging Technologies, IBM 544.9035 TIE line 559.587.1233 Office 919.486.0077 Voi

cvs commit: xml-axis/java/src/org/apache/axis/description ServiceDesc.java

gdaniels2002/07/03 13:02:07 Modified:java/src/org/apache/axis/wsdl/fromJava Tag: beta-3 Types.java java/src/org/apache/axis/description Tag: beta-3 ServiceDesc.java Log: Simple fix for bug 10103. Don't write Holder

Re: WSDL Ant Tasks

I didn't think that the ant tasks were in the distributed axis jar. Rich 'Shirley' Scheuerle IBM WebSphere & Axis Web Services Development 512-838-5115 (IBM TL 678-5115) Richard Sitze/Charlotte/IBM@IBMUS 07/03/2002 02:46 PM Please respond to axis-dev To: [EMAIL PROTECTED]

cvs commit: xml-axis/java/samples/attachments attachdeploy.wsdd

gdaniels2002/07/03 12:57:48 Modified:java/src/org/apache/axis/deployment/wsdd Tag: beta-3 WSDDDeployableItem.java java/test/functional Tag: beta-3 TestJAXRPCSamples.java java/samples/stock Tag: beta-3 ComInfoService.java

Re: WSDL Ant Tasks

Any chance we can separate core runtime function from tooling and support, including ant tasks, into different jar files? *** Richard A. Sitze[EMAIL PROTECTED] CORBA Interoperability & WebServices IBM WebSphere Development James M Snell/Fresno/I

RE: WSDL2Java: generated client stub and performance issues

You are absolutely right.   Do we believe that sharing a Stub across threads is a valid use case?    Does JAX-RPC say anything about this?  I sort of think it should NOT be supported, but since we support it now...   -- Tom Jordahl Macromedia   -Original Message-From: [EMAIL PROTE

RE: [PATCH] RE: Is this a bug in serialization?

John, I am getting encoding unit test failures with this change. I'll be on vacation after today, but Rich S. has offered to work with you on this. Here is the first failure I get: java.io.IOException: Can't serialize a java.lang.String with a DataSerializer. at test.encoding.D

RE: Property Descriptor Caching

+1 -- Tom Jordahl Macromedia -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 03, 2002 3:21 PM To: [EMAIL PROTECTED] Subject: Property Descriptor Caching Every time a Bean/Simple Serializer/Deserializer is invoked, it constructs a PropertyDe

Property Descriptor Caching

Every time a Bean/Simple Serializer/Deserializer is invoked, it constructs a PropertyDescriptor array (and possibly PropertyDescriptor Map). I have code in my sandbox that should improve performance. I added the following two methods to TypeDesc, which get and cache the array and map: public

RE: [PATCH] RE: Is this a bug in serialization?

I forgot the other diff for PackageTests.java. john diff.out Description: Binary data

RE: [PATCH] RE: Is this a bug in serialization?

With a test! Thanks John. Watch for the commit shortly. -- Tom Jordahl Macromedia -Original Message- From: John Gregg [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 03, 2002 2:29 PM To: [EMAIL PROTECTED] Subject: [PATCH] RE: Is this a bug in serialization? Here's fix to the seri

cvs commit: xml-axis/java/test/wsdl/addrNoImplSEI AddressBookTestCase.java

rsitze 2002/07/03 11:47:09 Modified:java/test/functional TestMessageSample.java TestBidBuySample.java TestProxySample.java TestJAXRPCSamples.java TestElementSample.java TestTCPTransportSample.java TestEchoSample.ja

WSDL Ant Tasks

Any chance the WSDL Ant Tasks could be moved into the main code base? Perhaps into an org.apache.axis.wsdl.tasks package? - James M Snell/Fresno/IBM Web services architecture and strategy Internet Emerging Technologies, IBM 544.9035 TIE line 559.587.1233 Office 919.486.0077

[PATCH] RE: Is this a bug in serialization?

Here's fix to the serialization problem Naresh had. To summarize the problem, in cases where two distinct objects for which equals() returned true and hashCode() returned the same value, only one "instance" would appear in the serialized output. The correct result was for 2 instances to appear i

RE: WSDL2Java: generated client stub and performance issues

Synchronizing each method is insufficient. Assume you synchronize each method and use one Call object. Follow this scenario: - Thread T1 sets the endpoint to X - Thread T2 sets the endpoint to Y - T1 calls stub.a synchronously but setting the endpoint is outside any synchronization so it calls T2

cvs commit: xml-axis/java/test/wsdl/extensibility ExtensibilityQueryBindingImpl.java

rsitze 2002/07/03 11:19:29 Modified:java/test/wsdl/extensibility ExtensibilityQueryBindingImpl.java Log: Hmm.. somehow this got missed. Updated for component reorg. Revision ChangesPath 1.9 +3 -3 xml-axis/java/test/wsdl/extensibility

RE: WSDL2Java: generated client stub and performance issues

I believe the code is the way that it is to allow the use of a Stub object from multiple threads, each having its own Call object. It is on my TODO list to revisit the way this all works because: - I believe that synchronizing the methods of the Stub would provide for the thread safety that

cvs commit: xml-axis/java build.xml

rsitze 2002/07/03 11:14:46 Modified:java build.xml Log: Fixed bytecode build paths, for reorganize pluggable component under org.apache.axis.components.*. Revision ChangesPath 1.157 +3 -3 xml-axis/java/build.xml Index: build.xml

cvs commit: xml-axis/java/src/org/apache/axis/components/bytecode - New directory

rsitze 2002/07/03 10:50:01 xml-axis/java/src/org/apache/axis/components/bytecode - New directory

cvs commit: xml-axis/java/src/org/apache/axis/components/logger - New directory

rsitze 2002/07/03 10:50:02 xml-axis/java/src/org/apache/axis/components/logger - New directory

cvs commit: xml-axis/java/src/org/apache/axis/components - New directory

rsitze 2002/07/03 10:50:00 xml-axis/java/src/org/apache/axis/components - New directory

cvs commit: xml-axis/java/src/org/apache/axis/components/compiler - New directory

rsitze 2002/07/03 10:50:01 xml-axis/java/src/org/apache/axis/components/compiler - New directory

RE: wsdl2Java proxy classes and SOAP headers

Just to clarify to situation Somehow, the original response about my implementation of soap:header support was not that positive... After cleaning it up a bit and clarifying the situation I got rather good feedback from the committers regarding getting it in even if the patch was not perfect

Re: client-side global chain

one example use of client-side chaining that is service specific is to handle client-side infrastructure. So, if client A wants to use service X, and the WSDL for service X indicates (by some means) that the input message of any/all operations must be signed using a digital signature, then we have

Re: client-side global chain

We use it to have add a handler that will add a security header into the message - but just for certain services, not all of them. Of course, the other answer is: because it's there. LOL! (sorry) -Dug Please respond to [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: client-side

Re: client-side global chain

Doug, A naive question... >Let's say someone wants to add a client-side handler >that's service specific. What might they hope to achieve by doing this? A specific scenario would help me. Glyn

DO NOT REPLY [Bug 10443] New: - HttpServletRequest.getUserPrincipal() call from ServletAuthenticatedUser

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_b

client-side global chain

Looking at the client-side of things for a moment... Let's say someone wants to add a client-side handler that's service specific. In the WSDD file they need to specify the service name as the QName of the 1st body element. This is, or could be I guess, contradictory to how things will work on t

RE: cvs commit: xml-axis/java/test/wsdl/extensibility ExtensibilityQueryBindingImpl.java

Sorry that I spent so much time writing up a commit message. I have spent a lot of time working on bugs in the meta data that were due to inconsistent state. Adding some very simple assertion checks like the one I added to setJavaType() are necessary to prevent future bugs. I don't see anyt

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

Glen/Costin I understand that the cost is LOW (we are using 'static Log' now). I also understand that I've introduced one more level of abstraction. I understood Axis to be both a frame work and a SOAP solution. My focus is the framework, and integrating that framework into/with other products

RE: Is this a bug in serialization?

I'm working on a fix right now. I think fixing it is easy-- writing the test is a little more work. john -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of [EMAIL PROTECTED] Sent: Wednesday, July 03, 2002 9:03 AM To: [EMAIL PROTECTED] Subject: RE: Is this

RE: Is this a bug in serialization?

If serialization is using the hashcode method to determine whether two references are the same object, this is definitely a bug. Please open a Bugzilla defect. The hashcode and equals methods are great for what they were designed to do...but no more. The generated equals method defines equal

Re: SOAP 1.2, GET, and Axis

On Wed, Jul 03, 2002 at 05:49:43AM -0400, Sam Ruby wrote: > Mark Baker wrote: > > You guys are losing me. > > OK, I will try to speak in one syl a ble words this time. [*] Hey old man, don't taunt the n00b! > > Sam's suggestion to punt the retrieval of the response is fine from > > this POV, bu

RE: error in wsdd processing

On it, thanks!   --G -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]Sent: Wednesday, July 03, 2002 8:54 AMTo: [EMAIL PROTECTED]Subject: error in wsdd processingChanging the stockquote wsdd file so it looks like:   xmlns:java="http://xml.apache.org/

error in wsdd processing

Changing the stockquote wsdd file so it looks like:    xmlns:java="http://xml.apache.org/axis/wsdd/providers/java">                                           The key changes are: - defined a "checks" chain - use that chain in the request flow of my service This will fail i

RE: SOAP 1.2, GET, and Axis

> > Well, on the client side, it is our job to do whatever triggers the > > generation of the response, receive it, and then hand it up to the > > user in whatever form they like (i.e. SOAPEnvelope for doc/lit, > > perhaps a deserialized Object for RPC). In the current case, "what > > trigg

Re: UDDIUtil and WSDLUtil

Title: RE: UDDIUtil and WSDLUtil Mark   Are you using WSDL4J?   Paul - Original Message - From: Volkmann, Mark To: Volkmann, Mark ; '[EMAIL PROTECTED]' ; '[EMAIL PROTECTED]' ; 'Suresh Marella' ; 'Christian Gründemann' ; 'Jean-Marc Taillant' ; 'Arulazi D' ; 'Sam' ; 'Axis Help

Re: SOAP 1.2, GET, and Axis

Mark Baker wrote: > You guys are losing me. OK, I will try to speak in one syl a ble words this time. [*] > A developer has to know that a GET is being performed, the same way > they have to know that any method is being invoked, because it has > meaning specific to the task they're trying to ac