February 2010 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-5046) JSF model/builder

by Alexey Kazakov (JIRA)

JSF model/builder ----------------- Key: JBIDE-5046 URL: https://jira.jboss.org/jira/browse/JBIDE-5046 Project: Tools (JBoss Tools) Issue Type: Task Components: JSF Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: LATER We have to create JSF builder to JSF 2 artifacts into JSF model. Such as: - annotated manage beans - resources ... -- 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

12 years, 11 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-496) Add Maping files

by Krasimir Goutcev (JIRA)

Add Maping files ---------------- Key: JBIDE-496 URL: http://jira.jboss.com/jira/browse/JBIDE-496 Project: JBoss Tools Issue Type: Feature Request Components: Hibernate Tools Reporter: Krasimir Goutcev Assigned To: Max Andersen Possibility to add mapping lfiles as Exadel ORM Explorer -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 12 months

4
10
0 / 0

[JBoss JIRA] Created: (JBIDE-499) All futures that was in ORM Explorer

by Krasimir Goutcev (JIRA)

All futures that was in ORM Explorer ------------------------------------ Key: JBIDE-499 URL: http://jira.jboss.com/jira/browse/JBIDE-499 Project: JBoss Tools Issue Type: Feature Request Reporter: Krasimir Goutcev - Open Mapping - Edit Source - Edit Mapping - View Table - Clear Mapping - Remove persistent class - rename class -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 12 months

4
3
0 / 0

[JBoss JIRA] Created: (JBIDE-911) EJB3 component wizards are not included in Beta3

by Tyronne Wickramarathne (JIRA)

EJB3 component wizards are not included in Beta3 ------------------------------------------------ Key: JBIDE-911 URL: http://jira.jboss.com/jira/browse/JBIDE-911 Project: JBoss Tools Issue Type: Feature Request Components: ejb3 Affects Versions: 2.0.0.Beta3 Environment: all environments Reporter: Tyronne Wickramarathne Fix For: 2.0.0.Beta4 EJB3 component wizards are not included in Beta3 release. include EJB3 project creation from the IDE too. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

4
5
0 / 0

[JBoss JIRA] Created: (JBIDE-3120) Support webbeans typesafe xml schema

by Max Rydahl Andersen (JIRA)

Support webbeans typesafe xml schema ------------------------------------- Key: JBIDE-3120 URL: https://jira.jboss.org/jira/browse/JBIDE-3120 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: webbeans Reporter: Max Rydahl Andersen Fix For: LATER http://docs.jboss.org/webbeans/reference/1.0/en-US/html/xml.html "The advantage of this approach is that you can write an XML schema that prevents spelling errors in your XML document. It's even possible for a tool to generate the XML schema automatically from the compiled Java code. Or, an integrated development environment could perform the same validation without the need for the explicit intermediate generation step." 1) the RI will have a code->xsd generator for web-beans.xml; could maybe be used for validation....but requires that all classes can compile 2) we should have xml completions following the naming standard layed out by webbeans spec -- 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

13 years

5
12
0 / 0

[JBoss JIRA] Created: (JBIDE-3725) Seam components from sources are not loaded by Seam Tools model right after project creation.

by Alexey Kazakov (JIRA)

Seam components from sources are not loaded by Seam Tools model right after project creation. --------------------------------------------------------------------------------------------- Key: JBIDE-3725 URL: https://jira.jboss.org/jira/browse/JBIDE-3725 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 3.0.0.CR2 Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: 3.0.0.GA 1. Create Seam EAR project using New Seam Web Project (I tested on Seam 2.1) 2. Open home.xhtml 3. Ctrl+Space on #{|}. There is not "authenticator" component (see Authenticator.java). 4. Open "Open Seam Component" dialog. Type "authenticator". There is not any "authenticator" component in the project. Clean/Rebuild helps. -- 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

13 years

5
24
0 / 0

[JBoss JIRA] Created: (JBDS-863) Mapping Diagram viewer redesign

by Svetlana mukhina (JIRA)

Mapping Diagram viewer redesign ------------------------------- Key: JBDS-863 URL: https://jira.jboss.org/jira/browse/JBDS-863 Project: JBoss Developer Studio Issue Type: Task Components: Doc - Hibernate Affects Versions: 2.0.0.GA Reporter: Svetlana mukhina Assignee: Olga Chukhutsina Fix For: 2.1.0-doc The viewer redesigned update section 4.9.1.1. Mapping Diagram see the link task and subtasks -- 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

13 years

4
13
0 / 0

[JBoss JIRA] Created: (JBIDE-1388) support remote hosts/external started AS adapter

by Max Andersen (JIRA)

