Object creation: default and non-default ctors

[aloubyansky]

I have added support for non-default ctors and documented it on the wiki. Any feedback/ideas are welcome here.

Jira issue: http://jira.jboss.org/jira/browse/JBXB-28
Wiki page: http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossXB_DefAndNonDefCtors

[aloubyansky]

Also, I would appreciate thoughts on the default value for 'useNoArgCtorIfFound'. Currently, it's false.

[starksm64]

This would seem to intersect with the recent discussion of how property editors might fit into jbossxb. It raises the bigger question of what controls string to object conversion. In the case of N attributes matching an N argument ctor, what controls the type matching?

In the case of an attribute of type string, is there any conversion capability/defaults in jaxb?

[aloubyansky]

First, all children are collected including values of both simple and complex types. Default binding of XSD built-in simple types are taken from the JAXB2.0 spec and can also be found here http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossXB_DefaultBinding

[aloubyansky]

You can override defaults using your own CharactersHandler.

[starksm64]

Do CharactersHandler apply to both TEXT and attribute values? If so, then it seems like we need a jbxb: set of extension types that cover things like java.net.URL, java.net.InetAddress, etc for which we already have property editor converters.

The problem then becomes how these types get injected into the current document SchemaBinding. This could be done via a jbxb: annotation on the associated document schema, as well as via an external jbxb binding instruction descriptor. Have we got into providing support for the latter yet?

[aloubyansky]

Do CharactersHandler apply to both TEXT and attribute values?

Yes.

jbxb:javaValue annotation could be used in the XSD on an attribute or characters content to customize the binding.

"External jbxb binding instruction descriptor" is not supported. But is required by the JAXB spec, AFAIK.