[thomasschenker]

Hi!

I have a problem with Hibernate UserTypes in MyEclipse2015 CI16 when generating POJOs for a Hibernate-Mapping-File (.hbm.xml)

I do the same as described in this topic: closed-hibernate-usertype

I’m using Hibernate UserTypes like the described TrimmedStringType for several years now
and until MyEclipse2014, MyEclipse generated the POJOs with the Type “String” for properties with the Type “TrimmedStringType”.

But now with MyEclipse2015 CI16, the Hibernate UserTypes are not treated the same way anymore.
MyEclipse2015 doesn’t generate the POJOs with the Type that is given by UserType.returnedClass(), but it takes the Hibernate UserType instead.

Example:

Behaviour MyEclipse2014:
.hbm.xml: <property name=”street” type=”my.own.usertype.TrimmedStringType”>
Generated POJO: private String street;

Behaviour MyEclipse2015:
.hbm.xml: <property name=”street” type=”my.own.usertype.TrimmedStringType”>
Generated POJO: private TrimmedStringType street;

In this example, MyEclipse2015 doesn’t take the Type java.lang.String given by TrimmedStringType.returnedClass() anymore.

Could you please fix this?
As you see in the mentioned topic from 2007, it worked since MyEclipse Verion 5.5GA.

Best regards, Thomas

[thomasschenker]

Hi!

I have an update on this topic:

I have some projects that have this problem with the POJO generation and, as I now noticed,
some other projects where the generation works as expected.

The only difference between these projects is the java-version they use!
With JDK 7 it works, but with JDK 8 it doesn’t.
I’m using JDK 8 Update 51 64bit with MyEclipse2015 CI 16 64bit.

Regards, Thomas

[support-swapna]

Thomas,

Thank you for pointing to this issue.I could replicate the issue at my end and I have filed a bug report with the dev team for further investigation. While I cannot provide you with a timeline for the fix right now, I will keep you posted when I have the details.

Sorry for inconvenience caused.

–Swapna
MyEclipse Support

[thomasschenker]

Hi!

I really appreciate that you publish updates for MyEclipse regularly!

But I’m a bit disappointed that this issue is still not resolved in the latest CI version 19.
This problem prevents us from switching to Java 8.

Regards, Thomas

[support-swapna]

Thomas,

I have escalated it to a dev team member. They will get back to you soon about the fix schedule.
Thank you for your patience.

–Swapna
MyEclipse Support

• This reply was modified 8 years, 3 months ago by support-swapna.

[Brian Fernandes]

Thomas,

I’m sorry we missed getting a fix for this into CI 19, and I can understand your disappointment. I will say that my team did start looking into it, but it fell off the schedule due to various reasons.

I’ll give it my personal attention for the next release. Apologies once again for the delay.

[Author]

Posts