[Jboss-dev-forums] [Design of JBossXB] - Re: POJO Schema parsing

[<sco...@jb...>]

I think incorporating the key into the entry as an attribute is too limiting. In terms of the difference between:


  | <map>
  |     <entry>
  |          <key><set><value>1</set></key>
  |          <value>collection><value>2</value></collection></value>
  |     </entry>
  | </map>
  | 
and:

  | <map>
  |       <key><set><value>1</set></key>
  |       <value>collection><value>2</value></collection></value>
  | </map>
  | 

I don't think its an issue of the parser not handling it, but rather having to introduce an uneccessary compilication in the handling of the parser stack state to effectively combine the key and value elements into a composite context at the object factory layer. Alexey could better speak to whether this is an actual complication in the current object factory though. However, since the entry element really does not translate to a single object as far as the java.util.Map api is concerned, the pair does have to be dealt with, and I don't see that its much easier to keep track of this by adding an entry element since the pair container can just as easily be created at the start of the key element as a containing entry element.

I browsed through the jaxb2.0 spec again, and they don't support map type of collections. Only arrays and list type of collections are supported so this is a construct that won't be supported other than by proprietary bindings.


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

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