Patrick Linskey wrote: > > FYI, once I commit a fix to OPENJPA-229, you'll be able to use the same > class names once again. Sorry about that bug. > Understood. Right now I'm in the connection debate: toplink cannot use less than 2, so each of my fat clients will have 3 open (1 it already has). So the decision is still open. It appears that using a business model this way is not something that is done often. -- View this message in context: http://www.nabble.com/Open-JPA-error-Could-not-locate-metadata-for-the-class-using-alias-tf3561516.html#a10204857 Sent from the open-jpa-dev mailing list archive at Nabble.com.
- Re: Open JPA error-Could not locate metadata for the class... Marina Vatkina
- Re: Open JPA error-Could not locate metadata for the class... tbee
- RE: Open JPA error-Could not locate metadata for the class... Patrick Linskey
- RE: Open JPA error-Could not locate metadata for the class... tbee
- RE: Open JPA error-Could not locate metadata for the class... Patrick Linskey
- RE: Open JPA error-Could not locate metadata for the class... Patrick Linskey
- RE: Open JPA error-Could not locate metadata for the class... tbee
- RE: Open JPA error-Could not locate metadata for the class... Patrick Linskey
- RE: Open JPA error-Could not locate metadata for the class... tbee
- RE: Open JPA error-Could not locate metadata for the class... Patrick Linskey
- RE: Open JPA error-Could not locate metadata for the class... tbee
- RE: Open JPA error-Could not locate metadata for the class... Patrick Linskey
- Re: Open JPA error-Could not locate metadata for the class... Marina Vatkina
- RE: Open JPA error-Could not locate metadata for the class... Patrick Linskey
- Re: Open JPA error-Could not locate metadata for the class... Marina Vatkina
- Re: Open JPA error-Could not locate metadata for the class... tbee
- RE: Open JPA error-Could not locate metadata for the class... Patrick Linskey
- RE: Open JPA error-Could not locate metadata for the class... tbee