On entity bean primary keys...
no matter if you're talking about entity beans or relational databases in
general it is always a good idea to use primary keys without business
meaning. You might run into a problem later if your PK embodies a business
concept and this concept changes later in the l
It's a good idea, so you can version them like your other files
-Ursprüngliche Nachricht-
Von: Emerson Cargnin - MSA [mailto:[EMAIL PROTECTED]]
Gesendet: Donnerstag, 25. April 2002 15:34
An: 'Xdoclet-User (E-mail)'
Betreff: [Xdoclet-user] keep jar files in cvs
Is it a bad idea to ke
Sorry, but I didn't know that :) You usually only need name entries and
mappings in web.xml for servlets.
-Ursprungliche Nachricht-
Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Gesendet: Donnerstag, 25. April 2002 15:11
An: [EMAIL PROTECTED]
Betreff: [Xdoclet-user] How to integrate J
I had the same problem early in February and posted a similar message to the
list, on Feb. 12 Ara answered that it was fixed, although I'm not quite sure
that it is.
-Ursprüngliche Nachricht-
Von: Vincent Harcq [mailto:[EMAIL PROTECTED]]
Gesendet: Donnerstag, 25. April 2002 13:13
An: [EMA
Just try it out and see whjat you get in jbosscmp-jdbc.xml. It should
generate the default jboss-relation-tags, i.e. implement the relations as
Jboss would by default if you chose not to include jbosscmp-jdbc.xml in your
distribution EJB jar. That is, default for one-to-one and one-to-many
relatio
USe @jboss.auto-key-fields and it should work fine
-Ursprungliche Nachricht-
Von: Ingo Bruell [mailto:[EMAIL PROTECTED]]
Gesendet: Mittwoch, 24. April 2002 12:12
An: [EMAIL PROTECTED]
Betreff: [Xdoclet-user] ejb:relation and jboss dd
Hi,
i am playin arround with the feature above and h
I find them convenient to use for lookups instead of hardcoded names.
-Ursprungliche Nachricht-
Von: Ingo Bruell [mailto:[EMAIL PROTECTED]]
Gesendet: Dienstag, 23. April 2002 10:07
An: [EMAIL PROTECTED]
Betreff: [Xdoclet-user] Constants in LocalHome
Hi,
is there a need for the constan
Put @ejb.home generate="local"
Replace local by "remote" or "both" if you desire something different.
-Ursprüngliche Nachricht-
Von: jfina [mailto:[EMAIL PROTECTED]]
Gesendet: Dienstag, 23. April 2002 10:54
An: Xdoclet-User
Betreff: [Xdoclet-user] EJBHome not generated
Hi!
I still cant
Guys,
any thoughts on release date of next (official) binary build of XDoclet
(1.1.3. or 1.2. whatever it'll be called).
Just curious, otherwise I'll try using CVS version for now, since I'm
especially interested in the xjavadoc and new dataobject/valueobject task.
Thanks,
Bernie
Hi all :)
Is support for JBossQL planned in XDoclet? So far it appears I can only use
specific declared (declarative) SQL queries to be generated into
jbosscmp-jdbc.xml by using the @jboss:finder-query element.
In JBoss 3 however you can now declare queries in JBossQL which is a
superset of EJB
Hi,
I have a stateful session bean whose ejbCreate has an argument. I have the
following three lines as class level tags (among others).
* @ejb:bean type="Stateful" name="HVAttributeManager"
* jndi-name="ejb/HVAttributeManager" view-type="remote"
* transaction-type="Contai
Hi all :)
Is support for JBossQL planned in XDoclet? So far it appears I can only use
specific declared (declarative) SQL queries to be generated into
jbosscmp-jdbc.xml by using the @jboss:finder-query element.
In JBoss 3 however you can now declare queries in JBossQL which is a
superset of EJB
I don't know about this error, on the other hand though it doesn't make much
sense to me to have so many parameters for ejbCreate. For performance and
convenience you should only set a few ( the most necessary) parameters in
ejbCreate and set the others later via the individual set methods (if usi
For me
it run's perfectly well with J2SE 1.4. Are you also using the most current
version of Ant? (I run it directly from the prompt or from NetBeans 3.x IDE).
I'm still using the @namespace:tag notation which works allright, except for
more javadoc error messages being printed on the consol
Hi,
after turning on logging for the merge handlers I noticed XDoclet searching
for JBoss merge files of the patterns jbosscmp-jdbc-db-settings-{0}.xml,
jbosscmp-jdbc-{0}.xml and jbosscmp-jdbc-load-{0}.xml.
As especially the first and second one are not explained in the docs I was
wondering about
Hi again,
doesn't really anybody have anything to say about that? If it's not my fault
I would say it constitutes a fairly serious problem if you can't use your
merge entries any more so please read on and tell me what's wrong.
Thanks,
Bernhard
Hi all,
with XDoclet 1.1.1. I successfully utili
Hi all,
with XDoclet 1.1.1. I successfully utilized the "mergedir" attribute of the
deploymentdescriptor task to merge stuff like environment entries etc. into
the generated ejb-jar.xml. After switching to the new 1.2.2. XDoclet
everything worked fine, except the env entries that appeared in my
e
Hi,
the field mapping for CMR fields doesn't seem to work quite right. I have a
unidirectional one-to-many relationship between two entity beans. On the one
side I have the @jboss:target-relation tag in front of the appropriate
public Collection getBlabla() method and I always get and
the tags b
Hi,
I have a session bean named PartnerFacade in package com.test.partner.
So the bean is com.test.partner.PartnerFacade and on my C drive its in the
c:\com\test\partner directory.
I want to include an environment entry which is in a mergefile named
ejb-env-entries-PartnerFacade.xml.
Is this th
Hi,
I'm
also interested in knowing more about this. From what I understand is you can
put an ejb:aggregate task in the javadocs for a method: eg. for public abstract
Collection getAddresses() in a person entity bean and then I would get a method
in my person value object as follows: public
Hi,
I have a problem with the method signature for my select method not
appearing in the generated CMP class (I'm using EJB 2.0 local CMP entity
beans). Therefore I can't compile my application.
I have declared a select method like this in my local Partner entity bean:
* @ejb:select si
Sorry for the confusion :)
What I meant to say was I'm looking up a remote session bean (facade) via
JNDI from the Web tier which itself (the remote session bean) makes local
lookups on local session and entity beans (via ejb-local-ref and ejb-link
tags in ejb-jar.xml) which is achieved by insert
That's what I'm doing now. And it does work like a charm :) Stupid me, I
didn't think of this before (I was the one who originally posted this
question). This really makes you independent of JNDI, is much more
performant and increases your flexibility. For local beans it doesn't really
matter what
Hi all,
and thanks Ara for fixing the overloaded method thing. When is the new
Xdoclet release coming?
Something else...
I want my beans to have JNDI names in the style of ejb/beanname.
Problem is, for bean with local interface only (eg. local CMP entity beans)
the jndi-name attribute of the @e
Hi,
I have a session bean containing multiple overloaded methods, e.g. void
addToPerson(String id, AddressDTO address), void addToPerson(String id,
CreditCardDTO creditCard) etc.
They are all correctly tagged (@ejb:interface-method) as I want all of them
to be accessible in the remote interface
Hi,
I have a session bean containing multiple overloaded methods, e.g. void
addToPerson(String id, AddressDTO address), void addToPerson(String id,
CreditCardDTO creditCard) etc.
They are all correctly tagged (@ejb:interface-method) as I want all of them
to be accessible in the remote interface
I simply would like to include field validation code in my generated data
objects and the question is how do I achieve it? Can I create a merge file
per entity bean/data object and if so, how would I go about doing that?
Thanks !
Bernie
-Ursprungliche Nachricht-
Von: Konstantin Pribloud
> Hi there,
>
> I use XDoclet 1.1.1. to generate EJB 2.0 CMP entity beans. I was wondering
> where you folks suggest to put field validation logic (preferably the
> generated data objects?) and ideas on how I would go about to have my
> validation code included in the generated code. Can I use a
Hi there,
I use XDoclet 1.1.1. to generate EJB 2.0 CMP entity beans. I was wondering
where you folks suggest to put field validation logic (preferably the
generated data objects?) and ideas on how I would go about to have my
validation code included in the generated code. Can I use a merge file t
Hi,
I do exactly as you say and what I get is the following output after running
ant.
c:\Programme\idea\bla>ant
Buildfile: build.xml
init:
prepare:
ejbdoclet:
[ejbdoclet] Generating Javadoc
[ejbdoclet] Javadoc execution
[ejbdoclet] Loading source file
C:\Programme\idea\bla\src\test\ejb\Partne
> Hi,
>
>
> I'm testing out Xdoclet at the moment and it works really great, however I
> have trouble with the following: I want to pass a Xdoclet-generated data
> object for my entity bean as the parameter for its ejbCreate method.
> However, when I include it using the fully qualified name (i
Hi,
I'm testing out Xdoclet at the moment and it works really great, however I
have trouble with the following: I want to pass a Xdoclet-generated data
object for my entity bean as the parameter for its ejbCreate method.
However, when I include it using the fully qualified name (it's the right
na
32 matches
Mail list logo