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 148657 - WSDL editor -JMS BC for Inbound request reposne configuration shows up as request for response consumer config
Summary: WSDL editor -JMS BC for Inbound request reposne configuration shows up as req...
Status: NEW
Alias: None
Product: soa
Classification: Unclassified
Component: JMS BC (show other bugs)
Version: 6.x
Hardware: All Windows Vista
: P4 blocker (vote)
Assignee: Sujit Biswas
Depends on:
Reported: 2008-09-29 18:00 UTC by ggenipudi
Modified: 2009-11-12 11:21 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

screen shot of error (39.76 KB, application/octet-stream)
2008-09-29 18:04 UTC, ggenipudi

Note You need to log in before you can comment on or make changes to this bug.
Description ggenipudi 2008-09-29 18:00:06 UTC
Using Glassfish ESB Build 200808290856, Create a WSDL using JMS BC and select Inbound request response and accept
defaults for request config and response config and click next notice in the next window as shown in the attachment it
is response consumer config but shows up as request configuration.
Comment 1 ggenipudi 2008-09-29 18:04:17 UTC
Created attachment 70820 [details]
screen shot of error
Comment 2 Jonelle Almero 2008-09-29 18:07:14 UTC
Title of panel should match the Step of wizard.  A Label issue.
Comment 3 ggenipudi 2008-09-29 18:19:13 UTC
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.

Comment 4 schmandt 2008-10-30 20:05:03 UTC
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.
Comment 5 schmandt 2008-10-31 01:39:10 UTC
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....
Comment 6 Sujit Biswas 2009-11-12 11:21:49 UTC
changing the priroty to p4, this is more to do having the most appropiate naming of the dialog/wizard