Binding on Java 7/8 at runtime should work just fine.
I've sent PR https://github.com/hibernate/hibernate-orm/pull/930 to update
XJC and configure the "target" parameter. I've built that branch with JDK 8
successfully, all tests pass.
I've also checked where the required() attribute actually is u
So if we get target to work on these XJC tasks and generate JAXB models
without required... does that hinder runtime binding at all in Java 7/8?
On Thu, Apr 2, 2015 at 9:50 AM, Steve Ebersole wrote:
> I just want the one that "works" :)
>
> On Thu, Apr 2, 2015 at 9:37 AM, Gunnar Morling
> wrote
I just want the one that "works" :)
On Thu, Apr 2, 2015 at 9:37 AM, Gunnar Morling wrote:
> It also works with that task from JAXB Commons when updating the JAXB
> Commons libs (and JAXB itself). That task has the "target" parameter in
> newer versions. I can send you a PR for that update.
>
> 2
It is just the one used in almost every example I have ever seen. I really
have no idea why one is used versus another.
On Thu, Apr 2, 2015 at 9:08 AM, Gunnar Morling wrote:
> Had a quick look into (1).
>
> The "target" parameter is not supported by that version of the Ant task
> currently in u
It also works with that task from JAXB Commons when updating the JAXB
Commons libs (and JAXB itself). That task has the "target" parameter in
newer versions. I can send you a PR for that update.
2015-04-02 16:08 GMT+02:00 Gunnar Morling :
> Had a quick look into (1).
>
> The "target" parameter is
Had a quick look into (1).
The "target" parameter is not supported by that version of the Ant task
currently in use. If I change the class name of the Ant task from
"org.jvnet.jaxb2_commons.xjc.XJC2Task" into "com.sun.tools.xjc.XJC2Task",
the "target" parameter is recognized and setting it to "2.0
After considering this some more, I think moving to Java 8 as baseline is
just not reasonable yet. And tbh I just do not see a compelling reason to
move to Java 7 as the baseline. So if reasonably possible I would still
like to remain backwards compatible with Java 6.
The only hurdle I believe i
Sanne, I went back and tried applying this -target flag but have not had
any luck with it. I applied it through the XJC2Task Ant task:
ant.xjc(
destdir: "${jaxbTargetDir}",
binding: hbmXjb.path,
schema: hbmXsd.path,
extension
Baseline on Java 8? Hmm... Well thanks for tempting me :)
What do you mean by "be able to experiment with significant API
improvements"?
On Tue, Mar 31, 2015 at 7:18 PM, Sanne Grinovero
wrote:
> I wouldn't disagree on requiring Java 7.
> I probably wouldn't disagree with Java 8 either, after a
Sorry, wrong class... XmlElementRef, not XmlElement:
/home/sebersole/projects/hibernate/hibernate-orm/hibernate-core/target/generated-src/jaxb/main/org/hibernate/boot/jaxb/hbm/spi/JaxbHbmFilterType.java:57:
error: cannot find symbol
@XmlElementRef(name = "aliases", namespace = "
http://www.hi
Hi,
Can you share the exact exception/error you get when using the generated
model with Java 6? The required() attribute already exists as of Java 6 [1].
You should be able to make the generated code Java 6 compatible by either
setting the right options for XJC (the JAXB code generator) or in the
I wouldn't disagree on requiring Java 7.
I probably wouldn't disagree with Java 8 either, after all we're not
removing older versions of Hibernate from any download location and
we'll still support and maintain some older versions. It would
actually be nice to have the latest ORM version to be able
12 matches
Mail list logo
