It sounds good to me, but I can't give much help regarding the actual
coding. It will be some extra work to bring current projects into line with
an updated Turbine, but I am all for improving this.
I wrote the "ugly" getTable_Column methods to allow Turbine to potentially
fit into a prior schema. I was not overly happy with the results, but it
got the job done. If introspection can be used to improve it, great.
>
>
> currently, there are ugly hardcoded methods in the current
> DatabaseMapBuilder...so, in the RolePeer, we currently have something like
> this:
>
> private static final String ROLD_ID = mapBuilder.getRole_RoleId();
>
> So, my proposal would be to make those methods available via
> reflection/introspection instead being hard coded...kinda like the way
that
> Ant works...
>
> so, each table/column in a database would get a method like the one below
in
> the MapBuilder itself:
>
> getTABLE_COLUMN()
>
> now, the part that i'm not sure about is actually how to implement that
> portion of things...in a hard coded situation, it is easy, but i don't
have
> a lot of experience doing introspection...
>
Me neither.
>
> suggestions?
>
Sorry, nothing right now.
John McNally
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
