Hi guys,
I'm halfway into removing all the *Id.java classes from the persistence
layer on the UDDI v3 branch, and it is making it all a lot cleaner. The
reason they are there is b/c the way the PKs are setup in the UDDI v2
schema. They are composite PK, however we can simplify the PKs to be of
type Long.
Does anyone see any issues with this? Where we planning on using the
parents business keys for fast searching or something? Are we afraid of
running out of 'integers' in the ID columns?
Speak up or hold your peace forever ;).
--Kurt
