July 2008 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Commented: (JBIDE-719) Hibernate Tools should be able to use a named Eclipse provided connection

by Max Rydahl Andersen (JIRA)

[ https://jira.jboss.org/jira/browse/JBIDE-719?page=com.atlassian.jira.plug... ] Max Rydahl Andersen commented on JBIDE-719: ------------------------------------------- the tem.use_jdbc_metadata_defaults is true by default we only set it to false in case of reverse enginering because here it is *not* required to know the dialect. Could you give me a testcase and stacktrace for it ? > Hibernate Tools should be able to use a named Eclipse provided connection > ------------------------------------------------------------------------- > > Key: JBIDE-719 > URL: https://jira.jboss.org/jira/browse/JBIDE-719 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Hibernate > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Priority: Critical > Fix For: 3.0.0.beta1 > > Attachments: EditConsolleConfig.JPG, EditConsolleConfig_Res1.jpg, EditConsolleConfig_Res2.jpg, EditConsolleConfigNew2.JPG, JBIDE-719.zip, NewSeamProj.JPG > > Original Estimate: 4 days > Remaining Estimate: 4 days > > currently we use the settings specified in hibernate.properties/cfg.xml/persistence.xml > Users should be able to say to use a named WTP provided database connection. -- 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

17 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBDS-343) Project loaded into JBoss DevStudio can't be opened, causes NullPointerException in "EJB3ClasspathContainer.getClasspathEntries()"

by David Tonhofer (JIRA)

Project loaded into JBoss DevStudio can't be opened, causes NullPointerException in "EJB3ClasspathContainer.getClasspathEntries()" ---------------------------------------------------------------------------------------------------------------------------------- Key: JBDS-343 URL: http://jira.jboss.com/jira/browse/JBDS-343 Project: Developer Studio Issue Type: Bug Affects Versions: 1.0.0.GA Environment: Linux Fedora 8, 2.6.24.7-92.fc8 Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_12-b04) Java HotSpot(TM) Client VM (build 1.5.0_12-b04, mixed mode, sharing) Reporter: David Tonhofer Assigned To: Max Rydahl Andersen A project exported from subversion into JBoss DevStudio cannot be opened. The Eclipse log shows NullPointerException, either at startup or later. Here is the one at startup: !ENTRY org.eclipse.core.jobs 4 2 2008-05-23 15:25:55.615 !MESSAGE An internal error occurred during: "Initializing Java Tooling". !STACK 0 java.lang.NullPointerException at org.jboss.ide.eclipse.as.classpath.core.ejb3.EJB3ClasspathContainer.getClasspathEntries(EJB3ClasspathContainer.java:113) at org.eclipse.jdt.internal.core.JavaModelManager.containerPutIfInitializingWithSameEntries(JavaModelManager.java:547) at org.eclipse.jdt.internal.core.SetContainerOperation.executeOperation(SetContainerOperation.java:49) at org.eclipse.jdt.internal.core.JavaModelOperation.run(JavaModelOperation.java:720) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1797) .... Speculation on what went wrong: The .classpath of the project has a Windows-Nature Absolute Path (a Bad Thing in our mixed environment), somehow created on an Eclipse with manually loaded-in JBoss Tools: <?xml version="1.0" encoding="UTF-8"?> <classpath> <classpathentry kind="src" path="src"/> <classpathentry kind="src" path="test"/> <classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/> <classpathentry combineaccessrules="false" kind="src" path="/jb_seam_demox-ejb"/> <classpathentry kind="lib" path="D:/jboss-seam-2.0.0.GA/lib/testng.jar"/> <classpathentry kind="con" path="org.jboss.ide.eclipse.as.classpath.core.ejb3.classpathContainer/JBoss 4.2 Server"/> <classpathentry kind="output" path="bin"/> </classpath> -- 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

17 years, 8 months

3
2
0 / 0

[JBoss JIRA] Updated: (JBIDE-1077) Seam refactoring tools

by Max Rydahl Andersen (JIRA)

[ https://jira.jboss.org/jira/browse/JBIDE-1077?page=com.atlassian.jira.plu... ] Max Rydahl Andersen updated JBIDE-1077: --------------------------------------- Fix Version/s: 3.0.0.beta (was: 3.0.0.alpha) > Seam refactoring tools > ---------------------- > > Key: JBIDE-1077 > URL: https://jira.jboss.org/jira/browse/JBIDE-1077 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Plan, Seam > Affects Versions: 2.0.0.Beta4 > Reporter: Denis Golovin > Assignee: Alexey Kazakov > Priority: Critical > Fix For: 3.0.0.beta > > Attachments: Screenshot.png > > -- 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

17 years, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBIDE-719) Hibernate Tools should be able to use a named Eclipse provided connection

