This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 92673 - editor for message textpart for JMSBC not working
Summary: editor for message textpart for JMSBC not working
Status: VERIFIED WORKSFORME
Alias: None
Product: xml
Classification: Unclassified
Component: WSDL Tools (show other bugs)
Version: 5.x
Hardware: All All
: P3 blocker (vote)
Assignee: issues@soa
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-01-17 10:43 UTC by pushpa
Modified: 2007-04-06 17:27 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description pushpa 2007-01-17 10:43:42 UTC
For JMSBC , wsdl is created with the default textpart as "Change me",
user can edit this from propertis window, but the new values are not getting 
saved.

Build details:20070116 gavotte build

Steps:
1.Create wsdl with JMSBC
2.Open wsdl editor & try editing saving the values for chamge me to the new 
value.
Comment 1 Shivanand Kini 2007-02-16 22:50:52 UTC
This has been fixed. Please verify
Comment 2 jlautz 2007-02-22 01:10:52 UTC
Still seen on Windows XP with EP Gavotte 070220_4 and JDK 1.5.0_10.

1. jms:message textPart attribute in source never changes from "change me", no
matter what you do in the WSDL view properties pane.

2. Also: jms:operation transaction attribute does not respond properly in the
Properties pane when I choose <Not Set>. It sets itself to NoTransaction instead
of removing the attribute from the source and unsetting the value in the
Properties pane.
Comment 3 Shivanand Kini 2007-02-27 03:30:04 UTC
I cannot reproduce the case #1, the text part is set when the part is chosen
from the drop down.

For 2., the default value is NoTransaction as per the JMS schema, unsetting the
value sets it to the default NoTransaction. Is this confusing? I can remove the
<Not Set> option, if there is a default specified.

James, do you want to comment on this behavior?
Comment 4 James Tran 2007-04-04 19:07:46 UTC
If Transaction is not defined then the bc assumes NoTransaction.  Indeed the
schema does specify NoTransaction as the default if the user chooses to define
Transaction. So whether Transaction is not defined or Transaction is defined as
NoTransaction, the behavior is the same.  You can remove the <Not Set> option if
this is confusing for the user.
Comment 5 jlautz 2007-04-06 17:27:32 UTC
Verified on Windows XP with Hula 070406_11 and JDK 1.6.0_1.

The jms:message textPart property is now set.

The jms:operation transaction property now has <Not Set> map to not specifying
the transaction attribute in the xml source. (Which makes more sense, at least
to me. :) )