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

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

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

Objects instance variable to SerializationContextImpl and populates it under certain conditions but never uses it otherwise. It looks like someone just got sidetracked and didn't finish his thought. john -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf

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?

is the usual definition.  Are they equal if they conceptually occupy the same spot in a graph of instances?  Are they equal if their persistent ids are the same?   john [John Gregg]  -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Tom JordahlSent:

RE: bugfixes

Glyn On Sat afternoon dims made some changes to SOAPHeader that included some of the code I wrote. That change is what's in 1.45 and probaly is why the diff against 1.43 has trouble. One of the changes I made was to eliminate duplicate code from getHeadersByActor() and findHeaderElements(). Di

handling java.lang.Error

Hi all. I checked the developer's guide but didn't see an answer. I tend to see a lot of catch clauses that specify either AxisFault or Exception but not Throwable. Is there a particular reason for this? I tend to put a catch (Throwable t) as my last line of defense before my app sends a respo

RE: [PATCH] for RPCProvider.java

Of Davanum Srinivas Sent: Wednesday, June 26, 2002 3:10 PM To: [EMAIL PROTECTED] Cc: 'John Gregg' Subject: RE: [PATCH] for RPCProvider.java Tom, I added some testcases. Can you please review those too? Thanks, dims

[PATCH] for RPCProvider.java

Hi all, I discovered the hard way that RPCProvider.java doesn't like comma-delimited allowed methods even though the docs claim it's ok. Sure enough, the only delimiter specified in the StringTokenizer is a space. I made the change and did some minor testing. I tested a space, a comma, and a c

RE: build javadocs failure

Glad I didn't delete 1.3.1 yet. Thanks john -Original Message- From: Davanum Srinivas [mailto:[EMAIL PROTECTED]] Sent: Monday, June 24, 2002 6:51 PM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: build javadocs failure John, This is a JDK1.4 bug Thanks, dims

build javadocs failure

I'm getting "error: cannot read: org.apache.axis.providers.java" when trying to create javadocs for the Axis mainline in CVS. I also had the problem with the previous cvs update that I did about a week ago. Javadoc seems to think the package ending in ".java" is really a source file. I've attac

ClassCastException and handlers

Hi all. Perhaps you saw my note to axis-user about a handler I was trying to write. I created a handler that was a subclass of javax.xml.rpc.handler.GenericHandler but WSDDDeployableItem expects it to be org.apache.axis.Handler. Consequently I was getting a ClassCastException on line 355 of vers