by Max Rydahl Andersen (JIRA)

[ https://jira.jboss.org/jira/browse/JBIDE-719?page=com.atlassian.jira.plug... ] Max Rydahl Andersen updated JBIDE-719: -------------------------------------- Fix Version/s: 3.0.0.beta (was: 3.0.0.alpha) > Hibernate Tools should be able to use a named Eclipse provided connection > ------------------------------------------------------------------------- > > Key: JBIDE-719 > URL: https://jira.jboss.org/jira/browse/JBIDE-719 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Hibernate > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Priority: Critical > Fix For: 3.0.0.beta > > Attachments: EditConsolleConfig.JPG, EditConsolleConfig_Res1.jpg, EditConsolleConfig_Res2.jpg, EditConsolleConfigNew2.JPG, JBIDE-719.zip, NewSeamProj.JPG > > Original Estimate: 4 days > Remaining Estimate: 4 days > > currently we use the settings specified in hibernate.properties/cfg.xml/persistence.xml > Users should be able to say to use a named WTP provided database connection. -- 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

17 years, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBIDE-831) Prevented recursive attempt to activate part org.eclipse.ui.views.PropertySheet while still in the middle of activating part com.redhat.palette.swt

by Max Rydahl Andersen (JIRA)

[ https://jira.jboss.org/jira/browse/JBIDE-831?page=com.atlassian.jira.plug... ] Max Rydahl Andersen updated JBIDE-831: -------------------------------------- Fix Version/s: 3.0.0.beta (was: 3.0.0.alpha) > Prevented recursive attempt to activate part org.eclipse.ui.views.PropertySheet while still in the middle of activating part com.redhat.palette.swt > --------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-831 > URL: https://jira.jboss.org/jira/browse/JBIDE-831 > Project: Tools (JBoss Tools) > Issue Type: Bug > Affects Versions: ExadelStudioPro4 > Reporter: Anton Klimkovich > Assignee: Viacheslav Kabanovich > Priority: Optional > Fix For: 3.0.0.beta > > Attachments: Palette.txt, Properies View.PNG > > > Open Hello.jsp for example > Open Properties View > Set cursor to Vulue field in Properties View (look at screenshoot) > Open or close any Group in Palette > Error message will appeare. > Log Attached -- 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

17 years, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBIDE-503) Seam Event breakpoints

by Max Rydahl Andersen (JIRA)

[ https://jira.jboss.org/jira/browse/JBIDE-503?page=com.atlassian.jira.plug... ] Max Rydahl Andersen updated JBIDE-503: -------------------------------------- Fix Version/s: 3.0.0.beta (was: 3.0.0.alpha) > Seam Event breakpoints > ---------------------- > > Key: JBIDE-503 > URL: https://jira.jboss.org/jira/browse/JBIDE-503 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Seam > Reporter: Max Rydahl Andersen > Priority: Optional > Fix For: 3.0.0.beta > > > http://docs.jboss.com/seam/1.2.0.PATCH1/reference/en/html/events.html#d0e... > Use Events.addListener remotely to listen to events. > Need to have seam define a stable location to install a breakpoint in case we are listening. -- 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

17 years, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBIDE-1497) Use single base class for EL parsing

by Max Rydahl Andersen (JIRA)

[ https://jira.jboss.org/jira/browse/JBIDE-1497?page=com.atlassian.jira.plu... ] Max Rydahl Andersen updated JBIDE-1497: --------------------------------------- Fix Version/s: 3.0.0.beta (was: 3.0.0.alpha) > Use single base class for EL parsing > ------------------------------------ > > Key: JBIDE-1497 > URL: https://jira.jboss.org/jira/browse/JBIDE-1497 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: Cleanup > Affects Versions: 2.0.0.GA > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Fix For: 3.0.0.beta > > Original Estimate: 1 week, 2 days > Remaining Estimate: 1 week, 2 days > > We use different classes to parce EL: > org.jboss.tools.common.model.util.ELParser (Used by JSF Conten Assist and VPE bundle resolver) > org.jboss.tools.seam.internal.core.el.SeamELTokenizer (Used by Seam Content Assist and Validator) > org.jboss.tools.jsf.text.ext.hyperlink.JSPExprHyperlinkPartitioner (Used by JSF Hiperlinks) > We have to refactor it to use one Basic Parcer for EL and maybe have some implementation for special cases if we need it. -- 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

17 years, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBIDE-351) Clean out bad exception handling

