October 2008 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBDS-443) GSG needs correction

by OLga Chikvina (JIRA)

GSG needs correction -------------------- Key: JBDS-443 URL: https://jira.jboss.org/jira/browse/JBDS-443 Project: Developer Studio Issue Type: Bug Affects Versions: 1.1.0.GA Reporter: OLga Chikvina Assignee: OLga Chikvina Fix For: 2.0.0.beta1 "1) Under Fig 3.23 http://localhost/workshop/myAction.seam should be http://localhost:8080/workshop/myAction.seam 2) Sect. 3.5.2 there was no Hibernate option for me after selecting >>. I had to go to the open perspective icon (the one on the left of figure 3.38) to see a Hibernate Option. Also I have found a feature in JBDS If you define a new seam project as described in section 3.1.2 Then repeat these steps using a new project name I find I cannot re-use the existing database connection. I get a "Driver class property is empty for selected 'DefaultDS' connection profile" error The only way I can find around this is to re-define the database connection to re-select the same database driver and re-enter the url as jdbc:hsqldb:hsql://localhost:1701 i.e all the same values as before. The above feature is only evident if I test the connection whilst in the JDBC Connection properties page. If I don't test the connection I can define as many new seam projects as I like. Sect. 4.2.1 If you add the code <% System.out.println("Hello World!"); %> into the hello.jsp when run it will actually output "Hello World" in the server log - it might be worth adding a note to say that, just incase people think it will be displayed in the browser. When you get to the point of running the application Figure 4.15 will actually display the result of <%= new java.util.Date() %> i.e. the <current_datetime> and not "Hello World" as shown - see attached screen shot." Comments are made by Shaun Appleton. -- 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

15 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-2842) Export wizard for BPMN to jPDL translation

by John Graham (JIRA)

Export wizard for BPMN to jPDL translation ------------------------------------------ Key: JBIDE-2842 URL: https://jira.jboss.org/jira/browse/JBIDE-2842 Project: Tools (JBoss Tools) Issue Type: Sub-task Reporter: John Graham Assignee: Feng Qian Fix For: 3.0.0.beta1 Create an Eclipse Export wizard for BPMN to jPDL translation -- 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

15 years, 8 months

2
4
0 / 0

[JBoss JIRA] Created: (JBIDE-2869) XSD based XML Source/Target not being used properly

by Tom Fennelly (JIRA)

XSD based XML Source/Target not being used properly --------------------------------------------------- Key: JBIDE-2869 URL: https://jira.jboss.org/jira/browse/JBIDE-2869 Project: Tools (JBoss Tools) Issue Type: Bug Components: smooks Reporter: Tom Fennelly Assignee: Xue Peng Fix For: 3.0.0.beta1 When a user selects an XSD as the Source/Target of a transform, they're not telling the Editor that they want to transform the XSD. They are telling the Editor they want to transform a message that conforms to the schema rules defined in the XSD. At present the editor just loads the XSD XML document and displays that as the Source/Target. What I think needs to happen is for the Editor to generate a valid "sample" message that conforms to the chosen schema and then use that as the source/target model in the Editor. Since this may not be trivial, this it the reason I suggested that for XML, the Editor should just offer the user the option to select a pre-generated "sample" XML file as the source/target model i.e. to leave the XSD based stuff for later. -- 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

15 years, 8 months

3
3
0 / 0

[JBoss JIRA] Created: (JBIDE-2838) Collapse/restore of mapping section causes incorrect resize

by John Graham (JIRA)

Collapse/restore of mapping section causes incorrect resize ----------------------------------------------------------- Key: JBIDE-2838 URL: https://jira.jboss.org/jira/browse/JBIDE-2838 Project: Tools (JBoss Tools) Issue Type: Bug Components: smooks Environment: FC8; Eclipse Ganymede Reporter: John Graham Assignee: Xue Peng Fix For: 3.0.0.beta1 Attachments: before-collapse.jpg Starting with a JavaBean2JavaBean mapping, collapse and restore of the mapping section does not size the data model trees correctly. (See attachments.) -- 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

15 years, 8 months

2
5
0 / 0

[JBoss JIRA] Created: (JBIDE-2840) Save attempt on XML2XML mapping fails

by John Graham (JIRA)

Save attempt on XML2XML mapping fails ------------------------------------- Key: JBIDE-2840 URL: https://jira.jboss.org/jira/browse/JBIDE-2840 Project: Tools (JBoss Tools) Issue Type: Bug Components: smooks Environment: FC8; Eclipse Ganymede Reporter: John Graham Assignee: Xue Peng Priority: Blocker Fix For: 3.0.0.beta1 Create an XML2XML mapping (see attached image). On save, a error dialog appears saying: "Error can't find the Analyzer for sourceID : org.jboss.tools.smooks.xml.viewerInitor.xml and the targetID : org.jboss.tools.smooks.xml.viewerInitor.xml " -- 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

15 years, 8 months

