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.
Rico, as per design agreement the DnD of WS node from EJB project was supposed to behave identically for 1.4 and 1.5 style WS. In both cases the xferable is supposed to help the drop target (BPEL Diagram) to retrieve the EBJ wsdl (plus xsd's) from the AS assuming they are deployed. This seems to be working as designed for 1.5 style WS. But it does not seem to be working for 1.4 style WS. See Enterprise pack Samples > SOA > TravelReservationServices for example. It has EJB project ReservationPartnerServicesApplication which contains EJB WS. These are 1.4 style WS. I tried to DnD these WS into a totally new and arbitrary BPEL diagram. I got no feedback at all. The DnD action just completed but nothing happened. No dialog saying that WS was not deployed. No files copied. No partner link created. Nothing. Alexey Y said he thinks this must mean that Rico has not implemented the 1.4 support. This is urgent issue.
I implemented DND on 1.4 web service nodes two weeks ago (when I was in Monrovia), so this should work. Will look at this.
Drag and drop of J2EE 1.4 web service nodes to the BPEL UI works in the current build. Here is what I did: 1. New Project/Samples/SOA/TravelReservationService 2. Resolved TravelReservationServiceApplication by adding JBI module TravelReservationService. 3. Opened projects ReservationPartnerServiceApplication and ReservationPartnerServices. 4. Deployed ReservationPartnerServiceApplication. (Note this shd be deployed not the EJB module) 5. Created new BPEL Module. 6. Added new BPEL process to the BPEL module. 7. Dragged and dropped AirlineReservationService from the ReservationPartnerServices module to the BPEL process. The PartnerLink Property Editor comes up. But this time, the WSDL file list is empty because of http://www.netbeans.org/issues/show_bug.cgi?id=84821. (See my comments to this bug). Because of this bug, no partner link is created. Meanwhile, using the debugger, I walked through the WebServiceReference (from the Transferable) and it was returning the correct wsdl URL. Closing as WORKSFORME.
I did a "quick and dirty" fix in my machine for 84821 and everything worked fine, i.e., wsdl list was populated and partner link was created propertly.
Rico, can you please test scenario where WS is NOT deployed to AS. This was what I think was case on my system. I was expecting at least a dialog from Alexey saying "Cannot retrieive web service WSDL. Please ensure that partner web service has been deployed" (or something like that). But instead I received absolutely no feedback. I did not get the PL dialog or anything. Admittedly, problem may be on Alexey side. But I want to take advantage of time zone lag and give you a chance to make sure you are not involved.
So if you observe the same "no feedback" for case where partners are not deployed then please just reassign to me or Alexey.
Yes, if the partner is not deployed and the user attempts to drag it to the BPEL process, it just silently fails. There should be a message indicating this failure. Reassigning to BPEL UI/ Alexey.
Rico, are you sure that you are providing the same contract to Alexey for 1.4 not deployed as you are for 1.5 not deployed? He said he tested for 1.5 not deployed and that was how he unit tested his dialog. So it seems strange that problem would be on his side since he does not have any conditionality (or even awareness) that target is 1.4 or 1.5. Just assigning to u to get your attention again.
Actually, now that I think about it, another edge case is probably "AS is not started, or not reachable". You see, I was having all sorts of mixed messages from the IDE regarding my AS status. The output window told me AS was started but I was also getting pop up dialogs saying that AS start failed. And the AS node in runtime tab did not show any sub nodes. So AS / IDE relationship was debatable. Can you try with AS stopped and AS not registered. We need to test all of these edge cases agressively.
Yes it is the same contract for 1.4 and 1.5 for undeployed partners. Hmmm, I tried it on undeployed 1.5 partner and did not get the dialog.
You tried it for undeployed 1.5 when AS was running? And did not get dialog? Basically we need to test at least following permutations AS 9 Registered + AS Running + WS deployed (should succeed) AS 9 Registered + AS Running + WS not deployed (should get "Must Deploy" dialog) AS 9 Registered + AS !Running - (should get "Must Deploy" dialog) AS 9 !Registered - (should get "Must Deploy" dialog) any others?
Yes I tried it for both AS running and not running. I think your cases are good. Should we downgrade this from P1?
Please clarify, you tested it for the cases I listed and you found what?
in both cases, dialog did not show up
Sorry folks, it was two problems on diagram side. First one is a missing error message once user tries to drop not-deployed projects. It was a result of missing bundle resource: i refactored one method to move it from one class to another, crossing the package boundaries, while bundle stayed in old package. Another problem was a regression introduced by my attempt to make use new DnD transferable API which provides module name. Once I agreed with Todd that i should use it instead of extracting module name from URL, i removed the old logic, and realized that new API is not yet in NB binaries I use. So, i hardcoded a dummy name for a service, remainding me to uncomment some line, and ,by mistake, this stub was commited to cvs.
I found that 1.4 EJB Module project can not be DnD-ed if it was deployed alone, not as a part of some J2EE application. In this case Transferable contains WebService reference with null url. Rico, can you take a look?
A web service in an EJB module can be DnD'd if the module was deployed standalone. The only case where DnD will fail is if the deployment failed, in which case, the WebServiceReference will return a null url. You probably tried this on the ReservationPartnerServices EJB module from the Travel sample. If you deploy that EJB module as is, deployment fails. This EJB module contains a Message Driven Bean which requires messaging resource configuration, in order for it to be deployed properly. The server log will indicate that deployment of the EJBs was not successful if you attempted to deploy this module. The resource configuration files for the MDB are in the ReservationPartnerServicesApplication project (I guess, the sample expects the user to deploy the J2EE app, not the EJB module). If you deploy this J2EE application (which contains ReservationPartnerServices), deployment of the EJBs(and webservices) is successful, and DnD is likewise successful (which was your experience). If you want to deploy ReservationPartnerServices as a standalone EJB module, you may copy the resource configuration files from ReservationPartnerServicesApplication into the EJB module: 1. Go to the Files view. 2. Expand the ReservationPartnerServices folder. 3. Add a new folder named "setup" under ReservationPartnerServices. 4. Expand the ReservationPartnerServicesApplication folder. 5. Go to its setup folder and copy the two files in it 6. Paste the two files into ReservationPartnerService/setup After doing this, deploying ReservationPartnerServices as a standalone EJB module will be successful, hence DnD will succeed. Also, you can simply create an EJB module with a simple web service in it (with no MDBs, etc) and deploy it standalone. DnD will be successful.
Thanks for great description Rico.
I checked with simple EJB WS project, which have no need to register any appserver resource and it works just fine evven when deployed as stand-alone module. Rico, thanx once again for your explanations. Closing thib bug as fixed.
WinXP Coke061001 steps 0 create EJB Java EE Version = J2ee 1.4 1 create Webservice NewWebservice , add operation, deploy 2 drop on bpel diagram 3 property editor is opened - there is newly created PLT. press ok 4 Process Files on project tab has node Partners|NewWebservice | NewWebservice.wsdl all is ok