July 2009 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBDS-808) Incorrect Seam and JBoss AS version after JBDS with EAP 5 installation.

by Anton Klimkovich (JIRA)

Incorrect Seam and JBoss AS version after JBDS with EAP 5 installation. ------------------------------------------------------------------------ Key: JBDS-808 URL: https://jira.jboss.org/jira/browse/JBDS-808 Project: Developer Studio Issue Type: Bug Components: seam, servers Affects Versions: 2.1.0 Environment: jbdevstudio-eap-win32-2.1.0.GA-N200907270215-H117 Reporter: Anton Klimkovich Assignee: Denis Golovin EXECUTE: Install JBDS build with EAP 5 EXECUTE: Look at Server Runtimes Environments FAILURE: JBoss AS 5.0 from EAP 5 marked as EAP 4.3 EXECUTE: Preferences->JBoss Tools-> web-> Seam FAILURE: Seam 2.2 marked as 2.0 -- 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

16 years, 8 months

4
5
0 / 0

[JBoss JIRA] Created: (JBDS-738) Add support for JBoss AS 5.1

by Nick Boldt (JIRA)

Add support for JBoss AS 5.1 ---------------------------- Key: JBDS-738 URL: https://jira.jboss.org/jira/browse/JBDS-738 Project: Developer Studio Issue Type: Feature Request Affects Versions: 2.1.0 Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 2.1.0 Add support for new AS 5.1.0 in build system & installer, released last week. https://sourceforge.net/project/showfiles.php?group_id=22866&package_id=1... -- 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

16 years, 8 months

3
4
0 / 0

[JBoss JIRA] Created: (JBIDE-4555) GenerateEntitiesWizard warning should be changed.

by Dmitry Geraskov (JIRA)

GenerateEntitiesWizard warning should be changed. ------------------------------------------------- Key: JBIDE-4555 URL: https://jira.jboss.org/jira/browse/JBIDE-4555 Project: Tools (JBoss Tools) Issue Type: Quality Risk Reporter: Dmitry Geraskov Assignee: Dmitry Geraskov Priority: Minor GenerateEntitiesWizard shows warning: " Impossible to check that hibernate dialect is set.". But in most cases it isn't more necessary for us as we could determine what is the dialect should be used. The meesage either should be removed either should be shown when we couldn't determine the dialect. Second variant requires from us to read specified driver, but it could be difficult as we haven't read dialect before. -- 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

16 years, 8 months

1
4
0 / 0

[JBoss JIRA] Created: (JBIDE-4680) add conf-relative paths for default filesets

by Rob Stryker (JIRA)

add conf-relative paths for default filesets -------------------------------------------- Key: JBIDE-4680 URL: https://jira.jboss.org/jira/browse/JBIDE-4680 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS Affects Versions: 3.1.0.M2 Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 3.1.0.M3 Currently, relative paths are based on the getLocation() method of the runtime. For JBoss servers, this means a relative path should be something like server/default/deploy. The problem here is that the user may want to set up a default fileset relative to the concrete configuration of that server's runtime. Allow default filesets for jboss servers to have a relative path of {config}/conf/jboss-log4j.xml. This path can be translated to server/all/conf/jboss-log4j.xml when being added to the new server as a fileset. -- 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

16 years, 8 months

2
14
0 / 0

[JBoss JIRA] Created: (JBIDE-3451) VPE - Preferences - please remove or rename "Default Editor Tab"

by Vitali Yemialyanchyk (JIRA)

VPE - Preferences - please remove or rename "Default Editor Tab" ---------------------------------------------------------------- Key: JBIDE-3451 URL: https://jira.jboss.org/jira/browse/JBIDE-3451 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Visual Page Editor core Affects Versions: 3.0.0.cr1 Reporter: Vitali Yemialyanchyk Assignee: Maxim Areshkau Priority: Minor Maxim, as you told me "Default Editor Tab" selection means default editor tab selection for new created jsp file (for example), in other rest cases vpe remember it's last open state. When i press "Preferences" and "Default Editor Tab" i expect to change something usefull for current editor. We can easy remove it and always open "Visual/Source" for new created files. Or it should be renamed into something like this "Default Editor Tab for new VPE files" - this name help you avoid questions. -- 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

16 years, 8 months

4
17
0 / 0

[JBoss JIRA] Created: (JBIDE-4249) Update of dependent archives

by Ondrej Medek (JIRA)

Update of dependent archives ---------------------------- Key: JBIDE-4249 URL: https://jira.jboss.org/jira/browse/JBIDE-4249 Project: Tools (JBoss Tools) Issue Type: Bug Components: Archives Affects Versions: 3.0.0.GA Environment: Win XP, Eclipse 3.4.2 Build id: M20090211-1700 Reporter: Ondrej Medek Priority: Minor I have a two archives, one is x.jar (compressed) and x.ear (exploded). x.ear contains a fileset, which includes x.jar. So my directory structure is: x.jar ear/x.ear/ ear/x.ear/x.jar x.jar contains compiled Java classes. When I make a change in the Java code, the x.jar is properly updated, however, the x.ear contains the old version of x.jar. I have to select "Build Archive" action from the menu. -- 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

16 years, 8 months

