January 2011 - jbosstools-issues - Jboss List Archives

[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

4
7
0 / 0

[JBoss JIRA] Created: (JBIDE-8088) Static Analysis Fault SA00014 not handled

by Robert (Bob) Brodt (JIRA)

Static Analysis Fault SA00014 not handled ----------------------------------------- Key: JBIDE-8088 URL: https://issues.jboss.org/browse/JBIDE-8088 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpel Affects Versions: 3.2.0.CR1 Reporter: Robert (Bob) Brodt Fix For: 3.2.x This is described here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=266991 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

3
6
0 / 0

[JBoss JIRA] Created: (JBIDE-7111) Internal error during building Project Archive

by Jiri Peterka (JIRA)

Internal error during building Project Archive ---------------------------------------------- Key: JBIDE-7111 URL: https://jira.jboss.org/browse/JBIDE-7111 Project: Tools (JBoss Tools) Issue Type: Bug Components: Archives Affects Versions: 3.2.0.M2 Environment: JBDS 4.0.0.m2 480, Linux 64 Reporter: Jiri Peterka Internal error and temporary IDE freeze during building SeamWAR in Project Archive View: 1. New workspace 2. Create seam war project (default EAP) 3. Switch to Project Archive 4. Create war archive 5. Build archive -- 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

4
8
0 / 0

[JBoss JIRA] Created: (JBDS-905) Forum revision for 3.1.0 release

by Svetlana mukhina (JIRA)

Forum revision for 3.1.0 release -------------------------------- Key: JBDS-905 URL: https://jira.jboss.org/jira/browse/JBDS-905 Project: JBoss Developer Studio Issue Type: Task Components: documentation Affects Versions: 2.1.0 Reporter: Svetlana mukhina Assignee: OLga Chikvina Fix For: 2.1.0-doc Review forum posts, update the guides according to users remarks, wishes, answer on forum posts related to docs or posts that you know answers for -- 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, 11 months

4
11
0 / 0

[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

3
4
0 / 0

[JBoss JIRA] Created: (JBIDE-7077) Open With -> JBoss Tools -> "JBoss Tools Docbook Editor" - exist in context menu for every xml file

by Vitali Yemialyanchyk (JIRA)

Open With -> JBoss Tools -> "JBoss Tools Docbook Editor" - exist in context menu for every xml file --------------------------------------------------------------------------------------------------- Key: JBIDE-7077 URL: https://jira.jboss.org/browse/JBIDE-7077 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Affects Versions: 3.2.0.M2 Reporter: Vitali Yemialyanchyk Assignee: Maxim Areshkau Priority: Minor if there is possibility to detect docbooks xmls -> try to detect or use some heuristics to detect docbook file type from file content. other way -> do not put "JBoss Tools Docbook Editor" in Open With menu - or put just in case when you can state what this is docbook file. -- 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

7
17
0 / 0

[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

8
23
0 / 0

[JBoss JIRA] Created: (JBIDE-7971) "Show All Eligible Beans..." OpenOn works wrong if it has less lines then in previous menu

by Daniel Azarov (JIRA)

"Show All Eligible Beans..." OpenOn works wrong if it has less lines then in previous menu ------------------------------------------------------------------------------------------ Key: JBIDE-7971 URL: https://issues.jboss.org/browse/JBIDE-7971 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi (jsr-299) Affects Versions: 3.2.0.Beta2 Reporter: Daniel Azarov Assignee: Daniel Azarov Fix For: 3.2.0.CR1 If "Show All Eligible Beans..." OpenOn menu has less lines then in previous menu it is immediately disappears in many cases -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

3
5
0 / 0

[JBoss JIRA] Created: (JBIDE-6527) [tester] include prefixed namespace definition instead of anonymous one in generated SOAP message

by Lukas Jungmann (JIRA)

[tester] include prefixed namespace definition instead of anonymous one in generated SOAP message ------------------------------------------------------------------------------------------------- Key: JBIDE-6527 URL: https://jira.jboss.org/browse/JBIDE-6527 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Webservices Affects Versions: 3.2.0.M1 Reporter: Lukas Jungmann Assignee: Brian Fitzpatrick it would be maybe good to include prefixed namespace definition instead of anonymous one in generated SOAP message, in the other words generate: <ns1:GetSearchResults xmlns:ns1 = "http://www.ecubicle.net/webservices"/> instead of current <GetSearchResults xmlns = "http://www.ecubicle.net/webservices"/>. The reason for this change is that it is pretty common that child elements of the root element are usually from no namespace and if the root element contains anonymous namespace definition the inheritance rules will cause that child elements will be taken from that "anonymous" namespace too, which is wrong, ...unless user tweak it. [originally mentioned in JBIDE-6497] -- 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

2
4
0 / 0

[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

4
23
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues January 2011