January 2010 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-1893) Can't add *.xhtml template using Preferenses -> JBossTools->Web->JSF->JSF Pages

by Anton Klimkovich (JIRA)

Can't add *.xhtml template using Preferenses -> JBossTools->Web->JSF->JSF Pages ------------------------------------------------------------------------------- Key: JBIDE-1893 URL: http://jira.jboss.com/jira/browse/JBIDE-1893 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF Affects Versions: 2.0.1 Reporter: Anton Klimkovich Priority: Minor EXECUTE: Create JSF with Facelets kickstart project EXECUTE: Create JSF1.2 kickstart project EXECUTE: Window->Preferenses -> JBossTools->Web->JSF->JSF Pages EXECUTE: Press Add button EXECUTE: Press Browse button ASSERT: Two projects available: JSF with Facelets and JSF1.2 kickstarts EXECUTE: Expand pages folder in JSF with Facelets project ASSERT: *.xhtml pages shoul be available . FAILURE: *.xhtml pages are not available . -- 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

14 years, 10 months

4
5
0 / 0

[JBoss JIRA] Created: (RHDS-321) Warning in the case of incorrect bean references

by Florian Marwede (JIRA)

Warning in the case of incorrect bean references ------------------------------------------------ Key: RHDS-321 URL: http://jira.jboss.com/jira/browse/RHDS-321 Project: Red Hat Developer Studio Issue Type: Feature Request Reporter: Florian Marwede Priority: Minor See forum thread. The warning should behave like a eclipse warning (yellow underline in the editor and also appear in problem view). It must be configurable, so you can switch it off when you manage your beans in a way RHDS can't analyze. -- 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

14 years, 10 months

5
7
0 / 0

[JBoss JIRA] Created: (JBIDE-2438) Support for backing bean configuration in Spring application context

by Claus Nyhus (JIRA)

Support for backing bean configuration in Spring application context -------------------------------------------------------------------- Key: JBIDE-2438 URL: http://jira.jboss.com/jira/browse/JBIDE-2438 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: jsp/jsf/xml source editing Reporter: Claus Nyhus Hi, When using Spring with JSF it is very compelling to define backing beans in Springs application context (either via XML configuration or annotations) rather than in faces-config.xml. The downside of this is that you cannot use completion on properties from the backing beans in JBoss tools when editing JSF pages (e.g. facelets files). It would be very nice if JBoss Tools could pick up backing beans from a Spring application context and treat them the same way backing beans from faces-config.xml is handled. Cheers /Claus References for defining backing beans in an Spring application context: http://prime.com.tr/cagataycivici/?p=92 http://prime.com.tr/cagataycivici/?p=94 -- 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

14 years, 10 months

4
5
0 / 0

[JBoss JIRA] Created: (JBIDE-5358) Change how beans are expanded when added via the bean add dialog

by Tom Fennelly (JIRA)

Change how beans are expanded when added via the bean add dialog ---------------------------------------------------------------- Key: JBIDE-5358 URL: https://jira.jboss.org/jira/browse/JBIDE-5358 Project: Tools (JBoss Tools) Issue Type: Task Components: smooks Reporter: Tom Fennelly Fix For: 3.1.0.GA At the moment, we iterate down the object model and add all sub-objects etc. This is looking a bit messy because: 1. It requires the user to expand out a tree in the bottom half of the bean creation dialog, selecting the sub-domain objects he/she wants to be added. 2. The beans all land on the canvas at the one time, which requires a load of rearranging etc I think it would be nicer for the user if only the bean class entered in the Bean Creation wizard was dropped on the canvas, with all it's properties, but not drop in the sub-domain classes, wired together etc (as now). If some of the properties are for sub-domain objects, the user should be able to right-click and add, resulting in that sub-domain object being added etc etc. The user can expand it out as they want. -- 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

14 years, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-5404) Smooks Drag and Drop Editor

by Jim Tyrrell (JIRA)

Smooks Drag and Drop Editor --------------------------- Key: JBIDE-5404 URL: https://jira.jboss.org/jira/browse/JBIDE-5404 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Jim Tyrrell Just saw a demo here: http://www.screencast.com/users/tfennelly/folders/Camtasia/media/4b184ca6... It would be nice to be able to reorder fields on either side of the graph when you are doing the Java Mapping. In other words it would be nice to not have to have lines cross if at all possible. It would be even better if this would be automatic that fields in an object would order the same way in both views. It would also be nice that dragging a field into a mapping would prompt for a dialogue box to ask/see if all the other like mappings should be applied rather then having to apply them. Quickstarts around the smooks editor that are easily importable into JBDS w/o any messing around with anything. -- 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

