June 2009 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-4514) Improve performance of Seam Validator when a Java file is modified

by Julien Kronegg (JIRA)

Improve performance of Seam Validator when a Java file is modified ------------------------------------------------------------------ Key: JBIDE-4514 URL: https://jira.jboss.org/jira/browse/JBIDE-4514 Project: Tools (JBoss Tools) Issue Type: Feature Request Affects Versions: 3.0.0.GA Environment: JBossTools-ALL-win32-3.0.1.GA-R200905070146-H18, Seam 2.1.2.GA Reporter: Julien Kronegg Seam Validator checks EL expressions in WebContent/*.xhtml pages when a Java file is modified. On a Intel Core2 1.83 GHz T5600 machine with 2 GB RAM, it takes about 0.5 second per XHTML page generated by seam-gen (and modified using the workaround described in JBIDE-4512 to have no "property cannot be resolved" warnings). This is very high and has a big impact if you got a lot of XHTML pages (I got 150 of them!). So it would be nice if the whole validation process could take about 2-5 seconds (instead of about 2 minutes for me). -- 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, 10 months

3
18
0 / 0

[JBoss JIRA] Created: (JBIDE-3562) Open-Ons for Seam 2.1

by Victor Rubezhny (JIRA)

Open-Ons for Seam 2.1 --------------------- Key: JBIDE-3562 URL: https://jira.jboss.org/jira/browse/JBIDE-3562 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: jsp/jsf/xml source editing Reporter: Victor Rubezhny Assignee: Victor Rubezhny Fix For: 3.1.0 Review existing and add new Open-Ons for Seam 2.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, 10 months

5
8
0 / 0

[JBoss JIRA] Created: (JBIDE-2899) Allow export of server definitions without resetting launch config

by Gabriele Garuglieri (JIRA)

Allow export of server definitions without resetting launch config ------------------------------------------------------------------ Key: JBIDE-2899 URL: https://jira.jboss.org/jira/browse/JBIDE-2899 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS Affects Versions: 3.0.0.alpha Reporter: Gabriele Garuglieri Priority: Minor Currently we can export a JBoss Tools server definition using the default WTP server panel. There right clicking on the server opens a context menu whose last item is "Properties". Clicking it opens a panel where the "Switch Location" button cause the server definition to be exported from workspace metadata to "Servers" project. The problem is that doing so resets the launch configuration to the default values loosing any customization the user could have done. The "Switch Location" function for JBoss Tools server definition should not loose launch config customizations. (This is not strictly related but while you are at it, in the "Export Launch Configurations" panel the "JBoss Application Server Startup Configurations" items are missing the icons). -- 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, 10 months

3
6
0 / 0

[JBoss JIRA] Created: (JBIDE-3897) Creation of core module

by Rob Stryker (JIRA)

Creation of core module ----------------------- Key: JBIDE-3897 URL: https://jira.jboss.org/jira/browse/JBIDE-3897 Project: Tools (JBoss Tools) Issue Type: Task Components: core Affects Versions: 3.0.0.GA, 3.0.1.GA Reporter: Rob Stryker Assignee: Nick Boldt Fix For: 3.1.0 Time to recreate the core module. Tasks are as follows: 1) The module folder, with plugins / features / test category 2) an (empty) test plugin 3) an empty core plugin 4) an empty ui plugin 5) a feature 6) properly added into build 7) properly added to build download page 8) properly added to update site The purpose of this module will be to hold common well-designed multi-functional classes that will be usable by others. This will help reduce dependencies between modules by providing a common base. -- 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, 10 months

3
7
0 / 0

[JBoss JIRA] Created: (JBIDE-3837) Move classpath providers into some common area

by Rob Stryker (JIRA)

Move classpath providers into some common area ---------------------------------------------- Key: JBIDE-3837 URL: https://jira.jboss.org/jira/browse/JBIDE-3837 Project: Tools (JBoss Tools) Issue Type: Task Reporter: Rob Stryker Creation of common area is important. Whether it gets its own module or just its own plugin in as is debatable. This "core" must have zero dependencies on anything not wtp-related. The scope of this core (if located in the AS module) could also be a home for any and all overridden or borrowed WTP code that we find unsuitable in its current form, or any code that could have a common use but interfaces with WTP via extension points or subclassing. -- 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, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (JBDS-712) cannot edit or delete XPaths in JBoss Server View after a rename (view does not refresh?)