support remote hosts/external started AS adapter ------------------------------------------------ Key: JBIDE-1388 URL: http://jira.jboss.com/jira/browse/JBIDE-1388 Project: JBoss Tools Issue Type: Feature Request Components: JBossAS Reporter: Max Andersen Fix For: 2.1 people like to start there server manually and just hook up to it via remote debugging - we should make that easy (its trivial via eclipse support for remote debugging) should be an option on the servers, doesnt require new server/runtime type if local server. Only catch is that the server might not even be accessible via filesystem - how should we handle deploy and runtime lib situation ? (my best bet is just that these would be unspecified and not provide those features) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

5
6
0 / 0

[JBoss JIRA] Created: (JBDS-1016) Usability issue with Seam Web Project Wizard

by Joshua Wulf (JIRA)

Usability issue with Seam Web Project Wizard -------------------------------------------- Key: JBDS-1016 URL: https://jira.jboss.org/jira/browse/JBDS-1016 Project: JBoss Developer Studio Issue Type: Bug Affects Versions: 3.0.0.M4 Environment: Mac OS X 10.4.11 32 bit PPC Reporter: Joshua Wulf The Seam Web Project Wizard changes the Configuration when the Target runtime is changed. Although it starts out with "Dynamic Web Application for Seam 2.0" selected by default, if the Target runtime is changed the Configuration selection is changed to match the Target Runtime. This results in an error "Seam facet must be enabled." Changing the Target Runtime back to the original one does not remove the error. There are two ways to remove the error message. One is to manually change the Configuration back to "Dynamic Web Application for Seam 2.x". Since it is not possible to move forward from this page without enabling the Seam facet, the configuration should not automatically change to one that does not have Seam facet enabled. The situation is more complicated, and worse, however, because the other way to remove the error message is to manually modify the Configuration using the "Modify" button. If the user does this, and enables JavaServer Faces and Seam, the error message will disappear and they will be able to move forward. However, when it comes time to select the Seam runtime the user will run into a problem. In the Modify Configuration screen where the user enabled the Seam facet, the unique option there was fixed at version 2.2. If the Seam runtime the user wishes to use is not 2.2 then they will get an error that the Seam runtime is an incompatible version. They will be unable to select any other version in the version drop-down box. So there are three problems: 1. The Configuration changes automatically to one incompatible with a Seam Web Project if the Target runtime is changed. 2 . Although a user may try to clear the resultant error message by changing the runtime back to the original one, the error message will remain, as the dialog will change the configuration to another incompatible one. If the user did not notice the original default configuration (which they may well not if they are moving from top to the bottom of the wizard, which will be the usual case), they have no way of knowing how to clear the error message. 3. If the user clicks on the tempting "Modify" button and manually enables Seam they can run into a problem several screens later (error message saying Seam version is incompatible and only 2.2 in the version drop-down box) with no obvious way to resolve it. The workaround is to document this quirk, but that defeats the purpose of an intuitive in-IDE wizard that guides you through setting up the project. I would recommend making the configuration stay on the default, even when the Target runtime is changed. If the user sees an incompatible version of Seam there when they scan down, they are likely to click it to see if a compatible version of Seam is there. If they see "Default configuration for X runtime" with a description saying "A good starting point... Additional facets can later be installed to add new functionality to the project" and an error message saying "Seam facet must be enabled", then their likely response will be to modify the configuration to "add new functionality" to the "good starting point" that the wizard has selected for them. -- 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

13 years

3
17
0 / 0

[JBoss JIRA] Created: (JBIDE-5725) JBossWS WSDL are not deployed under the right folder

by StÃ©phane Daviet (JIRA)

JBossWS WSDL are not deployed under the right folder ---------------------------------------------------- Key: JBIDE-5725 URL: https://jira.jboss.org/jira/browse/JBIDE-5725 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 3.1.0.CR1 Environment: GNU/Linux Ubuntu Karmic Koala 9.10, kernel 2.6.31-17-generic Reporter: StÃ©phane Daviet Priority: Minor Developping web services with Seam, my EAR is well deployed under the .metadata folder of Eclipse (.metadata/.plugins/org.jboss.ide.eclipse.as.core/JBoss_4.2_Runtime_Server/deploy/), but the WSDLs are deployed under the native JBoss deploy directory (/opt/jboss-4.2.3.GA/server/default/data/ for me). Hereunder, the log showing the problem : [...] 18:01:15,533 INFO [EJB3Deployer] Deployed: file:/media/donnees/Workspace/.metadata/.plugins/org.jboss.ide.eclipse.as.core/JBoss_4.2_Runtime_Server/deploy/odma-ws-ear.ear/odma-ws.jar/ [...] 18:01:18,906 INFO [WSDLFilePublisher] WSDL published to: file:/opt/jboss-4.2.3.GA/server/default/data/wsdl/odma-ws-ear.ear/odma-ws.jar/InscriptionDeploiement3850228908865809879.wsdl [...] -- 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

13 years

5
15
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues February 2010