14 years, 10 months

4
5
0 / 0

[JBoss JIRA] Created: (JBIDE-5294) Add ability to control output result types in Run Configuration

by Tom Fennelly (JIRA)

Add ability to control output result types in Run Configuration --------------------------------------------------------------- Key: JBIDE-5294 URL: https://jira.jboss.org/jira/browse/JBIDE-5294 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: smooks Reporter: Tom Fennelly Fix For: 3.1.0.GA At the moment, it's outputting everything, which can be information overload. -- 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

14 years, 10 months

2
6
0 / 0

[JBoss JIRA] Created: (JBIDE-5233) Move properties from the "Options" page into the Properties view

by Brian Fitzpatrick (JIRA)

Move properties from the "Options" page into the Properties view ---------------------------------------------------------------- Key: JBIDE-5233 URL: https://jira.jboss.org/jira/browse/JBIDE-5233 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: smooks Reporter: Brian Fitzpatrick Assignee: Brian Fitzpatrick Once we get JBIDE-5203 completed, we can add these optional/global options to the Properties view instead of taking up a page for them if we decided the page is overkill. But we need to have the whole editor wired to the Outline view and then wire the Properties pages to both objects in the editor and in the outline view to make this work. This is not for the JBDS 3.1 release. Future work. -- 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

14 years, 10 months

3
5
0 / 0

[JBoss JIRA] Created: (JBIDE-5756) Namespace declarations not being "cleaned" out of config after associated config elements have ben removed

by Tom Fennelly (JIRA)

Namespace declarations not being "cleaned" out of config after associated config elements have ben removed ---------------------------------------------------------------------------------------------------------- Key: JBIDE-5756 URL: https://jira.jboss.org/jira/browse/JBIDE-5756 Project: Tools (JBoss Tools) Issue Type: Bug Components: smooks Reporter: Tom Fennelly Assignee: Tom Fennelly Fix For: 3.1.0.CR2 All smooks configuration parts have an associated configuration namespace, which is declared in a namespace/prefix declaration on the root element of the configuration. These namespace declarations get added when a specific config type is added to the configuration e.g. a prefix:namespace declaration for the "http://www.milyn.org/xsd/smooks/freemarker-1.1.xsd" namespace is added when a FreeMarker config is added. If all the configurations from a specific namespace are removed, so should the declaration for that namespace. -- 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

14 years, 10 months

2
4
0 / 0

[JBoss JIRA] Created: (JBIDE-5203) Smooks editor - wire up non-source pages to Outline view

by Brian Fitzpatrick (JIRA)

Smooks editor - wire up non-source pages to Outline view -------------------------------------------------------- Key: JBIDE-5203 URL: https://jira.jboss.org/jira/browse/JBIDE-5203 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: smooks Affects Versions: 3.1.0.M4 Reporter: Brian Fitzpatrick Assignee: Brian Fitzpatrick Fix For: 3.1.0.CR1 Hook up the non-source pages to the Outline view This is a "nice to have" - but not critical for the first release. But it should be looked at in the future. -- 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

14 years, 10 months

3
5
0 / 0

[JBoss JIRA] Created: (JBIDE-5440) Update Smooks Examples to Minimize User Steps

by Brian Fitzpatrick (JIRA)

Update Smooks Examples to Minimize User Steps --------------------------------------------- Key: JBIDE-5440 URL: https://jira.jboss.org/jira/browse/JBIDE-5440 Project: Tools (JBoss Tools) Issue Type: Task Components: smooks Affects Versions: 3.1.0.GA Reporter: Brian Fitzpatrick Assignee: Tom Fennelly Fix For: 3.1.0.GA We have a bunch of quickstarts - but all the quickstarts require that you manually set the sample input data when you import them. can we tweak those to include the metadata for the sample input? This would include not only the samples from the Smooks project, but the ESB samples that include Smooks. This is basically just making sure that the sample input data is configured in the configuration so the user doesn't have to configure it by hand. -- 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

14 years, 10 months

2
4
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 January 2010