April 2008 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-1911) seam find references/declartions does not show exact location in xml (e.g. components.xml)

by Max Andersen (JIRA)

seam find references/declartions does not show exact location in xml (e.g. components.xml) ------------------------------------------------------------------------------------------ Key: JBIDE-1911 URL: http://jira.jboss.com/jira/browse/JBIDE-1911 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Reporter: Max Andersen Assigned To: Victor Rubezhny Fix For: 2.1 do a seam find ref on authenticator in a seam project and components.xml is one of the matches. But it just shows the file - not the actual location in it. -- 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

18 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (RHDS-265) import TLDs from jar files to Red Hat Palette

by Oleg Varaksin (JIRA)

import TLDs from jar files to Red Hat Palette --------------------------------------------- Key: RHDS-265 URL: http://jira.jboss.com/jira/browse/RHDS-265 Project: Red Hat Developer Studio Issue Type: Feature Request Affects Versions: 1.0.0.beta2 Environment: Windows XP, SP2 Reporter: Oleg Varaksin I have not been figured out how external TLDs, containing in jar files, can be added to the Red Hat Palette. Can we only add TLDs which are located under our imported projects ? I don't have TLDs in my projects, but I have TLDs (packed in jars) somewhere in Maven local repository. Sure, I can unpack any jar file, get the TLD file and then import it to rhds palette. But firstly, I have to place all unpacked TLDs into my project (so that Red Hat will be able to find them) and secondly, why Red Hat can't do that for me ? I want to import jar files with 3td party components directly. -- 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

18 years, 3 months

4
11
0 / 0

[JBoss JIRA] Created: (JBIDE-1291) Utilize JMX DeploymentScanner to ensure proper deployment

by Max Andersen (JIRA)

Utilize JMX DeploymentScanner to ensure proper deployment --------------------------------------------------------- Key: JBIDE-1291 URL: http://jira.jboss.com/jira/browse/JBIDE-1291 Project: JBoss Tools Issue Type: Feature Request Components: JBossAS Affects Versions: 2.0.0.CR1 Reporter: Max Andersen Fix For: 2.0.1 Jmx DeploymentScanner has suspendDeployment() and resumeDeployment() which could be usefull to call before/after deployment. See: http://docs.jboss.org/jbossas/javadoc/4.0.4/system/org/jboss/deployment/s... addURL() could be used to have our own eclipse workspace local deployment which won't pollute existing configurations. -- 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

18 years, 3 months

3
17
0 / 0

[JBoss JIRA] Created: (JBIDE-1453) New menu item and properties on component.xml editor tree item is redundant

by Denis Golovin (JIRA)

New menu item and properties on component.xml editor tree item is redundant --------------------------------------------------------------------------- Key: JBIDE-1453 URL: http://jira.jboss.com/jira/browse/JBIDE-1453 Project: JBoss Tools Issue Type: Feature Request Reporter: Denis Golovin Fix For: 2.0.0.GA -- 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

18 years, 3 months

4
11
0 / 0

[JBoss JIRA] Created: (JBIDE-895) Clean out jsf component

by Denis Golovin (JIRA)

Clean out jsf component ----------------------- Key: JBIDE-895 URL: http://jira.jboss.com/jira/browse/JBIDE-895 Project: JBoss Tools Issue Type: Sub-task Affects Versions: 2.0.0.Beta3 Reporter: Denis Golovin Fix For: 2.0.0.Beta4 -- 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

18 years, 3 months

3
6
0 / 0

[JBoss JIRA] Created: (JBIDE-1409) Unknown context variable name: entityManager

by Menashe (JIRA)

Unknown context variable name: entityManager -------------------------------------------- Key: JBIDE-1409 URL: http://jira.jboss.com/jira/browse/JBIDE-1409 Project: JBoss Tools Issue Type: Bug Components: JBoss Tools Core Affects Versions: 2.0.0.CR1 Environment: latest nightlybuild (dec 3) seam2.0.0 ecliple 3.3.1.1 Reporter: Menashe when em injection is used as in: @In private EntityManager entityManager; then validator fails with Unknown context variable name: entityManager although works fine with seam2 -- 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

