-->
These old forums are deprecated now and set to read-only. We are waiting for you on our new forums!
More modern, Discourse-based and with GitHub/Google/Twitter authentication built-in.

All times are UTC - 5 hours [ DST ]



Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 6 posts ] 
Author Message
 Post subject: Controlling reverse engineering limitations
PostPosted: Wed Apr 15, 2009 9:45 pm 
Newbie

Joined: Wed Apr 15, 2009 9:15 pm
Posts: 3
I have downloaded the trunk from svn.

I am going to change the collection type from Set to List

I have reach the file JDBCBinder.java, the method bindOneToMany

I have found a comment
Quote:
'// MASTER TODO: allow overriding collection type'


Are You guys going to work on it soon?

Any address I would need for working on it?

Regards


Top
 Profile  
 
 Post subject: Re: Controlling reverse engineering limitations
PostPosted: Tue May 05, 2009 7:22 am 
Hibernate Team
Hibernate Team

Joined: Tue Aug 26, 2003 6:10 am
Posts: 8615
Location: Neuchatel, Switzerland (Danish)
List requires an index which requires some extra info in reveng.xml/reverse engineering strategy.

It has not been implemented, if you want to work on it then sure go ahead. No special address needed.

_________________
Max
Don't forget to rate


Top
 Profile  
 
 Post subject: Re: Controlling reverse engineering limitations
PostPosted: Mon Jun 15, 2009 4:07 pm 
Newbie

Joined: Wed Apr 15, 2009 9:15 pm
Posts: 3
Thanks Max.

It was necessary just to change mapping.Set(rc) by mapping.List(rc)

The advantage of having a List is that is ordered when I add elements to the list from the view.

Regards

_________________
andres


Top
 Profile  
 
 Post subject: Re: Controlling reverse engineering limitations
PostPosted: Mon Jun 29, 2009 9:54 am 
Hibernate Team
Hibernate Team

Joined: Tue Aug 26, 2003 6:10 am
Posts: 8615
Location: Neuchatel, Switzerland (Danish)
that change wouldn't be enough would it ? Which column do you use for the index storage ?

...or are you just asking for mapping as a <bag> ?

_________________
Max
Don't forget to rate


Top
 Profile  
 
 Post subject: Re: Controlling reverse engineering limitations
PostPosted: Fri Jul 10, 2009 4:11 pm 
Newbie

Joined: Wed Apr 15, 2009 9:15 pm
Posts: 3
Hi Max, I am using the attribute just as a bag.

I work on the List in the view (jsf). (adding and removing items in the list).

Actually, I think the solution is not elegant, it would be better if i could add an attribute (tag) in seam-gen.reveng.xml (hibernate.reveng.xml).
For Applying this change, without recompiling and creating the jar again. It would be more useful for more people

Regards

_________________
andres


Top
 Profile  
 
 Post subject: Re: Controlling reverse engineering limitations
PostPosted: Mon Jul 27, 2009 9:05 am 
Hibernate Team
Hibernate Team

Joined: Tue Aug 26, 2003 6:10 am
Posts: 8615
Location: Neuchatel, Switzerland (Danish)
andres.ramirez.pe wrote:
Hi Max, I am using the attribute just as a bag.

I work on the List in the view (jsf). (adding and removing items in the list).

Actually, I think the solution is not elegant, it would be better if i could add an attribute (tag) in seam-gen.reveng.xml (hibernate.reveng.xml).
For Applying this change, without recompiling and creating the jar again. It would be more useful for more people


I agree - so feel free to submit a patch in jira that allow it to be controlled in reveng.xml/reverse engineering strategy and we can get it into the main core.

_________________
Max
Don't forget to rate


Top
 Profile  
 
Display posts from previous:  Sort by  
Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 6 posts ] 

All times are UTC - 5 hours [ DST ]


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
© Copyright 2014, Red Hat Inc. All rights reserved. JBoss and Hibernate are registered trademarks and servicemarks of Red Hat, Inc.