That's the default, xdoclet assumes an abstract bean which has
subclasses is probably just an abstract base class and not a deployable
ejb. Set generate="true".
Ara.
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:xdoclet-user-
> [EMAIL PROTECTED]] On Behalf Of Paul Cantrell
> Sen
I have three entity beans, two of which extend the first:
public abstract class NodeEntityEJB implements EntityBean
public abstract class QuestionEntityEJB extends NodeEntityEJB
public abstract class GuessEntityEJB extends NodeEntityEJB
Oddly, although I specify @ejb:bean tags for all three clas
Hi,
I have a model, done on Rational Rose and want to create the EJB from
this model.
I was thinking on the idea of export it as a XMI file, then process it
creating .java files with ejb XDoclet tags on it.
Do you think this is a viable idea ?
Or there are a tool to do this ready
Title: data-object, getData() not generated when setdata="false"
I
don't know if it fixed already.
I have stateless session bean with
defined tags as following:
* @ejb:bean name="MyStatelessSessionEJB"
type="Stateless" view-type="both"
* jndi-name="MyStatelessSession"
local-jndi-n
I am currently using xdoclet to generate home and remote interfaces for
a large set of Ejbs. In doing so, I am noticing some strange behavior
when a set of beans inherits from a base class with xdoclet tags.
Specifically when the parent class defines the ejbCreate() method, the
subclasses' home s
Em Seg, 2002-04-29 às 04:51, Enrique Rodriguez escreveu:
> Four months working with xdoclets+Jboss+struts,and always the same error,
> "Malformed UTF-8 char
> -- is an XML encoding declaration missing?" (line number may be too low)."
You need to ask xdoclet to generate UTF-8 charset declaration
Guys, I have to admit I was wrong...
It's not that case I cited as an example. In my example the whole table is
dedicated to handle relationships but in the forum's example the table
contains other data too and is considered as a bean. It seems, it's not
possible for now with JBoss.
Sorry,
> But i wonder why most the time autonumber fields are used as pk. Could
> someone explane (it should be OT but i am interested in)
>
Why not ?
OK that is simple answer
Why would you want to have a complex PK ?
OK also not very fair
The main reason I see is the possibility you have after to chan
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
Hi,
oops, my reply was going directly to Marius.
MK> Alex Loubyansky wrote:
>> What do you mean "complex PKs don't work very well with jboss3.x now"?
>>
MK> http://main.jboss.org/forums/thread.jsp?forum=46&thread=9931
MK> So i stopped using it. I don't know if it is just the table-creating
M
Don't have such a problem if I understand it correctly. I use
jboss-3.1.0alpha and complex primary keys.
I've just modified some of my beans to test: CategoryEJB - ResourceEJB
relationship. CategoryPK consists of 'categoryId' and 'name' (just for
example) and ResourcePK - resourceId. Works fi
Oh my god
Four months working with xdoclets+Jboss+struts,and always the same error,
"Malformed UTF-8 char
-- is an XML encoding declaration missing?" (line number may be too low)."
I always thought that was a extrange config error with my classpath but...
The strange think for me is that i
12 matches
Mail list logo
