[JBoss JIRA] Created: (JBESB-518) Exception logging
by Kevin Conner (JIRA)
Exception logging
-----------------
Key: JBESB-518
URL: http://jira.jboss.com/jira/browse/JBESB-518
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: 4.2 Milestone Release 1
Reporter: Kevin Conner
Assigned To: Mark Little
There are numerous locations in the code where exceptions are being logged at a high logging level. Some of these include locations where the exceptions are being rethrown or ignored.
It would be better if these exceptions were logged at DEBUG level and, if neccessary, accompanied with an appropriate logging message at a higher level.
--
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
18 years, 10 months
[JBoss JIRA] Created: (JBESB-603) Add the ability to specify the Smooks configuration directly on the action config.
by Tom Fennelly (JIRA)
Add the ability to specify the Smooks configuration directly on the action config.
----------------------------------------------------------------------------------
Key: JBESB-603
URL: http://jira.jboss.com/jira/browse/JBESB-603
Project: JBoss ESB
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Transformation Service
Affects Versions: 4.2
Reporter: Tom Fennelly
Assigned To: Tom Fennelly
Priority: Optional
Since we upgraded from Smooks 0.8 to 0.9, it's a lot easier to specify non-profiled transformations.
This has the following benefits:
1. Makes the transformation configs a lot easier to write and read.
2. Makes it easier for us to support specifying configurations directly on the action configuration.
3. Being able to specify non-profiled transformations means you don't have to specify the "to", "from" etc attributes on the actions in order to perform a transformation. You just specify the Smooks config file + the config file itself is a lot cleaner.
Over the weekend, I made the changes to support this and I think it cleans things up considerably. It's not checked in yet and won't be - unless I get the go-ahead.
I think the profiling stuff is very powereful and we can still support it. However, I think that for new users, it's a bit daunting so we should just save that for the more advanced usecases where you have a larger message set and you need to share transform configs across them (done via the console).
--
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
18 years, 11 months
websphere ESB xsl medition primitive
by abhishek
Hi
I am facing issues with the xsl tranformation in the mediation component of
websphere ESB
sceanrio requires mapping two different business objects, when mapping child
level objects the compiler does not show ny error but at runtime it shows
transformtion error
can anyone help in the same
18 years, 11 months