title: JAXB POJO's generated from WDSL seem cumbersome to use
body: <p>I'm not new to SOAP and turning WSDL's into POJO's. I've managed to connect to the web service and retrieve the data I need.</p>
  
  <p>The problem rests in traversing the object hierarchy that the WSDL created. 
  Most of the variables stored in the generated classes are of the type <code>JAXBElement&lt;NameOfJavaClassHere&gt;</code>. So when ever I want that object I need to issue a call like <code>ListOfEntitiesType loe = ents.getListOfEntities().getValue();</code> The <code>.getValue()</code> is where I have my issue.</p>
  
  <p>Does there exist a way of making this a smoother integration? If I have to keep doing a <code>getValue()</code> it's going to be a death of 1000 cuts.</p>
  
  <p>It feels like they left in a level of indirection at the client level that they didn't need to.</p>
  
  <p>I've tried to unmarshal the xml with a <code>JAXBContent</code> object, there are a lot of examples on the net on how to do this, but it didn't work in this case. My object came out as null.</p>
  
  <p>Should the WSDL not make POJO's that don't need all this casting about with generics?</p>
  
  <p>Did I use the wrong settings on my <code>wsimport</code> command that came with java 1.7?</p>
  
  <p>Should I use a different wsimport-ish program altogether to generate my POJO's?</p>
  
  <p>If I have to stick with the <code>.getValue()</code> thing, I think I'd much rather make an xpath interface to the raw XML or turn the whole thing into Hashtables and ArrayLists than deal with this. </p>
  
  <p>At least then, I'd have direct access to the info I want.</p>