2
3
0 / 0

[JBoss JIRA] Deleted: (JBIDE-2874) GSG needs correction

by Svetlana mukhina (JIRA)

[ https://jira.jboss.org/jira/browse/JBIDE-2874?page=com.atlassian.jira.plu... ] Svetlana mukhina deleted JBIDE-2874: ------------------------------------ > GSG needs correction > -------------------- > > Key: JBIDE-2874 > URL: https://jira.jboss.org/jira/browse/JBIDE-2874 > Project: Tools (JBoss Tools) > Issue Type: Bug > Reporter: OLga Chikvina > Assignee: OLga Chikvina > > "1) Under Fig 3.23 http://localhost/workshop/myAction.seam should be http://localhost:8080/workshop/myAction.seam > 2) Sect. 3.5.2 there was no Hibernate option for me after selecting >>. I had to go to the open perspective icon (the one on the left of figure 3.38) to see a Hibernate Option. > Also I have found a feature in JBDS > If you define a new seam project as described in section 3.1.2 > Then repeat these steps using a new project name I find I cannot re-use the existing database connection. > I get a "Driver class property is empty for selected 'DefaultDS' connection profile" error > The only way I can find around this is to re-define the database connection to re-select the same database driver and re-enter the url as jdbc:hsqldb:hsql://localhost:1701 i.e all the same values as before. > The above feature is only evident if I test the connection whilst in the JDBC Connection properties page. If I don't test the connection I can define as many new seam projects as I like. > Sect. 4.2.1 If you add the code <% System.out.println("Hello World!"); %> into the hello.jsp when run it will actually output "Hello World" in the server log - it might be worth adding a note to say that, just incase people think it will be displayed in the browser. > When you get to the point of running the application Figure 4.15 will actually display the result of <%= new java.util.Date() %> i.e. the <current_datetime> and not "Hello World" as shown - see attached screen shot." > Comments are made by Shaun Appleton. -- 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

15 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBIDE-2874) GSG needs correction

by OLga Chikvina (JIRA)

GSG needs correction -------------------- Key: JBIDE-2874 URL: https://jira.jboss.org/jira/browse/JBIDE-2874 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.0.0.alpha Reporter: OLga Chikvina Assignee: OLga Chikvina Fix For: 3.0.0.beta1 "1) Under Fig 3.23 http://localhost/workshop/myAction.seam should be http://localhost:8080/workshop/myAction.seam 2) Sect. 3.5.2 there was no Hibernate option for me after selecting >>. I had to go to the open perspective icon (the one on the left of figure 3.38) to see a Hibernate Option. Also I have found a feature in JBDS If you define a new seam project as described in section 3.1.2 Then repeat these steps using a new project name I find I cannot re-use the existing database connection. I get a "Driver class property is empty for selected 'DefaultDS' connection profile" error The only way I can find around this is to re-define the database connection to re-select the same database driver and re-enter the url as jdbc:hsqldb:hsql://localhost:1701 i.e all the same values as before. The above feature is only evident if I test the connection whilst in the JDBC Connection properties page. If I don't test the connection I can define as many new seam projects as I like. Sect. 4.2.1 If you add the code <% System.out.println("Hello World!"); %> into the hello.jsp when run it will actually output "Hello World" in the server log - it might be worth adding a note to say that, just incase people think it will be displayed in the browser. When you get to the point of running the application Figure 4.15 will actually display the result of <%= new java.util.Date() %> i.e. the <current_datetime> and not "Hello World" as shown - see attached screen shot." Comments are made by Shaun Appleton. -- 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

15 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBIDE-2365) Eclipse editor for Smooks

by John Graham (JIRA)

Eclipse editor for Smooks ------------------------- Key: JBIDE-2365 URL: http://jira.jboss.com/jira/browse/JBIDE-2365 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: esb Reporter: John Graham Assigned To: John Graham Eclipse editor and supporting components for creating Smooks mapping and configuration files. Eventually will include ability to test, deploy, debug and monitor smooks transformations. -- 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

15 years, 8 months

3
9
0 / 0

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

by Maxim Areshkau (JIRA)

[ https://jira.jboss.org/jira/browse/JBIDE-1226?page=com.atlassian.jira.plu... ] Maxim Areshkau updated JBIDE-1226: ---------------------------------- Fix Version/s: 3.0.0.cr1 (was: 3.0.0.beta1) > 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: Maxim Areshkau > Fix For: 3.0.0.cr1 > > 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

15 years, 8 months

1
0
0 / 0

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

by Maxim Areshkau (JIRA)

[ https://jira.jboss.org/jira/browse/JBIDE-1226?page=com.atlassian.jira.plu... ] Maxim Areshkau reassigned JBIDE-1226: ------------------------------------- Assignee: Maxim Areshkau (was: Eugene Stherbin) > 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: Maxim Areshkau > Fix For: 3.0.0.beta1 > > 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

15 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues October 2008