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.
Summary: | WSDL editor -JMS BC for Inbound request reposne configuration shows up as request for response consumer config | ||
---|---|---|---|
Product: | soa | Reporter: | ggenipudi <ggenipudi> |
Component: | JMS BC | Assignee: | Sujit Biswas <sujitbiswas> |
Status: | NEW --- | ||
Severity: | blocker | CC: | jalmero, jlautz, schmandt |
Priority: | P4 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | Windows Vista | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: | screen shot of error |
Description
ggenipudi
2008-09-29 18:00:06 UTC
Created attachment 70820 [details]
screen shot of error
Title of panel should match the Step of wizard. A Label issue. Same mismatch of heading tags are seen for outbound One way 3rd step Request connection configuration appears as Request configuration and Request publisher Configuration appears as Request configuration. Same for Inbound One way Request connection configuration appears as Request configuration Request Consumer Configuration appears as Request Configuration for Inbound Request response Request Connection Configuration appears as Request configuration Request Destination Configuration appears as Request configuration same for JMS BC solicited Read and Outbound Request Response windows. I'm seeing the same thing. Please help me understand this -- what is the workaround? it appears to me that this makes the one-way jms bindings useless or there a work around? if there is no workaround, imo this should be p1 or p2. Note that i'm trying to test many kinds of configurations in CASA, it's not possible to test if the bindings cannot be created....also if no workaround then the customer cannot create desired configurations so jms bc is dead on arrival imo Surely we are not expecting the customer to edit wsdl's to fix this? pls correct me if i'm wrong, thx. my mistake, my problem is a new bug see 151931, the binding created by the jms send operation cannot be used as an output operation in bpel editor. sorry for any confusion, there was more wrong with the binding than the labels, an input msg type was created for the output operation, which bpel editor rejects.... changing the priroty to p4, this is more to do having the most appropiate naming of the dialog/wizard |