by Nick Boldt (JIRA)

cannot edit or delete XPaths in JBoss Server View after a rename (view does not refresh?) ----------------------------------------------------------------------------------------- Key: JBDS-712 URL: https://jira.jboss.org/jira/browse/JBDS-712 Project: Developer Studio Issue Type: Bug Components: servers Affects Versions: 2.0.0.GA Reporter: Nick Boldt 1. Open the JBoss Server View 2. Expand XML Configuration > Ports. 3. Right-click > New XPath 4. Enter a name "foo", a pattern "//server/mbean[@name='jboss:service=Naming']/attribute[@name='Port']" 5. Click preview - note there are 3 child nodes (if server is running; 2 if not). 6. Click OK 7. Expand new "foo" node; note the same three child nodes / files as seen in the preview So far, so good. Now to break things... 8. Right-click the new "foo" XPath > Edit XPath. Rename the new XPath "foo2". View updates w/ new label 9. Right-click the new "foo2" XPath > Delete XPath. Nothing happens. 10. Right-click the new "foo2" XPath > Edit XPath. Change the pattern to "//attribute[@name='Port']"; preview and note that there are now nested nodes. 11. Click OK; view does not update w/ change. 12. If your server is not running, you can rename it back to "foo" and then delete it, but after renaming the pattern still won't refresh. -- 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, 10 months

3
5
0 / 0

[JBoss JIRA] Created: (JBIDE-4056) cooperation with mylyn?

by arne anka (JIRA)

cooperation with mylyn? ----------------------- Key: JBIDE-4056 URL: https://jira.jboss.org/jira/browse/JBIDE-4056 Project: Tools (JBoss Tools) Issue Type: Feature Request Affects Versions: 3.0.0.GA Reporter: arne anka Priority: Minor Attachments: jboss.png i work on two projects alternately, one is a jboss seam project (say, A), one is totally unrelated (say, B). both projects are, in eclipse terms, always open. i swotch between them by using mylyn and working sets. the last week i worked on B and frequently experienced rather heavy resource usage because jboss tools did some operations, which were unnecessary because nothing changed in in A. looking into the progress view there was an entry about building workspace, "invoking JProject ARchives Builder on A", "System: Jboss Tools Update" (see attached screenshot). i don't know, if there's a more intelligent way, but maybe jboss tools could try to detect if the project is part of the mylyn task currently active and if not, stop any activity? -- 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, 10 months

3
16
0 / 0

[JBoss JIRA] Created: (JBIDE-4432) Add or move "Show experimental sites" from prefences to the Project Examples wizard

by Max Rydahl Andersen (JIRA)

Add or move "Show experimental sites" from prefences to the Project Examples wizard ----------------------------------------------------------------------------------- Key: JBIDE-4432 URL: https://jira.jboss.org/jira/browse/JBIDE-4432 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: project-examples Affects Versions: 3.1.0.M1 Reporter: Max Rydahl Andersen it is on the project examples site that users actually will take the choice if they want to use experimental or not. the property on the preference page can simply be the default. -- 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, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-4415) Failed while installing Seam 2.1

by David Hernandez (JIRA)

