[JBoss JIRA] Created: (JBDS-1440) Smooks Java-To-XML FreeMarker Fails in ESB
by Will Dinyes (JIRA)
Smooks Java-To-XML FreeMarker Fails in ESB
------------------------------------------
Key: JBDS-1440
URL: https://jira.jboss.org/browse/JBDS-1440
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: SOA Platform
Affects Versions: 4.0.0.Beta1
Environment: java-1.6.0-sun-devel, JBDS 4.0.0.Beta1
Reporter: Will Dinyes
I created a smooks-java-to-xml.xml (attached) config via the Smooks tooling in JBDS to translate a simple bean (.java file attached) back to XML via Apply Template with an XSD (attached).
When deploying this to SOA-P and then running a test, I get the following exception (in part, full exception stack attached):
freemarker.core.InvalidReferenceException: Expression .vars["com"] is undefined on line 3, column 21 in free-marker-template.
freemarker.core.TemplateObject.assertNonNull(TemplateObject.java:124)
freemarker.core.DynamicKeyName._getAsTemplateModel(DynamicKeyName.java:75)
freemarker.core.Expression.getAsTemplateModel(Expression.java:89)
freemarker.core.Expression.getStringValue(Expression.java:93)
freemarker.core.DollarVariable.accept(DollarVariable.java:76)
freemarker.core.Environment.visit(Environment.java:208)
freemarker.core.MixedContent.accept(MixedContent.java:92)
freemarker.core.Environment.visit(Environment.java:208)
freemarker.core.Environment.process(Environment.java:188)
freemarker.template.Template.process(Template.java:232)
This seems to be a missing descriptor or library that isn't deployed to the server? Not sure what's causing this. Maybe Smooks Java-to-XML isn't something we can do through the tooling at this time?
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 10 months
[JBoss JIRA] Created: (JBIDE-8119) parent pom maintenance for 3.3 trunk and 3.2 stable_branch
by Nick Boldt (JIRA)
parent pom maintenance for 3.3 trunk and 3.2 stable_branch
----------------------------------------------------------
Key: JBIDE-8119
URL: https://issues.jboss.org/browse/JBIDE-8119
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 3.3.x
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 3.3.x
1. Increment parent pom in trunk to 0.0.2-SNAPSHOT
2. publish updated trunk parent pom @ version 0.0.2-SNAPSHOT, and deploy to nexus
3. Increment all pom.xml refs to parent pom to 0.0.2-SNAPSHOT in all repos (jbosstools, devstudio, teiid, pi4soa, savara, scribble)
(repeat process for 0.0.1-SNAPSHOT -> 0.0.1 in stable_branch just before release / GA respin)
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 10 months
[JBoss JIRA] Created: (JBIDE-6396) Filter wizard/Database Collector should correctly identify catalog, schema, and tables even when tables contain dots (".") in the name
by Michael Walker (JIRA)
Filter wizard/Database Collector should correctly identify catalog, schema, and tables even when tables contain dots (".") in the name
--------------------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-6396
URL: https://jira.jboss.org/browse/JBIDE-6396
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Reporter: Michael Walker
Attachments: JBIDE-tablename-with-dots-patch-mpw.txt
The DefaultDatabaseCollector uses StringHelper.qualifier(String) to determine the catalog and schema name for each table, given the fully-qualified name.
StringHelper.qualifier() assumes that everything proceeding the final "." in the fully-qualified name represents the qualifier.
This assumption breaks down if a table contains a dot in the name. This is found to be the case when working with MetaMatrix (and possibly Teiid).
The result is that the Filter Wizard will generate invalid filters, based on the incorrect naming of catalog and schema for each table.
As a fix, I modified DefaultDatabaseCollector to form the qualifier by using the known catalog and schema, rather than by using the StringHelper.qualifier method. I rebuilt tools and verified that this fixed the problem when working with MetaMatrix.
This may be better addressed by changing the behavior of StringHelper.qualifier() itself.
See forum discussion for details.
Patch attached.
--
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, 10 months