May 2009 - jboss-dev-forums - Jboss List Archives

[Design of JBoss Serialization] - Re: Mavenization status

by clebert.suconic＠jboss.com

"trustin" wrote : Also, please make sure the correct dependency versions were specified in the 'dependencies' section of the pom.xml. The JARs in the ${basedir}/libs directory didn't have version numbers in their file names, so I did wild guess. Thank you so much Trustin... David could upload a release already. I checked the produced JARS and it seemed ok. It will be much simpler uploading a fix after this. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4229802#4229802 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4229802

17 years

1
0
0 / 0

[Design of JBoss ESB] - Re: Synchronous calls inside the ESB

by Kevin.Conner＠jboss.com

The danger of this is the usual issue of transactions though, especially with transports such as JMS. Perhaps a better solution would be to try and formalise the idea of continuations, making this easier for developers to use. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4229725#4229725 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4229725

17 years

1
0
0 / 0

[Design of JBoss ESB] - Re: XSL and other transformation engines

by Kevin.Conner＠jboss.com

"tfennelly" wrote : Kevin doesn't want to discuss them here, so I'll wait until he decides the appropriate topic/location for them. Actually, Kevin wants this thread to stick to topic i.e. alternative transformation engines to smooks. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4229721#4229721 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4229721

17 years

1
0
0 / 0

[Design of JBoss ESB] - Re: Transformation Actions to handle specific use cases

by tfennelly

"tfennelly" wrote : A simple action for converting JSON to XML, allowing you to specify an EDI mapping model ala the Smooks EDIParser. Doh... scrap the second part of that sentence of course :) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4229681#4229681 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4229681

17 years

1
0
0 / 0

[Design of JBoss ESB] - Re: Transformation Actions to handle specific use cases

by tfennelly

A simple action for converting JSON to XML, allowing you to specify an EDI mapping model ala the Smooks EDIParser. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4229680#4229680 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4229680

17 years

1
0
0 / 0

[Design of JBoss ESB] - Re: Transformation Actions to handle specific use cases

by tfennelly

A simple action for converting EDI to XML, allowing you to specify an EDI mapping model ala the Smooks EDIParser. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4229679#4229679 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4229679

17 years

1
0
0 / 0

[Design of POJO Server] - Re: Various performance issues in core projects

by jaikiran

"jaikiran" wrote : | | The question however still remains, do we really need to register each MC bean as a MBean? | | Just looked at a sample MBean corresponding to a MC Bean, that gets registered by default (ex: jboss.deployment:id="HDScanner",type=Component). This MBean and other similar MBeans that are registered for each MC bean provide debug level information. The MBean has a listAttachments() method which doesn't provide much except the object ids/classnames of the attachments. Even the attributes of these MBeans are the kind of information that's just useful (IMO) for low level debugging. So shouldn't registering these as MBeans be an optional thing, and by default be turned off? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4229672#4229672 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4229672

17 years

1
0
0 / 0

[Design of JBoss ESB] - Re: Transformation Actions to handle specific use cases

by tfennelly

A simple action for converting CSV to XML, aloowing you to specify the CSV fields, field separators, root element name, record element name etc. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4229669#4229669 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4229669

17 years

1
0
0 / 0

[Design of JBoss ESB] - Re: Transformation Actions to handle specific use cases

by tfennelly

An action that allows you to perform some "rough" binding of data from an XML message into a simple Map structure might be useful. As an example of what I mean... XML: | <Order> | <header> | <orderId>1</orderId> | <orderDate>Wed Nov 15 13:45:28 EST 20061</orderDate> | <statusCode>0</statusCode> | </header> | <Customer userName="user1" firstName="Harry" lastName="Fletcher" state="SD"/> | <Product productId="364" title="The 40-Year-Old Virgin " price="29.98"/> | </Order> | Suppose the service is only interested in the header and product info in this message, the ESB Config for binding that data out of this message and into a Map based model (i.e. untyped and in a Map) might look something like: | <action name="bindRequestData" class="org.jboss.esb.actions.XMLToMapBinder"> | <property name="bindings"> | <bean beanId="header" element="order/header" /> | <bean beanId="product" element="order/Product" /> | </property> | </action> | This would allow the action following this action to access this info and use it in something like an MVEL or Groovy script e.g.: | def orderData = message.getBody().get(); | def price = orderData.product.price; | | if (price > 30.00) { | def orderStatus = orderData.header.statusCode; | def productId = orderData.product.productId; | | // Run some sort of check using the captured data... | } | Of course you could also just tell it to bind the complete message into a Map structure, but that has obvious performance issues. Also, the likes of Groovy can do this for you anyway. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4229667#4229667 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4229667

17 years

1
0
0 / 0

[Design of JBoss ESB] - Re: Transformation Actions to handle specific use cases

by tfennelly

As far as processing CSV data is concerned, I think one useful action might be one that allows you to more easily bind the fields in a CSV record set into a Java object. It could allow you to produce a List or Map (keyed on one of the fields) of objects. Should also allow you to simply populate the fields into a Map i.e. don't force the user into implementing a custom Java object. Might also be useful to allow this action to perform some basic splitting, by allowing you to specify the name of a Service to which each populated Java object could be sent for further processing. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4229656#4229656 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4229656

17 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums May 2009