4
9
0 / 0

[JBoss JIRA] Created: (JBIDE-4575) Nested archives are not updated when the respective files change in the workspace

by Flavio Costa (JIRA)

Nested archives are not updated when the respective files change in the workspace --------------------------------------------------------------------------------- Key: JBIDE-4575 URL: https://jira.jboss.org/jira/browse/JBIDE-4575 Project: Tools (JBoss Tools) Issue Type: Bug Components: Archives Affects Versions: 3.0.1.GA Environment: Linux mobile 2.6.30-ARCH #1 SMP PREEMPT Fri Jun 19 21:25:17 UTC 2009 i686 Intel(R) Core(TM)2 Duo CPU T7250 @ 2.00GHz GenuineIntel GNU/Linux Eclipse 3.4.2 JBoss Application Server 4.2.3.GA Reporter: Flavio Costa Fix For: 3.0.2.GA I'm currently experiecing some very strange. As I explained to Max on IRC couple days ago, I have that has a structure pretty much similar to what seam-gen generates (I've actually generated it through seam-gen and then modified some bits here and there) and I'm using Project Archives in order to have, mainly, fast redeploys of view artifacts (XHTMLs, CSS, JS, ...) and a better integration with IDE (publishing to the server inside eclipse, for example). Let's say the project is called "BugSample" in my workspace. Inside /BugSample/resources/META-INF there's an "application.xml" which is copied to /BugSample/build-artifacts/project-archives/BugSample.ear/META-INF. That's perfecly correct and as soon as I change /BugSample/resources/META-INF/application.xml, Project Archives "notices" that change and copy it to the correct directory and, as the application is published to the server and I have changed the application descriptor, the app is then redeployed. That is the proof that Project Archives is enabled and "should" be working. But my application is also composed by EJBs and some other POJOs and a view layer, so I must have, nested to the EAR, a JAR and a WAR. That's where the problem comes in. The JAR and the WAR were created "inside the EAR" (the attached image shows that). All my view stuff (XHTML, CSS,...) are inside /BugSample/view and are mapped in Project Archives to be copied to /BugSample/build-artifacts/project-archives/BugSample.ear/BugSample.war/. I guessed that whenever I change the content of any file inside /BugSample/view the WAR generated by Project Archives would be updated right way, the same way the application.xml affected the EAR archive. The same happens for the JAR. The project I'm having problem is available for download here: http://dcc.ufrj.br/~coutinho/jbtools/FenixTemplate.tar.bz2 Just extract it and import the project in Eclipse. If you need anymore info I'll be more than happy to provide. -- 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

16 years, 8 months

3
10
0 / 0

[JBoss JIRA] Created: (JBIDE-4622) Add icon for "Pending..." tree item of Hibernate CC

by Vitali Yemialyanchyk (JIRA)

Add icon for "Pending..." tree item of Hibernate CC --------------------------------------------------- Key: JBIDE-4622 URL: https://jira.jboss.org/jira/browse/JBIDE-4622 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Hibernate Affects Versions: 3.1.0.M2 Reporter: Vitali Yemialyanchyk Assignee: Vitali Yemialyanchyk Priority: Minor Fix For: 3.1.0.M3 This is a simple nice feature, I remember this functionality was implemented coupled with some patch, which hasn't get into the trunk. -- 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

16 years, 8 months

1
3
0 / 0

[JBoss JIRA] Created: (JBIDE-4695) Seam Generate Entities layout folder check is broke

by David Thompson (JIRA)

Seam Generate Entities layout folder check is broke --------------------------------------------------- Key: JBIDE-4695 URL: https://jira.jboss.org/jira/browse/JBIDE-4695 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 3.1.0.M2 Environment: Running on Galileo with JBoss Tools 3.1.0M3 Reporter: David Thompson Priority: Blocker Created project with seam-gen, imported into Eclipse. Checked the org.jboss.tools.seam.core.prefs and seam.project.web.root.folder is set to /projectName/view The layout directory exists within /projectName/view. Right click on the project and select New->Seam Generate Entities Red x appears with error stating "Folder '/ProjectName/layout' doesn't exist". However if you create the /ProjectName/layout folder and then generate the entities they are placed in /ProjectName/view/layout as they should. It appears the new check added in JBIDE-4012 isn't using the seam.project.web.root.folder property. -- 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

16 years, 8 months

3
2
0 / 0

[JBoss JIRA] Created: (JBIDE-4577) JBossAS 5.1 not supported for EJB and Web projects

by Juergen Zimmermann (JIRA)

JBossAS 5.1 not supported for EJB and Web projects -------------------------------------------------- Key: JBIDE-4577 URL: https://jira.jboss.org/jira/browse/JBIDE-4577 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.1.0.M2 Environment: Eclipse 3.5, WTP 3.1, JBossAS-Tools Nightly 2.1.0.M2-N200907061943-H341 Reporter: Juergen Zimmermann When creating an EJB and/or Web project there are no "EAR Libraries" provided to have the JARs of JBossAS 5.1 available. A screenshot will be provided. See also https://jira.jboss.org/jira/browse/JBIDE-3374 which claims to be resolved. -- 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

16 years, 8 months

3
11
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 July 2009