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 153564 - Activity with traced descendant disappear after calling "Wrap With..." action on it.
Summary: Activity with traced descendant disappear after calling "Wrap With..." action...
Status: VERIFIED FIXED
Alias: None
Product: soa
Classification: Unclassified
Component: BPEL (show other bugs)
Version: 6.x
Hardware: All All
: P1 blocker (vote)
Assignee: Vitaly Bychkov
URL:
Keywords:
: 153572 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-11-20 17:14 UTC by Alexey Anjeleevich
Modified: 2008-11-25 22:34 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alexey Anjeleevich 2008-11-20 17:14:24 UTC
Steps to reproduce

1) Take a BPEL project
2) Select activity.
3) Use the Logging tab to add Logging on an activity
4) Call on activity (or on ascendant of activity) any "Wrap with..." action
-everything you wrapped with the scope will simply disappear (also from the source view). 
5) Activity (or ascendant of activity) will disappear

4') Instead "Wrap with..." action you can move activity by mouse drag. Result will be the same.
Comment 1 Alexey Anjeleevich 2008-11-20 17:17:08 UTC
java.lang.NullPointerException
	at org.netbeans.modules.bpel.model.impl.CookieCopierService.setCookie(CookieCopierService.java:69)
	at org.netbeans.modules.bpel.model.impl.CookieCopierService.setCookie(CookieCopierService.java:69)
	at org.netbeans.modules.bpel.model.impl.CookieCopierService.setCookie(CookieCopierService.java:69)
	at org.netbeans.modules.bpel.model.impl.CookieCopierService.postDispatch(CookieCopierService.java:54)
	at org.netbeans.modules.bpel.model.impl.BpelModelImpl.postInnerEventNotify(BpelModelImpl.java:635)
	at org.netbeans.modules.bpel.model.impl.BpelEntityImpl.postEvent(BpelEntityImpl.java:709)
	at org.netbeans.modules.bpel.model.impl.BpelEntityImpl.cut(BpelEntityImpl.java:180)
	at org.netbeans.modules.bpel.nodes.actions.AbstractWrapWithAction$1.call(AbstractWrapWithAction.java:135)
	at org.netbeans.modules.bpel.model.impl.BpelModelImpl.invoke(BpelModelImpl.java:234)
	at org.netbeans.modules.bpel.nodes.actions.AbstractWrapWithAction.performAction(AbstractWrapWithAction.java:166)
	at org.netbeans.modules.bpel.nodes.actions.BpelNodeAction$1.call(BpelNodeAction.java:85)
	at org.netbeans.modules.bpel.model.impl.BpelModelImpl.invoke(BpelModelImpl.java:234)
	at org.netbeans.modules.bpel.nodes.actions.BpelNodeAction.performAction(BpelNodeAction.java:83)
	at org.openide.util.actions.NodeAction.performAction(NodeAction.java:289)
	at org.openide.util.actions.CallableSystemAction$1.run(CallableSystemAction.java:118)
	at org.netbeans.modules.openide.util.ActionsBridge.doPerformAction(ActionsBridge.java:77)
	at org.openide.util.actions.CallableSystemAction.actionPerformed(CallableSystemAction.java:114)
	at org.openide.util.actions.NodeAction.actionPerformed(NodeAction.java:277)
	at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1995)
	at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2318)
	at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:387)
	at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:242)
	at javax.swing.AbstractButton.doClick(AbstractButton.java:357)
	at javax.swing.plaf.basic.BasicMenuItemUI.doClick(BasicMenuItemUI.java:1225)
	at javax.swing.plaf.basic.BasicMenuItemUI$Handler.mouseReleased(BasicMenuItemUI.java:1266)
	at java.awt.Component.processMouseEvent(Component.java:6134)
	at javax.swing.JComponent.processMouseEvent(JComponent.java:3265)
	at java.awt.Component.processEvent(Component.java:5899)
	at java.awt.Container.processEvent(Container.java:2023)
	at java.awt.Component.dispatchEventImpl(Component.java:4501)
	at java.awt.Container.dispatchEventImpl(Container.java:2081)
	at java.awt.Component.dispatchEvent(Component.java:4331)
	at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4301)
	at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3965)
	at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3895)
	at java.awt.Container.dispatchEventImpl(Container.java:2067)
	at java.awt.Window.dispatchEventImpl(Window.java:2458)
	at java.awt.Component.dispatchEvent(Component.java:4331)
[catch] at java.awt.EventQueue.dispatchEvent(EventQueue.java:599)
	at org.netbeans.core.TimableEventQueue.dispatchEvent(TimableEventQueue.java:104)
	at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:269)
	at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:184)
	at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:174)
	at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:169)
	at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:161)
	at java.awt.EventDispatchThread.run(EventDispatchThread.java:122)
Comment 2 Sergey Lunegov 2008-11-20 17:22:56 UTC
We need to test other activities with BPEL extensions. Nikita please verify the type cast and pseudo-components scenario.
Comment 3 Sergey Lunegov 2008-11-21 06:22:57 UTC
*** Issue 153572 has been marked as a duplicate of this issue. ***
Comment 4 Sergey Lunegov 2008-11-21 06:23:52 UTC
comments from I saw this problem already some time ago, but then when I was to write here about it I couldn't repeat the
problem in
"general case". Now after reading Ingebright's email I am able to do so every time and the small important thing here is
that you have to have logging enabled for the activity that you are wrapping to scope.

The same issue is there also for any wrapping (not only wrapping to a scope) like wrap to sequence, flow etc.

In addition the very similar problem exist there if you first create scope (sequence, flow, etc.) and then drag and drop
an existing invoke activity (or any activity) with logging on, inside the scope. In this case the scope is not lost, but
the activity is. I.e. let's say you have already made process where you have an invoke called "CallMyService" to which
you have enabled logging. If you then add a scope from palette to your process and then drag the "CallMyService" inside
the scope you'll lose the "CallMyService" invoke activity.

Still to add :). The very same happens if you have a scope (sequence, flow, etc.) and inside that you have an activity
(like invoke, assign etc.) to which has logging enabled. Then when you drag the item outside  the scope the activity
(invoke etc.) will be lost.

Fortunately undo still works and you can get your activity back. Anyhow to move items in to or out from a scope
(sequence, flow, etc.) in a BPEL process requires that you first remember to disable logging on the activity you are to
move.

I have tested that the same problem exists in JCAPS6, GFesb m2, and GFesb RC1.
Comment 5 Vitaly Bychkov 2008-11-22 03:27:21 UTC
Fixed in soa-dev.
Changesets: 973aef94965c, d75d89fa27ee.
Comment 6 Vitaly Bychkov 2008-11-22 03:49:03 UTC
Fixed in soarelease.
Comment 7 ggenipudi 2008-11-25 22:34:09 UTC
Tested and verified using caps6u1 11/24 build and was able to wrap with scope the assign after doing a logging and it
did not disappear.