Thank you, Kevin.
Yes, I read those.
For SchemaTool:
Most users will only access the schema tool indirectly, through the
interfaces provided by other tools. You may find, however, that the
schema tool is a powerful utility in its own right. The schema tool has
two functions:
1. To reflec
Thank you, Kevin.
On Thu, 2009-03-26 at 09:01 -0500, Kevin Sutter wrote:
> Hi David,
> I think we'll need a bit more information.
Ok, no problem.
I kept fiddling, but still no luck. I noticed that when stepping through
the code, even with the @Table annotation, for some reason value for
"given
I've done some more digging around, and it appears that the cause of
the bug is actually a joined table entry:
@Table(name = "CUSTOMER")
public class Customer implements Serializable {
@EmbeddedId
protected CustomerPK customerPK;
@JoinColumns({...@joincolumn(name = "DEFAULT_DISCOUNT
Cool! That's very nice and it makes sense that starting a new JVM
changes the class loader issue. Notice the ant lib directory includes
xercesImpl.jar (ant 1.7.1). That also explains why the OpenJPA examples
work because the examples build.xml has fork=yes.
Thanks for figuring that out. Mi
Paul -
I don't fully understand whats going on, but I found what is causing the
problems. When you launch your java application, you don't fork the JVM. Adding
fork="yes" to Paul-
> If you still are unable to figure out what's going on, feel free to zip
> up your simple test app and I'll take
As I recall that's a rather large change. I'd feel a bit uncomfortable
putting it into a maintenance release (1.2.2). 1.3.x is fair game though (if
it isn't there already).
Seeing as Richard is already having problems with 2.0.0-SNAPSHOT we might
not be out of the woods yet. I'm still a little con
Hi David,
OpenJPA has the same type of tooling that Kodo used to have. OpenJPA
provides the SchemaTool [1]. We also provide a MappingTool [2]. Would
either of these help you out?
Kevin
[1]
http://openjpa.apache.org/builds/1.2.0/apache-openjpa-1.2.0/docs/manual/manual.html#ref_guide_schema_sche
Hi David,
I think we'll need a bit more information. What do your Entities look
like? What's in your persistence.xml file? From the exception text, it
looks like you have an Entity with the name of "TYPE". Is that accurate?
That may be reserved word, have you tried something like "TYPE1" just f
