Chris Lewold

+ Follow
since Dec 16, 2003
Cows and Likes
Total received
In last 30 days
Total given
Total received
Received in last 30 days
Total given
Given in last 30 days
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Chris Lewold


I have a Dirset identifying all my source folders.
I use this Dirset as argument for my javac task.

This looks like

<dirset id="dirs.src" dir="${basedir}>
<include name="**/src"/>
<include name="**/test">

<path id="path.src">
<dirset refid="dirs.src"/>

<javac destdir="build">
<src refid="path.src">
<include name="**/*.java/>

Ok - now I want to copy all files contained in the dirset to a given location. (Or simply jar it in order to build a source file package).

How do I do that? Please be aware that I want to use the "dirs.src" id as reference for the copy (or jar) operation.
The concrete background is, that dirs.src is defined in a project specific build file, while the javac, jar, copy tasks are kept in a generic file. Consequently hardcoding the folders in the generic file is a no-no.

[ November 24, 2008: Message edited by: Chris Lewold ]
13 years ago
I started to work on the EJB certification at the begin of the year. If I am not totally mistaken the Head First EJB book is geared towards EJB 2.0, and so is the certification.

Well - job stress came over me, so I had to interrupt my studies. Now I would have the time to resume, but of course I want to do that on the most current stuff.

-) The book recommends to use the 1.3 reference server. Now that the JSEE 1.4 update 1 is already available I would prefer to use the most current stuff, but of course I assume there will be differences to 1.3. What's your recommendation here ?
-) Is there an update for the book available for EJB 2.1? Is there actually a big difference between 2.0 and 2.1? - Forgive the silly question, but I had to do something completely different, and lost "contact" to the EJB area a bit.

Thanks all for the help,
The PK doesnt have to be a String
Chris Lewold
I was hoping for more practical samples like the AdviceApp at the start.
Now I came to the point where I want to implement some EntityBeans on my own (including CMP/CMR).
I assume the RI can be used for that purpose, but ...... I also assume I need a database for this.
Did any of you folks implement some samples? Which database did you use?
Any bad experiences with given RI/DB combos ?
Thanks for any tip,
Just to ensure I get this right ....
If you want to use CMR, then you have to go with local coponent interfaces on entity beans - right ?
Now I know that handing Entity beans to clients might be a performance issue, and that you better hide stuff using the Facade pattern.
BUT .... This makes the design still very inflexible, and you have to build a facade for basically each situation where Entity beans are involved.
OR ... if you dont want that you have to build both a remote and local component interface, which also is kind of overhead.
Is one of you folks able to tell me
a) why this restriction exists ?
b) If this restriction still exists in J2EE 1.4 ?
This is likely the first thing with EJBs I really have a problem with - that's why I at least want to understand the reasoning behind.
Thanks - I got it the moment you postet.
There is a difference between J2EE Spec (1.3) and EJB Spec (2.0) .... confusion solved ;-)

Thanks again
[ January 28, 2004: Message edited by: Chris Lewold ]
I am totally confused.
I downloaded the spec from in PDF format.
The document is called j2ee-1_3-fr-spec.pdf and has 160 pages.
Now I often see references in the HFE book to something like: spec: 192-193
I assume 192-193 means page number, but I have just 160 pages ;-)
Ouch .... do I have the wrong spec ? does 192-193 not mean page number but something else?
Hehe ... the book often says "there are no dumb questions" ... but I am afraid this might be the first ;-) ..... what am I missing here ???
Chris Lewold
[ January 28, 2004: Message edited by: Chris Lewold ]
[ January 28, 2004: Message edited by: Chris Lewold ]
Imho the timeline is wrong (arrow on top of page)....
ejbStore is called prior to ejbPassivate
If I am mistaken here then page 352 would be wrong btw ...
But imho the correct answer then would still be NO.
Chris Lewold
Stateless session beans can NEVER be shared. Only one of them can service a given client at the same time.
I am missing two methods:
Whos wrong - me or the book ?
Chris Lewold
Bumping this because I read HFE Book Page 282 now.
It clearly says "Client will get an exception if he tries to use the EJB object reference after removing the bean". (Stateless session beans).
Using the RI this is NOT the case, as shown above.
Chris Lewold
Please provide a short code listing.
Chris Lewold
-) Stateless session beans are held in a pool.
-) It is up to the container when to create them. (E.g. initialize the pool at startup with 10 beans, or create them "on need" or whatever).
-) When a client invokes a business method on the ComponentInterface the bean is taken out of the pool, and associated with the clients EJBObject.
-) After using the business method the bean is de-associated from the EJBObject and put back into the pool.
Consequently there is no way one client can use the same bean as another client.
This is my view of things - hope it helps (and please correct me if I am mistaken)
Chris Lewold
Correct - all u say is right.
My whole thread was about the sidenote which really confuses me.