December 2010 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-7772) cannot manage keys separately, need to open "launch instance" wizard for it

by Andre Dietisheim (JIRA)

cannot manage keys separately, need to open "launch instance" wizard for it --------------------------------------------------------------------------- Key: JBIDE-7772 URL: https://jira.jboss.org/browse/JBIDE-7772 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: deltacloud Affects Versions: 3.2.0.Beta2 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.2.0.CR1 currently there's not item in the context menus, view menus, toolbars that allow me to manage keys. The only place where this might be reached is the "launch instance" wizard ("Manage" button) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

2
14
0 / 0

[JBoss JIRA] Created: (JBIDE-7523) Properties View: is not refreshed when correcting a connection url

by Andre Dietisheim (JIRA)

Properties View: is not refreshed when correcting a connection url ------------------------------------------------------------------ Key: JBIDE-7523 URL: https://jira.jboss.org/browse/JBIDE-7523 Project: Tools (JBoss Tools) Issue Type: Bug Components: deltacloud Affects Versions: 3.2.0.Beta2 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.2.0.Beta2 -- 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
12
0 / 0

[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-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-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-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

[JBoss JIRA] Created: (JBIDE-6830) Cannot recreate a service created by the wizard

by Lukas Jungmann (JIRA)

Cannot recreate a service created by the wizard ----------------------------------------------- Key: JBIDE-6830 URL: https://jira.jboss.org/browse/JBIDE-6830 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 3.2.0.M2 Reporter: Lukas Jungmann Assignee: Brian Fitzpatrick -have a dynamic web project 1) create a sample web service in the project using default values in the wizard 2) delete created file 3) delete entries added to web.xml by the wizard 4) save all changes 5) create a sample web service using default values in the wizard again 6) open web.xml file => contains: <servlet> <display-name>HelloWorld</display-name> <servlet-name>HelloWorld</servlet-name> <servlet-class>org.jboss.samples.webservices.HelloWorld</servlet-class> </servlet> <servlet-mapping> <servlet-name>HelloWorld</servlet-name> <url-pattern>/HelloWorld</url-pattern> </servlet-mapping> <servlet> <display-name>HelloWorld1</display-name> <servlet-name>HelloWorld1</servlet-name> <servlet-class>org.jboss.samples.webservices.HelloWorld</servlet-class> </servlet> <servlet-mapping> <servlet-name>HelloWorld1</servlet-name> <url-pattern>/HelloWorld1</url-pattern> </servlet-mapping> but since we did step 3 it should contain only: <servlet> <display-name>HelloWorld1</display-name> <servlet-name>HelloWorld1</servlet-name> <servlet-class>org.jboss.samples.webservices.HelloWorld</servlet-class> </servlet> <servlet-mapping> <servlet-name>HelloWorld1</servlet-name> <url-pattern>/HelloWorld1</url-pattern> </servlet-mapping> 7) delete all created files from the project, remove servlet related entries from the web.xml and save all files 8) create a sample web service using "HelloWorld" as the web service name => see attached screenshot - web.xml is empty but wizard says that web.xml already contains servlet "HelloWorld" -- 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
9
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 December 2010