[JBoss JIRA] Created: (JBIDE-7288) Server Delete action should close opened Server Configuration Editor
by Denis Golovin (JIRA)
Server Delete action should close opened Server Configuration Editor
--------------------------------------------------------------------
Key: JBIDE-7288
URL: https://jira.jboss.org/browse/JBIDE-7288
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.2.0.Beta2
Reporter: Denis Golovin
Assignee: Rob Stryker
1. EXEC: Create Runtime and Server by New->Server action on server view
2. EXEC: Open Server Configuration Editor by double click on server created before in server view
3. EXEC: Delete created server by Delete item in context menu
4. ASSERT: Server deleted and Configuration editor is closed
Now it editor stays ope and it is confusing in some cases. If you have many editors open and Server Configuration editor was changed is is easy to get to situation, when finally you get to the point of closing it. When editor with changes is closing it asks about saving changes. If you says yes on this request for editor that left open after test case above it saves deleted configuration and restore deleted server in server view.
--
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, 11 months
[JBoss JIRA] Created: (JBIDE-8097) JBoss Tools Docbook editor is missing in JBT/JBDS
by Vlado Pakan (JIRA)
JBoss Tools Docbook editor is missing in JBT/JBDS
-------------------------------------------------
Key: JBIDE-8097
URL: https://issues.jboss.org/browse/JBIDE-8097
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor core
Affects Versions: 3.2.0.CR1
Environment: Linux 32bit, Java Sun 1.6
Reporter: Vlado Pakan
Assignee: Maxim Areshkau
Create new .xml file. It's not possible to open this file with JBoss Docbook editor.
There was context menu when right clicked on this .xml Open With > JBoss Tools Docbook and also when dialog with all available editors Open With > Other... contained JBoss Tools Docbook item.
It's not working neither in JBT 2011-01-11_22-57-02-H898 nor JBDS 201101071424N-H660-CR1.
It's working in JBDS 201012161657N-H584-CR1.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 11 months
[JBoss JIRA] Created: (JBIDE-8049) *.inc content type JSP clash with PDT
by Sylvain Lecoy (JIRA)
*.inc content type JSP clash with PDT
-------------------------------------
Key: JBIDE-8049
URL: https://issues.jboss.org/browse/JBIDE-8049
Project: Tools (JBoss Tools)
Issue Type: Bug
Environment: Eclipse Helios
Windows 7 x64
Reporter: Sylvain Lecoy
I'm using eclipse 3.6.1, and among other things have a few j2ee plugins and php.
In the content types (under text) both the jsp type and php type both have ".inc" in the file association.
The workspace in which I work with php is a different one than the one I'm using for jsp (or java for that matter) and so in the php workbench I defaulted the php editor to handle .inc files.
When I open a .inc file in the editor though all of the text is one big error (all red underlined) and in the Problems view all of the errors are from type "JSP Problem", also when I view the properties of the file I get Type: File (JSP).
This bug originally reported on eclipse.org : http://www.eclipse.org/forums/index.php?t=msg&goto=647203&S=21af02ce175ae...
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 11 months
[JBoss JIRA] Created: (JBIDE-8017) No bean is eligible for @Inject BeanManager manager;
by Alexey Kazakov (JIRA)
No bean is eligible for @Inject BeanManager manager;
----------------------------------------------------
Key: JBIDE-8017
URL: https://issues.jboss.org/browse/JBIDE-8017
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: cdi (jsr-299)
Affects Versions: 3.2.0.CR1
Reporter: Alexey Kazakov
Assignee: Viacheslav Kabanovich
Fix For: 3.2.0.CR1
See the spec.:
11.3. The BeanManager object
Portable extensions sometimes interact directly with the container via programmatic API call. The interface javax.enterprise.inject.spi.BeanManager provides operations for obtaining contextual references for beans, along with many other operations of use to portable extensions. The container provides a built-in bean with bean type BeanManager, scope @Dependent and qualifier @Default.
The builtin implementation must be a passivation capable dependency, as defined in Section 6.6.2, "Passivation capable dependencies". Thus, any bean may obtain an instance of BeanManager by injecting it:
@Inject BeanManager manager;
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 11 months