April 2011 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-6362) Smooks: WSDL/SOAP Source

by Brian Fitzpatrick (JIRA)

Smooks: WSDL/SOAP Source ------------------------ Key: JBIDE-6362 URL: https://jira.jboss.org/browse/JBIDE-6362 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: smooks Affects Versions: 3.2.next Reporter: Brian Fitzpatrick Assignee: John Graham Fix For: 3.2.next Though users have the ability to go from an XML source to an XML target, it would be helpful to be able to map to/from WSDL or SOAP-specific targets. That would greatly simplify a good chunk of the transformations users are doing. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 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, 7 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, 7 months

2
4
0 / 0

[JBoss JIRA] Created: (JBIDE-5295) Add ability to configure an Execution Report on Run Configurations

by Tom Fennelly (JIRA)

Add ability to configure an Execution Report on Run Configurations ------------------------------------------------------------------ Key: JBIDE-5295 URL: https://jira.jboss.org/jira/browse/JBIDE-5295 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: smooks Reporter: Tom Fennelly Fix For: 3.1.0.GA -- 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, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-5695) Localize labels etc in FreemarkerXMLTemplateCreationWizardPage

by Tom Fennelly (JIRA)

Localize labels etc in FreemarkerXMLTemplateCreationWizardPage -------------------------------------------------------------- Key: JBIDE-5695 URL: https://jira.jboss.org/jira/browse/JBIDE-5695 Project: Tools (JBoss Tools) Issue Type: Task Components: smooks Affects Versions: 3.1.0.CR1 Reporter: Tom Fennelly Assignee: Tom Fennelly Priority: Minor Fix 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

14 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBIDE-6364) Smooks: EDI Templating

by Brian Fitzpatrick (JIRA)

Smooks: EDI Templating ---------------------- Key: JBIDE-6364 URL: https://jira.jboss.org/browse/JBIDE-6364 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: smooks Affects Versions: 3.2.next Reporter: Brian Fitzpatrick Assignee: John Graham Fix For: 3.2.next We need a new template for the Smooks Editor to handle EDI documents. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-6511) Smooks Editor doesn't support mapping to Virtual Models

by Stelios Koussouris (JIRA)

Smooks Editor doesn't support mapping to Virtual Models ------------------------------------------------------- Key: JBIDE-6511 URL: https://jira.jboss.org/browse/JBIDE-6511 Project: Tools (JBoss Tools) Issue Type: Bug Components: smooks Affects Versions: 3.1.1 Reporter: Stelios Koussouris Assignee: John Graham We have an XML using a HashMap class for the Java Mapping for the transformation. You can connect the TransformationRequestType from the XML to the HashMap but not the individual values to the hashmap values When I try to match the valueA from the XML to the HashMap's valueA it fails as the "arrow connection" doesn't connect but... Then trying to connect the roots succeeds but after connecting the roots I am still unable to connect valueA to valueA etc That sounds like a bgug -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

5
7
0 / 0

[JBoss JIRA] Created: (JBIDE-6782) Add EDI/Json reader in reader panel

by Xue Peng (JIRA)

Add EDI/Json reader in reader panel ----------------------------------- Key: JBIDE-6782 URL: https://jira.jboss.org/browse/JBIDE-6782 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: smooks Reporter: Xue Peng Assignee: Xue Peng 1.Add EDI/JSON reader in reader panel 2.Update the Selector generate with these kind reader -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-5797) Set default value for the bean property "Setter Method" field

by Tom Fennelly (JIRA)

Set default value for the bean property "Setter Method" field ------------------------------------------------------------- Key: JBIDE-5797 URL: https://jira.jboss.org/jira/browse/JBIDE-5797 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: smooks Reporter: Tom Fennelly Assignee: Tom Fennelly Fix For: LATER Default the "Setter Method" field value to the Javabean setter method name translation of the associated bean property e.g. if the property is "name", the default value shown in this field should be "setName". Only map this value to the config source if the user modifies it from the default. Mapping it otherwise would not break anything, but would be making the config more verbose than it needs to be. I think showing this default value is a good idea for usability reasons i.e. the field could be left blank, as is is now. I think that the user being able to see the default value should give them a clearer idea of what it's about and if it needs to be modified based on their model. -- 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, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBIDE-7244) usage reporting should use the eclipse usage data collector service

by Andre Dietisheim (JIRA)

usage reporting should use the eclipse usage data collector service ------------------------------------------------------------------- Key: JBIDE-7244 URL: https://jira.jboss.org/browse/JBIDE-7244 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: usage Affects Versions: 3.2.0.M2 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.2.0.CR1 eclipse has a usage data collector framework. we didn't want to use it since it's UI is not convincing and since we wanted to report with Google Analytics and it's superior analyze capabilities. The eclipse usage data collector backend (the service component) is prettiy nice and we might use it for collecting data. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
7
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 April 2011