January 2010 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBDS-1055) Names of the links are missed on Welcome screen in JBDS.

by Anton Klimkovich (JIRA)

Names of the links are missed on Welcome screen in JBDS. -------------------------------------------------------- Key: JBDS-1055 URL: https://jira.jboss.org/jira/browse/JBDS-1055 Project: JBoss Developer Studio Issue Type: Bug Affects Versions: 3.0.0.CR1 Environment: Version: 3.0.0.CR1 Build id: v201001060655N Build date: 201001060704 Reporter: Anton Klimkovich Assignee: Denis Golovin EXECUTE: Install JBDS EXECUTE: Run JBDS 3.0.0.CR1 Build id: v201001060655N FAILURE: Names of the links are missed on Welcome screen. Screenshots 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

16 years, 3 months

1
3
0 / 0

[JBoss JIRA] Created: (JBIDE-5291) Generalize the code used to handle source to target template mappings

by Tom Fennelly (JIRA)

Generalize the code used to handle source to target template mappings --------------------------------------------------------------------- Key: JBIDE-5291 URL: https://jira.jboss.org/jira/browse/JBIDE-5291 Project: Tools (JBoss Tools) Issue Type: Task Components: smooks Reporter: Tom Fennelly Fix For: 3.1.0.CR1 I'm wondering can we generalize the editor parts that handle the mappings between the Java Mappings and the target templating model. I probably didn't lay out my thoughts clearly enough on this, but what I was hoping for was that the target model parts would be agnostic of target message format (CSV, XML etc) and the templating technology used - FreeMarker only now, but I've structured the templating API to allow us add other TemplateBuilder impls e.g. for XSLT. What I see at the moment in the editor is that when I attempt to make a mapping connection, I see the FreemarkerCSVNodeGraphicalModel and FreemarkerCSVContentGenerator editor model parts on the call stack. I may be reading the code incorrectly, but I would only expected to see totally generic editor parts at play here... imo, this mapping part of the process should be totally generic i.e. exactly the same, no matter what the target message format and templating tech. I know I might just be reading the code incorrectly and I don't really understand the EMF process, but I thought I should add this JIRA anyway so as to allow it be tracked ... if I'm talking rubbish, we can just reject this JIRA :) -- 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, 3 months

3
17
0 / 0

[JBoss JIRA] Created: (JBDS-1052) JBDS docs release bundle

by Svetlana mukhina (JIRA)

JBDS docs release bundle ------------------------- Key: JBDS-1052 URL: https://jira.jboss.org/jira/browse/JBDS-1052 Project: JBoss Developer Studio Issue Type: Task Components: documentation Affects Versions: 2.1.0 Reporter: Svetlana mukhina Assignee: OLga Chikvina Fix For: 3.0.0.CR1 Update guides versions, create doc bundle with com. styles for JBDS release 3.0.0.CR1 with index page, use index page from the previous releases only changes version, check that all guides versions are available from index page, make sure all guides for JBDS are in the bundle. -- 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, 3 months

2
5
0 / 0

[JBoss JIRA] Created: (JBIDE-5638) Preview doesn't fully support h:graphicImage for JSF 2

by Juergen Zimmermann (JIRA)

Preview doesn't fully support h:graphicImage for JSF 2 ------------------------------------------------------ Key: JBIDE-5638 URL: https://jira.jboss.org/jira/browse/JBIDE-5638 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF Affects Versions: 3.1.0.CR1 Reporter: Juergen Zimmermann JSF 2 enhances h:graphicImage, e.g.: a) <h:graphicImage ... name="hs-logo.gif" library="images" ...> is the same as b) <h:graphicImage ... value="#{resource['images:hs-logo.gif']}" ...> Variant b) works fine in the previewer. But variant a) doesnt -- although it's much more convenient for page authors. -- 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, 3 months

4
9
0 / 0

[JBoss JIRA] Created: (JBIDE-5675) Increase width and depth of Smooks automated testing

by Brian Fitzpatrick (JIRA)

