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 128427 - CASA Editor - WSIT - Not able to modify the porttype
Summary: CASA Editor - WSIT - Not able to modify the porttype
Status: STARTED
Alias: None
Product: soa
Classification: Unclassified
Component: Composite Application (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Tientien Li
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-02-26 12:29 UTC by deepakhp
Modified: 2008-02-29 21:20 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
WSIT-AppCreation (2.50 KB, text/plain)
2008-02-26 12:30 UTC, deepakhp
Details
ChangingNameSpace (202.44 KB, image/jpeg)
2008-02-26 12:30 UTC, deepakhp
Details
ChangePort (39.68 KB, image/jpeg)
2008-02-26 12:31 UTC, deepakhp
Details
DummyPortType (34.97 KB, image/jpeg)
2008-02-26 12:31 UTC, deepakhp
Details

Note You need to log in before you can comment on or make changes to this bug.
Description deepakhp 2008-02-26 12:29:30 UTC
I'm testing WSIT client using the following NetBeans build from Sierra latest bits.
Product Version: NetBeans IDE Dev (Build 20080225050543)
Java: 1.6.0_04; Java HotSpot(TM) Client VM 10.0-b19
System: Windows XP version 5.1 running on x86;

Follow the steps provided in the attachment (WSIT-AppCreation.txt) to create WSIT service and client application.
In the Step 19 of creating client, I'm not able to modify the PortType to "TestNS:..PortType". It always shows as Dummy
port.
Comment 1 deepakhp 2008-02-26 12:30:06 UTC
Created attachment 57262 [details]
WSIT-AppCreation
Comment 2 deepakhp 2008-02-26 12:30:43 UTC
Created attachment 57264 [details]
ChangingNameSpace
Comment 3 deepakhp 2008-02-26 12:31:14 UTC
Created attachment 57265 [details]
ChangePort
Comment 4 deepakhp 2008-02-26 12:31:38 UTC
Created attachment 57266 [details]
DummyPortType
Comment 5 Sergey Lunegov 2008-02-26 16:56:55 UTC
Venkat, is it really belongs to "binding components". Reassign if it's needed.
Comment 6 Sherry Weng 2008-02-26 19:15:07 UTC
Change the subcomponent to "service assembly editor"
Comment 7 Tientien Li 2008-02-28 17:53:43 UTC
Deepak,

I could not reproduce this error. The porttype of two endpoints must match before one can make the connection in step 
17. So, I don't understandy the problem reported on step 19. Can you attach your projects to help us reproduce this 
problem?

Thanks,
Comment 8 Tientien Li 2008-02-28 19:02:40 UTC
OK, after repeated your steps a few times, we are able to reproduce this. Working on a fix right now.. Thanks,
Comment 9 Tientien Li 2008-02-29 21:16:17 UTC
Deepak,

We have analyzed this problem and reached the following decision:

1. There is a procedural problem in the instructions attached with the ticket. When I created the demo project for 
Noel/Sherry before, the steps 18 and 19 were done before 15-17. The parent node properties should be changed before 
its children. This example should work correctly, if you make this switch in the instructions.

Yes, there is a bug if the child node was changed first as you have reported here. Since this is a valid bug, but not 
a show stopper, we decided to down grade this ticket to a P3 and will address it later.

2. There are better ways to create the client project now. For example, once you have imported the server wsdl into 
CompApp you can do the following to load the server wsdl port into CASA. After the build in step 10,

- open CASA
- right click on the "WSDL ports" area in CASA and select "Load WSDL Port..." action
- select the server port from server wsdl file
- once the server port is loaded in CASA, right click to invoke WSIT client configuration

3. A even better way is to use the server wsdl from the client bpel project directly without import it again into 
compapp. To do this, you have to use a recent NB builds, e.g., #783 or later. After adding bpel project in step 8:

- build the compapp project
- open CASA
- right click on the sever port and select "Clone WSDL port to edit..." action
- after the port is cloned, right click to invoke WSIT client configuration

Feel free to ask us if you have any question or need more information.

Thanks,

--
Tientien Li