to point out that a third table is only needed for a N-M
(many-to-many) relationship.
In the case of a 1-N relationship, simply have a foreign key to the
master table.
--
Sean P. McNamara[EMAIL PROTECTED]
SOMA Technologies, Inc. [EMAIL PROTECTED
.)
Together is 100% java based, and runs like a pro on Linux. It's much
more than simply an IDE. If you haven't checked it out, I recommend
it highly.
--
Sean P. McNamara[EMAIL PROTECTED]
SOMA Technologies, Inc. [EMAIL PROTECTED]
[EMAIL
to Segfault after about 5 minutes of
continuous HTTP requests. To be fair, I don't think this would happen under
Windows... which isn't to say I want to use Windows... but lets be fair.
--
Sean P. McNamara[EMAIL PROTECTED]
SOMA Technologies, Inc. [EMAIL PROTECTED
(JAX)
And the useBean segment from my JSP is:
---
jsp:useBean
id="employee"
scope="page"
type="com.soma.axon.ejb.entity.Employee"
/
--
Sean P. McNamara[EMAIL PROTECTED]
SOMA Technologies,
; and
one-to-many mapping and such things as it pertains to EJB2.0.
I'm not familiar with these concepts, and so am unable to follow the ongoing
discussions. Can someone point me someplace where I can find some good
(possibly concise) information about it?
Thanks.
for?
I apologize for the basic-nature of this question, but I haven't done
much work with EntityBeans, and even the O'reilly EJB book doesn't
seem to provide much detail on the subject.
Thanks!
Sean P. McNamara writes:
Hi again-
Baby-steps, baby-steps I've finally gotten my application
as there are some fundamental
basics missing. trial and error will not get you very far in J2EE. look at
the specs (they are actually rather readable) and maybe check out ed romans
ejb book (free download at www.theserverside.com).
--
Sean P. McNamara[EMAIL PROTECTED]
SOMA
sense to me... Any
pointers?
Thanks!
--
Sean P. McNamara[EMAIL PROTECTED]
SOMA Technologies, Inc. [EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
