|
From: <hei...@jb...> - 2006-06-28 15:30:15
|
Previously (using XercesXSMarshaller) the reflection wrapper have been cached in the MappinObjectModelProvider. This could eagerly be populated and reused throughout several Marshaller invocations. Especially the WS usecases did benefit from this, because otherwise the same classes would have been introspected over and over again. When optimizing XB regarding the use of the reflection API, wouldn't it makes sense to extend the API that the callee could actually provide that mapping model, similar to what has been possible with the MappinObjectModelProvider? IMO usecases that work on the same object model /schema would greatly benefit in terms of performance. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3954087#3954087 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3954087 |