Bugzilla – Bug 5682
Change name of topic in ws-gram currently known as RP_STATE
Last modified: 2007-11-22 23:15:04
You need to
before you can comment on or make changes to this bug.
In WS-GRAM the topic being subscribed to to get bundled information about
state, exit code, holding and fault has the same QName as the 'state'
resource property. The expectation for subscribing to that would be a
ResourcePropertyValueChangeNotification with a NewValues element containing
the value of the types:state RP that has changed. Because WS-GRAM packages
together several resource properties into a single notification, it should
publish a new Topic with a different name that includes those pieces.
I renamed the existing Topic. It's QName is now
I committed the change to a branch named ws-gram-bug5682
I didn't change the namespace yet. When the new job termination
code gets committed this should be done.
MJFS.createManagedJob() now also throws a TopicNotSupportedFaultType
in case someone refers to the old and no longer existing topic name
or to another non-existing topic name in the Subscribe element of the
createManagedJob element in a job submission.
Merged code from ws-gram-bug5682 to trunk. This includes
Java and C changes.