Increase width and depth of Smooks automated testing ---------------------------------------------------- Key: JBIDE-5675 URL: https://jira.jboss.org/jira/browse/JBIDE-5675 Project: Tools (JBoss Tools) Issue Type: Task Components: smooks Reporter: Brian Fitzpatrick Fix For: LATER Now that we have started putting together some automated tests, it's made me think again about what it is we should be testing... At a high level, we have some basic functional areas... Setting the input data, mapping to some Java Classes, and then taking the data from the Java Classes and outputting to some other format (such as CSV or XML (XSD)). We take input from: * XML/XHTML files * Incoming Java classes (meeting JavaBean-type interfaces) * XSD/WSDL files * CSV files * EDI files * JSON files * Custom files (what requirements do custom Smooks inputs have?) So we need to test to make sure that a variety of these input types can be successfully brought into the editor without errors. But since we only really support a limited set of inputs, this should remain pretty stable if we come up with a few solid examples of each. Tests should include edge cases such as Java Classes that don't match the Java Bean structure, invalid files, empty files, etc. The next area is then the Java Mapping task, where we provide a facility for users to import Java classes to map their input to. These java classes need to meet the Java Bean-type structure. This Java Mapping should be tested against: * Java Classes that don't match the Java Bean-type structure * Simple classes (single class vs. collection) * Collection of simple classes * Collection of compound classes And the final area at this point is applying a template - either CSV or XML (XSD). This mapping between the Java Mapping task and the output template should mix/match a number of things, including but not limited to: * (Same things we tested the Java Mapping against) * Java Classes that don't match the Java Bean-type structure * Simple classes (single class vs. collection) * Collection of simple classes * Collection of compound classes Plus: * Single-field CSV (field1) * Multi-field CSV (field1,field2,field3,...) * Simple XML (XSD) - i.e. XSD with only simple types * Complex XSD - multiple complex types * Invalid XSD * Blank XSD Generally I just want us to try and automate as many tests as we can. Dart, Tom & I can help you with this process once we get through the release. Ultimately we need to think of as many weird or strange things as we can to start hitting fringe cases that our users may try. Users are talented in the ways they will try to make tools work. And I have to admit I've used the occasional screwdriver to pound in a nail (typically unsuccessfully) so we should anticipate the user will try and do the same thing with the Smooks editor. The better we build our test suite, the better off we'll be as we add additional template types, new functionality, and continue to bang on this thing. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBIDE-5644) Java bean "srcPath" not being set properly in some situation

by Tom Fennelly (JIRA)

Java bean "srcPath" not being set properly in some situation ------------------------------------------------------------ Key: JBIDE-5644 URL: https://jira.jboss.org/jira/browse/JBIDE-5644 Project: Tools (JBoss Tools) Issue Type: Bug Components: smooks Reporter: Tom Fennelly Assignee: Xue Peng Fix For: 3.1.0.CR2 In some situations, the java bean srcPath is not being worked out properly. See the following flash: http://www.screencast.com/t/MDcyN2Nh I've tried other examples that work OK. The only difference I can see is that in the case of the example shown in the flash, there's just a single bean in the model. Perhaps it's something to do with the fact that it's the "root" bean? -- 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, 3 months

3
5
0 / 0

[JBoss JIRA] Created: (JBIDE-5289) Don't re-scan all ELs every time when user invokes class/method/field refactoring.

by Alexey Kazakov (JIRA)

Don't re-scan all ELs every time when user invokes class/method/field refactoring. ---------------------------------------------------------------------------------- Key: JBIDE-5289 URL: https://jira.jboss.org/jira/browse/JBIDE-5289 Project: Tools (JBoss Tools) Issue Type: Task Components: JSF Reporter: Alexey Kazakov Assignee: Daniel Azarov Fix For: 3.1.0.GA Use PageContextFactory.createContext().getELReference() to get EL references which could be cached. -- 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, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (JBIDE-5671) Seam 2.2EAP projects are created with error marker pages.xml and login.page.xml

by Anton Klimkovich (JIRA)

Seam 2.2EAP projects are created with error marker pages.xml and login.page.xml ------------------------------------------------------------------------------- Key: JBIDE-5671 URL: https://jira.jboss.org/jira/browse/JBIDE-5671 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 3.1.0.CR1 Environment: JBoss Developer Studio Version: 3.0.0.CR1 Build id: v201001060655N Build date: 201001060704 Reporter: Anton Klimkovich Assignee: Alexey Kazakov Priority: Minor EXECUTE: Create Seam 2.2 EAP project FAILURE: Project is created with error marker on pages.xml and login.page.xml EXECUTE: Open pages.xml and login.page.xml in Editor and swith to Source. Error markers will disappear. -- 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, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-5581) XML catalog not complete for JBossAS 6.0.0.M1

by Juergen Zimmermann (JIRA)

XML catalog not complete for JBossAS 6.0.0.M1 --------------------------------------------- Key: JBIDE-5581 URL: https://jira.jboss.org/jira/browse/JBIDE-5581 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.1.0.M4 Reporter: Juergen Zimmermann JBossAS 6.0 supports JPA 2.0 which requires persistence_2_0.xsd. This schema file can be found in docs/schema and should be added to plugins\org.jboss.ide.eclipse.as.core_...jar within the subdirectory dtd. -- 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, 3 months

3
5
0 / 0

[JBoss JIRA] Created: (JBIDE-5665) Add stable JBoss Developer Studio 3.0 Examples site

by Snjezana Peco (JIRA)

Add stable JBoss Developer Studio 3.0 Examples site --------------------------------------------------- Key: JBIDE-5665 URL: https://jira.jboss.org/jira/browse/JBIDE-5665 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: project-examples Affects Versions: 3.1.0.CR1 Reporter: Snjezana Peco Assignee: Snjezana Peco Fix For: 3.1.0.CR2 -- 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, 3 months

1
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 January 2010