March 2009 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-2495) Merge JBESB-2492: Smooks transformer in WSSecurityInfoExtractor should probably use SAX filter

by Tom Fennelly (JIRA)

Merge JBESB-2492: Smooks transformer in WSSecurityInfoExtractor should probably use SAX filter ---------------------------------------------------------------------------------------------- Key: JBESB-2495 URL: https://jira.jboss.org/jira/browse/JBESB-2495 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.5 Reporter: Tom Fennelly Fix For: 4.6 Is currently using the DOM filter (default). Should use the SAX filter for performance reasons. -- 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, 11 months

3
6
0 / 0

[JBoss JIRA] Created: (JBESB-2494) Merge JBESB-2252: JBossRemotingMessageComposer should have the security extractors as fields and not create them everytime.

by Tom Fennelly (JIRA)

Merge JBESB-2252: JBossRemotingMessageComposer should have the security extractors as fields and not create them everytime. --------------------------------------------------------------------------------------------------------------------------- Key: JBESB-2494 URL: https://jira.jboss.org/jira/browse/JBESB-2494 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Rosetta, Transports Affects Versions: 4.4 CP1 Reporter: Tom Fennelly Assignee: Daniel Bevenius Fix For: 4.5 This task mainly concerns the WSSecurityInfoExtractor which uses Smooks and the current impl will in effect create a new Smooks instance upon every call. Making this a field will have it create only once. I'd did this so I bow my head in shame :( I discovered this issue when investigating this user forum thread: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4198266#4198266 -- 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, 11 months

3
5
0 / 0

[JBoss JIRA] Created: (JBESB-2186) monitoring.cfg.xml not found

by Kevin Conner (JIRA)

monitoring.cfg.xml not found ----------------------------- Key: JBESB-2186 URL: https://jira.jboss.org/jira/browse/JBESB-2186 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Management Reporter: Kevin Conner The configuration of the management services is currently broken, leaving an opportunity for the following exception to be thrown. org.hibernate.HibernateException: monitoring.cfg.xml not found at org.hibernate.util.ConfigHelper.getResourceAsStream(ConfigHelper.java:147) at org.hibernate.cfg.Configuration.getConfigurationInputStream(Configuration.java:1405) at org.hibernate.cfg.Configuration.configure(Configuration.java:1427) at org.jboss.soa.esb.monitoring.MonitoringSessionFactory.init(MonitoringSessionFactory.java:80) at org.jboss.soa.esb.monitoring.MonitoringSessionFactory.getInstance(MonitoringSessionFactory.java:68) at org.jboss.soa.esb.monitoring.client.OperationsCollector.getClassPatterns(OperationsCollector.java:84) at org.jboss.soa.esb.monitoring.client.OperationsCollector.collectData(OperationsCollector.java:165) at org.jboss.soa.esb.monitoring.client.OperationsCollectorAction.collectOperations(OperationsCollectorAction.java:72) The reason for this issue is that the monitoring services specified in jbossesb.esb have an implicit dependency on a jar provided in management.esb but management.esb has an explicit dependency on jbossesb.esb. This will, therefore, leave a window where the management configuration may be required *before* the jar has been loaded. The implicit dependency is caused by the requirement of jbossesb.esb/management-client.jar to access the monitoring.cfg.xml file included in management.esb/management-server.jar. -- 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, 11 months

3
5
0 / 0

[JBoss JIRA] Created: (JBESB-2455) SoapUIClientService does not populate request attributes

by Joakim Sandström (JIRA)

SoapUIClientService does not populate request attributes -------------------------------------------------------- Key: JBESB-2455 URL: https://jira.jboss.org/jira/browse/JBESB-2455 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.5, 4.4 CP2 Reporter: Joakim Sandström SoapUIClientService only appears to handle population of text elements and not the attributes. expected request: <soapenv:Body> <ns:updateCustomer customerId="124343"> <ns:name> <ns:firstName>FIRSTNAME</ns:firstName> actual request: <soapenv:Body> <ns:updateCustomer customerId="?"> <ns:name> <ns:firstName>FIRSTNAME</ns:firstName> -- 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, 11 months

