--- "Harkness, David" <[EMAIL PROTECTED]>
的訊息：> One line looks suspect to me, though I don't
know if
> it's the source of your trouble.
>
> > @ejb:table-name User
>
> The correct tag is
>
> @ejb:persistence table-name="User"
>
> At least that's what I'm using.
>
> David Harkness
> Sr.
i encounter a problem when running client to access
an ejb deployed on jboss3.0.4-tomcat4.1.12. i test the
cmr one to one relationship via xdoclet.1.2-b3.
it issues window application error dialogue: "The
instruction at '0x6d3a1bea' referenced memory at
'0x000c'. The memory could not be 'read'
I am using XDoclet
to generate a local BMP Entity bean to be deployed on Weblogic 6.1. XDoclet
works well until I include the tag @weblogic.resource-description in my Bean
source. For some reason this tag causes XDoclet to generate unwanted
remote interfaces and a primary key class (which I
--- matt <[EMAIL PROTECTED]> wrote:
> Sorry, I didn't mean to sound like a whinger. I
> love XDoclet and
> appreciate all of the effort that has gone into
> making it such a great
> product, and I certainly don't consider my skills to
> be sufficiently
> well-developed for committer status - I
Hello everyone,
XDoclet allows to map EJB relationships (e.g. CMR) to the generated value objects. For
example, XDoclet generates a getter in one value object that retrieves the value
object of the related EJB in a 1-to-1 relationship.
Unfortunately, the code that initializes the first value ob
Hi
I used the JDO module in the 1.2 version to generate JDO metadata, the .JDO file. The code worked fine with around 600 Java classes but threw error with around 2000 classes. Now I have to slice the classes in three directories and proceed them separately. But I prefer to proceed all the class
