Bug 3113 - Processing in the compact dirs produces output depending on JVM
: Processing in the compact dirs produces output depending on JVM
Status: NEW
: Java WS Core
globus_wsrf_core
: unspecified
: PC Linux
: P3 minor
: ---
Assigned To:
:
:
:
:
  Show dependency treegraph
 
Reported: 2005-04-08 14:05 by
Modified: 2007-09-12 16:38 (History)


Attachments


Note

You need to log in before you can comment on or make changes to this bug.


Description From 2005-04-08 14:05:49
I am seeing different wsdl being generated when running with 1.3.1 vs running
with 1.4.2. I tried adding the core endorsed dir when running the commands
(thinking it might have to do with different xerces versions, but that didn't
make a difference). Needs more investigation.
------- Comment #1 From 2005-04-09 22:12:15 -------
How exactly different? I think I was just seeing the differences in ordering 
which might be related to using a hashtable and iterating over it.
------- Comment #2 From 2005-04-10 10:38:26 -------
The differences were in ordering, so maybe this just means that I can't use a
hashtable for things like RPs (which I think is the only thing I touch where
ordering matters).

/Sam
------- Comment #3 From 2005-11-23 19:53:45 -------
I looked into this a bit more closely and I think the problem is really in the 
WSDL library itself. It stores things such as faults, port types, operations, 
etc. in a hashtable so the order is never predicitable.
------- Comment #4 From 2007-09-12 16:38:28 -------
Reassigning to current wsrf developer to close/fix as appropriate