[Jboss-dev-forums] [Design of JBossXB] - Re: JBoss-4.0.4.GA and XB-1.0.0.CR5+

[<hei...@jb...>]

anonymous wrote : 
  | but the best solution would seem to be a patch to the jboss-system.jar that made the call to the unmarshal(java.lang.String, org.jboss.xb.binding.ObjectModelFactory, java.lang.Object) variation explicit.
  | 

I agree, it probably makes most sense to replace these calls. 
But if we chose this way i'd say we reinstate the DocumentBinding for the next XB release and stick to it until the next AS will be released. 

The problem on the WS side is, that we can't communicate differrent XB versions for different environments. And since we offer drop in replacements for the most current AS (different release cycles), we need XB to align to this strategy. 

I understand that the refactoring needs to be done. But what difference does it make to postpone it until the next AS release? 




View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3955919#3955919

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3955919