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.
Hula Build 8 When renaming an IEP process, a new file gets created, and does not get removed. When I renamed RenameIEP.iep to Tuple.iep, I found the following file in my IEP Prject Directory .LCKRenameIEP.iep~
I am able to rename the project.
Tested with Hula Build 070330_16, and I still see the same issue
Verified that this is no longer an issue in latest nb trunk 61.
Not sure this is the expected behavior: Retested with Java CAPS 6 with NB 6.1 patches applied and IEP nbms for Build080720 (july 20) installed. If I rename an IEP process file: -- the original component id inside the renamed file has not changed -- the generated *.wsdl file generated with the new name (the original name *.wsdl continues to be generated)
Please specify what do you mean by "the original component id", is it the name attribute on top level component. The wsdl file name matches the name of the iep file so if file is renamed wsdl file should be regenerated with new name.
create a IEP process with name "Notification", the .IEP file use "Notification" as the name of attribute on top level component. Rename the IEP process to "NotificationWithCLOB" ; the name of attribute on top level component still shows "Notification". WSDL generated is still "Notification". Try creating a new IEP process with "Notification". Re Deployment cause following exception the name here is "NotificationWithCLOB_iep" which was "Notification_iep" before rename operation. [#|2008-08-06T21:40:24.144-0700|SEVERE|sun-appserver9.1|com.sun.jbi.engine.iep.core.runtime.IEPEngine|_ThreadID=190;_ThreadName=TimeBasedAggregatorCombinedCA-TimeBasedAggregatorIEP;_RequestID=3e608bdb-011c-4192-8cf3-f2e521f158aa;|IEPSEafa00000: Fail to load event processor: NotificationWithCLOB_iep java.lang.NullPointerException at com.sun.jbi.engine.iep.core.runtime.operator.QueryPlanImpl.addOperator(QueryPlanImpl.java:82) at com.sun.jbi.engine.iep.core.runtime.operator.QueryPlanImpl.loadOperators(QueryPlanImpl.java:296) at com.sun.jbi.engine.iep.core.runtime.operator.QueryPlanImpl.loadAll(QueryPlanImpl.java:170) at com.sun.jbi.engine.iep.core.runtime.operator.QueryPlanImpl.<init>(QueryPlanImpl.java:308) at com.sun.jbi.engine.iep.core.runtime.operator.QueryPlanFactoryImpl.createQueryPlan(QueryPlanFactoryImpl.java:47) at com.sun.jbi.engine.iep.core.runtime.util.Util.getPlanByInstanceId(Util.java:1377) at com.sun.jbi.engine.iep.core.runtime.DefaultIEPEngine.getPlanByInstanceId(DefaultIEPEngine.java:75) at com.sun.jbi.engine.iep.core.runtime.DefaultIEPEngine.start(DefaultIEPEngine.java:150) at com.sun.jbi.engine.iep.IEPSEServiceUnitManager.start(IEPSEServiceUnitManager.java:415) at com.sun.jbi.framework.ServiceUnitOperation.process(ServiceUnitOperation.java:185) at com.sun.jbi.framework.Operation.run(Operation.java:104) at java.lang.Thread.run(Thread.java:595) |#]
we might want to use refactoring api for this. we may need to depend on xml refactoring and add a iep editor as friend. To get it working on top of java caps we may have to get this friend dependency on nb61release patch4.
started work on rename refactoring.
Refactoring is nice to have feature, downgrading as per discussion with Gabe.