3
5
0 / 0

[JBoss JIRA] Created: (JBESB-2381) XMLBeansModel: toProperties method should handle configs that contain attribute and element value content

by Tom Fennelly (JIRA)

XMLBeansModel: toProperties method should handle configs that contain attribute and element value content --------------------------------------------------------------------------------------------------------- Key: JBESB-2381 URL: https://jira.jboss.org/jira/browse/JBESB-2381 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.5 Reporter: Tom Fennelly Fix For: 4.6 The toProperties method currently only handles mapping values defined on the "value" attribute. It doesn't handle property values defined as element content, or both element and on the attribute. -- 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, 11 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-2236) Investigate drools flow support

by Kevin Conner (JIRA)

Investigate drools flow support ------------------------------- Key: JBESB-2236 URL: https://jira.jboss.org/jira/browse/JBESB-2236 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Process flow Affects Versions: 4.4 Reporter: Kevin Conner Fix For: 4.5 Attachments: bpm_orchestration_flow_1.zip -- 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, 11 months

2
11
0 / 0

[JBoss JIRA] Created: (JBESB-2492) Smooks transformer in WSSecurityInfoExtractor should probably use SAX filter

by Tom Fennelly (JIRA)

Smooks transformer in WSSecurityInfoExtractor should probably use SAX filter ---------------------------------------------------------------------------- Key: JBESB-2492 URL: https://jira.jboss.org/jira/browse/JBESB-2492 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.5 Reporter: Tom Fennelly Fix For: 4.6 Is currently using the DOM filter (default). Should use the SAX filter for performance reasons. -- 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, 11 months

3
3
0 / 0

[JBoss JIRA] Created: (JBESB-2456) Tidy up smooks instance manager

by Kevin Conner (JIRA)

Tidy up smooks instance manager ------------------------------- Key: JBESB-2456 URL: https://jira.jboss.org/jira/browse/JBESB-2456 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Transformation Service Affects Versions: 4.4 CP2 Reporter: Kevin Conner Fix For: 4.4 CP3 The smooks instance manager listenes to JMS Topics for configuration updates but we do not support this. We need to remove this code along with any other parts which may no longer be used. TomF says that the trunk codebase has already been updated so we need to pull those changes across. -- 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, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-1883) quickstart: business_ruleservice_ruleAgent has an extraneous processDefinition directory

by Burr Sutter (JIRA)

quickstart: business_ruleservice_ruleAgent has an extraneous processDefinition directory ---------------------------------------------------------------------------------------- Key: JBESB-1883 URL: https://jira.jboss.org/jira/browse/JBESB-1883 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.4 Reporter: Burr Sutter Priority: Minor The business_ruleservice_ruleAgent quickstart should have its processDefinition folder removed. -- 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, 11 months

3
2
0 / 0

[JBoss JIRA] Created: (JBESB-2446) The update to the message context has broken serialisation with older versions

by Kevin Conner (JIRA)

The update to the message context has broken serialisation with older versions ------------------------------------------------------------------------------ Key: JBESB-2446 URL: https://jira.jboss.org/jira/browse/JBESB-2446 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.5 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.6 The message context was previously unused but was modified, by me I must admit, so that we could usefully distinguish between message context and message contents. Unfortunately this breaks when an old version of a serialized message is read by the new version. The fix is straight forward, add the following into the ContextImpl for the serialized format. /** * Deserialise the object, checking for old versions. * @param ois The object input stream. * @throws IOException For IO exceptions during object deserialisation. * @throws ClassNotFoundException If dependent classes cannot be found. */ private void readObject(final ObjectInputStream ois) throws IOException, ClassNotFoundException { ois.defaultReadObject() ; if (context == null) { context = new HashMap<String, Serializable>() ; } } The XML variant is correct. -- 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, 11 months

1
4
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues March 2009