by Max Rydahl Andersen (JIRA)

[ https://jira.jboss.org/jira/browse/JBIDE-351?page=com.atlassian.jira.plug... ] Max Rydahl Andersen updated JBIDE-351: -------------------------------------- Fix Version/s: 3.0.0.beta (was: 3.0.0.alpha) > Clean out bad exception handling > -------------------------------- > > Key: JBIDE-351 > URL: https://jira.jboss.org/jira/browse/JBIDE-351 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Cleanup > Affects Versions: 2.0.0.GA > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Priority: Critical > Fix For: 3.0.0.beta > > > weed out all ex.printStackTrace() by either > a) remove them (and their catch clause) > b) replace them with log to the error log > There is waay to many of 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

17 years, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBIDE-1226) Various bugs in visual previews of richfaces components

by Max Rydahl Andersen (JIRA)

[ https://jira.jboss.org/jira/browse/JBIDE-1226?page=com.atlassian.jira.plu... ] Max Rydahl Andersen updated JBIDE-1226: --------------------------------------- Fix Version/s: 3.0.0.beta (was: 3.0.0.alpha) > Various bugs in visual previews of richfaces components > ------------------------------------------------------- > > Key: JBIDE-1226 > URL: https://jira.jboss.org/jira/browse/JBIDE-1226 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Visual Page Editor > Reporter: Gavin King > Assignee: Sergey Vasilyev > Fix For: 3.0.0.beta > > Attachments: calendar.png, calendar_ve.png, dataDefinitionList.png, dataDefinitionList_ve.png, dataTable.png, dataTable_ve.png, dropDownMenu.png, dropDownMenu_ve.png, inputNumberSlider.png, inputNumberSlider_ve.png, modalPanel.png, modalPanel_ve.png, panelBar.png, panelBar_ve.png, panelMenu.png, panelMenu_ve.png, status.png, status_ve.png, toolTip.png, toolTip_ve.png, tree.png, tree_ve.png > > > Here's a list of previews that need fixing: > rich:calendar won't popup, and puts the button in the wrong place > rich:dataDefinitionList broken > rich:dropDownMenu nonfunctional > rich:panelMenu nonfunctional > rich:panelBar functional, but rendering is broken > rich:toolTip nonfunctional > rich:modalPanel nonfunctional > rich:dataTable broken > rich:tree sorta works, but the nodes are not functional and don't render as links > rich:inputNumberSlider and other sliders are ugly > a4j:status should show some kind of preview -- 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

17 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBIDE-2515) Jboss Tools. Seam EJB3 Web Project does not properly deploy jar files on Jboss AS 4.2 Server deploy directory.

by Anthony Yulo (JIRA)

Jboss Tools. Seam EJB3 Web Project does not properly deploy jar files on Jboss AS 4.2 Server deploy directory. -------------------------------------------------------------------------------------------------------------- Key: JBIDE-2515 URL: http://jira.jboss.com/jira/browse/JBIDE-2515 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 2.0.1 Environment: WinXP, Eclipse Europa 3.2, Jboss AS 4.2, Seam 2.0 Technology Preview. Reporter: Anthony Yulo Fix For: 2.0.1 I have created a skeleton seam web project using Jboss Tools wizard. I set it to be an EJB rather than a WAR deployment. The wizard generated 4 folders/projects MyProj, MyProj-ear, MyProj-ejb, MyProj-test. I try to run the skeleton project on MyProj, right click on the folder and choose Run-As.... Now when the built-in browser, the page cannot be displayed appears and there is a stack-trace on the console. The console prints DeploymentException saying that the jar file jboss-seam.jar cannot be found at the deploy directory /JbossAs/default/deploy/MyProj-ear.ear/ As a workaround, I selected all jar files on the Project folder MyProj-ear and copied it manually to the deploy directory ../../deploy/MyProj-ear.ear. Jboss Tools should copy or upload these jar files to the deploy directory. -- 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

17 years, 8 months

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