means that: Reviewing an assign that you created in the past doesn't seem to work anymore. This is a pretty serious error.
Please provide more exact steps how to reproduce the issue.
Please also attach the project you work with.
Would it be ok if I sent a project to your email address? It has to much work stuff in there for me to attach it here.
yes send it to my email
I sent you the code in decemeber. Can you confirm if you received it and / or if this is a bug?
Changed target milestone from Sierra to 6.1 in order to display correct info on
NB 6.1 dashboard
Created attachment 55203 [details]
David, I received the project. This is a bug. Exception is another but it exists.
We'll address it.
Nikita, I've attached the project.
Will be addressed after Sierra
Dave, looks like fixed in NB 6.1 FCS. Would you please verify.
QA, please verify this fix till 09-Jun-2008, so it can be part of NB 6.1 patch 2.
Also clarify if the bug fix is already part of NB 6.1 FCS or not.
NetBeans IDE Dev (Build 200805280004)
- open the attached project;
- open BPEL document;
- double-click topmost Assign activity on the diagram.
can you please fix this bug as soon as possible (till 09-Jun-2008), so it can be part of NB 6.1 patch 2?
This issue has a bit misleading instructions.
So I looked only to latest one (about NPE).
Also the attached project has a character in an unusual encoding.
So it works with problems on my computer. I changed that character to
simple 'u' to be able open the project.
I can't reproduce the NPE on my local NetBeans,
which is built from the latest sources.
I get another Exception, when I open the BPEL first time.
But I don't have any ideas what that exception about.
And it definitely not related to this issue.
I will attach my exception for other case.
Created attachment 62584 [details]
There is definitely something wrong here.. :(
1) Don't you consider the possibility of the fact that it is the "character in an unusual encoding", which is causing
the issue? Shouldn't we ALWAYS try to reproduce the exception given the project as it is?
2) You found an exception. Okay, you have no idea what it means. Why not file another bug for that? If it happens,
shouldn't it get fixed?
For the latest exception I've filed issue 136863.
Changes are very small and safe
You can see them here: http://hg.netbeans.org/main/rev/9f081d6560f0
The fix has been ported into the release61_fixes repository.
Verified with NetBeans IDE Dev (Build 20080611100304)