[JBoss JIRA] Created: (JBIDE-5531) Moved jBPM process error during saving
by Jiri Peterka (JIRA)
Moved jBPM process error during saving
--------------------------------------
Key: JBIDE-5531
URL: https://jira.jboss.org/jira/browse/JBIDE-5531
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jbpm
Affects Versions: 3.1.0.CR1
Environment: Linux 64-bit, Sun JDK 1.6, JbossTools-3.1.0.v200912171816M-H185-RC1
Reporter: Jiri Peterka
Fix For: 3.1.0.GA
Attachments: jbpm-move-err1.png
1. Have a jBPM project
2. Create process in root project location
3. Edit process (insert some elements)
4. Move process into src/main/jpdl
5. Do some modifications (move element) and save it
FAILURE: Error message (see screenshot 1)
After similar operation workbench window is somehow corrupted, you can see screenshot 2
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 3 months
[JBoss JIRA] Created: (JBIDE-6759) ELReferencesQueryParticipant throws NullPointerException if user searches references for class from jar file
by Daniel Azarov (JIRA)
ELReferencesQueryParticipant throws NullPointerException if user searches references for class from jar file
------------------------------------------------------------------------------------------------------------
Key: JBIDE-6759
URL: https://jira.jboss.org/browse/JBIDE-6759
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JSF
Affects Versions: 3.2.0.M1
Reporter: Daniel Azarov
Assignee: Daniel Azarov
Fix For: 3.2.0.M2
java.lang.NullPointerException
at org.jboss.tools.jsf.ui.el.refactoring.ELReferencesQueryParticipant$ELSearcher.<init>(ELReferencesQueryParticipant.java:87)
at org.jboss.tools.jsf.ui.el.refactoring.ELReferencesQueryParticipant.search(ELReferencesQueryParticipant.java:59)
at org.eclipse.jdt.internal.ui.search.JavaSearchQuery$2.run(JavaSearchQuery.java:164)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.jdt.internal.ui.search.JavaSearchQuery.run(JavaSearchQuery.java:170)
at org.eclipse.search2.internal.ui.InternalSearchUI$InternalSearchJob.run(InternalSearchUI.java:91)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 3 months
[JBoss JIRA] Created: (JBIDE-6553) New JSF wizard often only has ONE server / runtime listed
by Rob Stryker (JIRA)
New JSF wizard often only has ONE server / runtime listed
---------------------------------------------------------
Key: JBIDE-6553
URL: https://jira.jboss.org/browse/JBIDE-6553
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jsp/jsf/xml source editing
Affects Versions: 3.1.1, 3.2.0.M1
Reporter: Rob Stryker
Assignee: Denis Golovin
I have four servers installed in my workspace, but for some reason when trying to create a new JSF project, only *one* is listed in the wizard. Some quick tracing has shown that it's executing this call to find which server is selected:
AppRegisterComponent.initTargetServerValue(), and this method also calls
IServer sel = ServerManager.getInstance().getSelectedServer();
Looking through the method's logic I actually have zero clue what is going on here, what the goal is, etc. I would expect that on this page you would be able to select which server / runtime you want to use, but it seems it always invariably only shows one possible entry, and that entry is rarely the entry I want to use. In this case I'm trying to make a project targeted to my EAP server, and the wizard provides me absolutely no method to do so.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 3 months