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.
Tested using gfesb rc1 build and was able to reproduce the error following steps below on windows vista. Ingebrigt M Berg wrote: > Hi ! > > I noticed several times that when I try to wrap something in a scope, > everything I wrap simply disappears. > > I think I have traced the problem, and that it only happens if there is > logging/alerting on any of the activities I try to log. > > To reproduce: > > -Take a BPEL project > -Use the Logging tab to add Logging on an activity > -wrap that activity with a scope. > -everything you wrapped with the scope will simply disappear (also from the > source view). > > cheers, > Ingebrigt >
Created attachment 73967 [details] project
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.
This is dup of 153564 *** This issue has been marked as a duplicate of 153564 ***
tested and verified using \\thumper\50builds\gfesb-sync\v2\nightly\20090105-0707 and was able to wrap with scope activity with logging and the activity did not disappear.