18 years, 3 months

6
22
0 / 0

[JBoss JIRA] Created: (JBIDE-1905) Need to create new icons for actions

by Victor Rubezhny (JIRA)

Need to create new icons for actions ------------------------------------ Key: JBIDE-1905 URL: http://jira.jboss.com/jira/browse/JBIDE-1905 Project: Tools (JBoss Tools) Issue Type: Feature Request Affects Versions: 2.1 Reporter: Victor Rubezhny Assigned To: Victor Rubezhny Priority: Minor Fix For: 2.1 Need to create new icons for: - Find Seam Declarations action - Find Seam References action -- 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

18 years, 3 months

3
5
0 / 0

[JBoss JIRA] Created: (JBDS-225) Wrong dialog title in "Add JSF Capabilities" wizard

by Sergei Abragevich (JIRA)

Wrong dialog title in "Add JSF Capabilities" wizard --------------------------------------------------- Key: JBDS-225 URL: http://jira.jboss.com/jira/browse/JBDS-225 Project: Developer Studio Issue Type: Bug Affects Versions: 1.0.0.GA Reporter: Sergei Abragevich Assigned To: Max Andersen 1. Create a non-jsf web project: New -> Project -> Web -> Dynamic Web Project. 2. Right click the project folder - > JBoss Tools -> Add JSF Capabilities. The dialog is called "Import JSF Project". I guess it's not logical, should be something like "Add JSF Capabilities". -- 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

18 years, 3 months

4
6
0 / 0

[JBoss JIRA] Updated: (JBIDE-771) Context path don't work with JBOSS AS 4.2

by Max Andersen (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-771?page=all ] Max Andersen updated JBIDE-771: ------------------------------- Fix Version/s: 2.1.0.beta1 (was: 2.1) batch update of issues with 2.1 fix instead of the correct 2.1.b1 > Context path don't work with JBOSS AS 4.2 > ----------------------------------------- > > Key: JBIDE-771 > URL: http://jira.jboss.com/jira/browse/JBIDE-771 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JBossAS > Affects Versions: 2.0.1 > Environment: WindowsXP SP2 > rhds-win32-1.0.0.ALPHA.jar > Red Hat Developer Studio > Version: 1.0.0 > Build id: 1.0.0 > Reporter: Aliaksey Nis > Assigned To: Viacheslav Kabanovich > Fix For: 2.1.0.beta1 > > Attachments: ContextPath.PNG, ContextPath2.PNG > > > 1. From Web projects View do: Create new JSF project > 2. Select Template - KickStart, JSF version - 1.2, project name "test", context path - "test_test" > 3. Register this project on JBOSS AS 4.2 server > 4. Start server > 5. Use Run button on toolbar, link here will be like http://localhost:8080/test_test, click on it > 6. 404 error appears > 7. In browser command promt enter http://localhost:8080/test (project real name) - all works fine. -- 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

18 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBIDE-1785) Build results should be stored to be loaded when Eclipse restarts

by Viacheslav Kabanovich (JIRA)

Build results should be stored to be loaded when Eclipse restarts ----------------------------------------------------------------- Key: JBIDE-1785 URL: http://jira.jboss.com/jira/browse/JBIDE-1785 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Seam Affects Versions: 2.0.0.GA Reporter: Viacheslav Kabanovich Assigned To: Viacheslav Kabanovich Fix For: 2.1 Currently, each time Eclipse starts, all java and xml files that had contributed to Seam model, are parsed to restore it. Parsing takes a lot of time, a project with 1000 components takes 2 - 3 minutes to handle. We may not be able to improve it when full rebuild of project is selected, but we need to avoid that waste of time when once obtained build results are to be picked up by model at start. I propose to serialize parsed seam component declarations into xml file (which is now used just to keep paths of files that contribute to seam model). It is better to keep xml human-readable, so that it is easier to solve problems, especially that may arise at future modifications to Seam model. Testing will include iteration on seam component declaration in just built Seam project, each one serialized, deserialized, and compared to the original to assert that no changes occurred. -- 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

18 years, 3 months

2
7
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 April 2008