There are 2 parts though, the class generation and then the binding.
As long as the plugin allows some hook into the binding process as
well...
On Tue 10 Jul 2012 09:09:14 AM CDT, Hardy Ferentschik wrote:
>
> On Jul 10, 2012, at 4:04 PM, Steve Ebersole wrote:
>
>> If you can get JAXB to perform
On Jul 10, 2012, at 4:04 PM, Steve Ebersole wrote:
> If you can get JAXB to perform that binding for you great! There are lots of
> places where we have this.
>
> Just to be clear, however, we cannot change the XSD to accomplish this in a
> way that means changes to end-user syntax.
I think
If you can get JAXB to perform that binding for you great! There are
lots of places where we have this.
Just to be clear, however, we cannot change the XSD to accomplish this
in a way that means changes to end-user syntax.
On 07/10/2012 03:43 AM, Hardy Ferentschik wrote:
> Type checking always
Type checking always sucks in this context. I also would try to minimize it as
much as possible.
Provided your suggested change still allows to parse existing mapping documents
I don't see why we should
not make our code easier to write.
--Hardy
On Jul 10, 2012, at 10:35 AM, Strong Liu wrote:
current is defined as :
then the generated org.hibernate.internal.jaxb.mapping.hbm.JaxbQueryElement has
a _getContent()_ method for both String/Text and query-param attribute
* Objects of the following type(s) are allowed i