Failed while installing Seam 2.1 -------------------------------- Key: JBIDE-4415 URL: https://jira.jboss.org/jira/browse/JBIDE-4415 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.0.1.GA Environment: OS: Microsoft Windows SP3 en JDK: Sun JDK 6.0_4 Eclipse Ganymede SR2 (3.4.0) JBoss Tools plugins (JBossTools-ALL-win32-3.0.1.GA-R200905070146-H18) JBoss Seam 2.1.2 CR2 JBoss AS 4.2.2 GA ANT_HOME=C:\apache-ant-1.7.0 CATALINA_HOME=C:\Program Files\Apache Software Foundation\Apache Tomcat 6.0.18 JAVA_HOME=C:\Program Files\Java\jdk1.6.0_04 java_home and ant_home in the path Reporter: David Hernandez I create a new project using war deployment and all is fine, the .log file in the .metadata folder only contains this lines: !SESSION 2009-06-03 10:57:16.546 ----------------------------------------------- eclipse.buildId=M20090211-1700 java.version=1.6.0_04 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US Command-line arguments: -os win32 -ws win32 -arch x86 !ENTRY org.eclipse.ui.views.properties.tabbed 4 4 2009-06-03 10:58:56.453 !MESSAGE Contributor org.jboss.ide.eclipse.as.ui.views.JBossServerView cannot be created. Now, I try to create a project using the EJB deployment way and get an error that said "Failed while installing Seam 2.1" and the detailed description is "java.lang.IllegalArgumentException". To create the project I first configure the server in the "Jboss server view", later I create the new seam web project. In the first view I select "Dinamic web project with seam 2.1 (technology preview)", the other values are the default ones (jboss 4.2 runtime, dinamic web module 2.5 and jboss 4.2 server). When the seam facet view is show I select the seam runtime from my disk, create new connection to my postgreSQL local server, select DB tables already exists in database and select ejb as deployment way. the database schema and catalog names are left empty. Finally press the finish button and I get the error. the .log file now contains the exception: !SESSION 2009-06-03 10:57:16.546 ----------------------------------------------- eclipse.buildId=M20090211-1700 java.version=1.6.0_04 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US Command-line arguments: -os win32 -ws win32 -arch x86 !ENTRY org.eclipse.ui.views.properties.tabbed 4 4 2009-06-03 10:58:56.453 !MESSAGE Contributor org.jboss.ide.eclipse.as.ui.views.JBossServerView cannot be created. !ENTRY org.eclipse.wst.common.project.facet.core 4 0 2009-06-03 11:15:50.953 !MESSAGE Failed while installing Seam 2.1. !STACK 0 java.lang.IllegalArgumentException at org.eclipse.wst.common.project.facet.core.internal.FacetedProjectWorkingCopy.changeProjectFacetVersion(FacetedProjectWorkingCopy.java:858) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject$1.run(FacetedProject.java:290) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.modify(FacetedProject.java:319) at org.jboss.tools.seam.internal.core.project.facet.SeamProjectCreator.execute(SeamProjectCreator.java:270) at org.jboss.tools.seam.internal.core.project.facet.SeamFacetAbstractInstallDelegate.execute(SeamFacetAbstractInstallDelegate.java:188) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.callDelegate(FacetedProject.java:1394) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.modifyInternal(FacetedProject.java:401) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.mergeChangesInternal(FacetedProject.java:1134) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.access$2(FacetedProject.java:1070) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject$5.run(FacetedProject.java:1052) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.mergeChanges(FacetedProject.java:1062) at org.eclipse.wst.common.project.facet.core.internal.FacetedProjectWorkingCopy.commitChanges(FacetedProjectWorkingCopy.java:1828) at org.eclipse.wst.common.project.facet.ui.ModifyFacetedProjectWizard.performFinish(ModifyFacetedProjectWizard.java:388) at org.eclipse.wst.web.ui.internal.wizards.NewProjectDataModelFacetWizard.performFinish(NewProjectDataModelFacetWizard.java:276) at org.jboss.tools.seam.ui.wizard.SeamProjectWizard.performFinish(SeamProjectWizard.java:226) at org.eclipse.wst.common.project.facet.ui.ModifyFacetedProjectWizard$3.run(ModifyFacetedProjectWizard.java:330) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800) at org.eclipse.wst.common.project.facet.ui.ModifyFacetedProjectWizard$4.run(ModifyFacetedProjectWizard.java:344) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) The curious thing is that using the same tools (eclipse, seam framework, jboss as, java jdk, jboss tools and even microsoft windows) in other PC all works fine. -- 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, 10 months

5
12
0 / 0

[JBoss JIRA] Created: (JBIDE-3874) Maven integration

by Max Rydahl Andersen (JIRA)

Maven integration ----------------- Key: JBIDE-3874 URL: https://jira.jboss.org/jira/browse/JBIDE-3874 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: common Affects Versions: 3.0.0.GA Reporter: Max Rydahl Andersen Priority: Critical Fix For: 3.1.0 It is time to make sure our stuff works well with Maven, at least to the extent that the underline runtimes support it. First shot would be to add an adapter that allows m2eclipse controlled projects to activate the seam features. That would allow us still to bundle JBoss Tools without any dependencies to m2eclipse which still seem to drag in non-compatible plugins which we need to look into before tying us to m2eclipse. -- 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, 10 months

6
42
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 June 2009