Yes, using my own hacked up velocity script because my target interface
was way different than the beans being generated by middlegen
out-of-the-box. The target structure was dictated by an existing
application that was based on a weblogic-specific bean generator we made
in-house. There are several hundred session beans that depend on our
custom value-objects, finders and create methods. I used middlegen to
duplicate those beans and the results was fabulous and not tied to
weblogic: jboss, weblogic, websphere... I will send you a delta when I
get a chance outlining my merge points and what I needed to change.
Anyway, I will trace through the generator to find out why those tables
are ReadOnly (they do have public setters) now that you have pointed me
in the right direction.
Thanks!
-----Original Message-----
From: Aslak Hellesoy [mailto:***@netcom.no]
Sent: Tuesday, January 28, 2003 9:04 AM
To: middlegen-***@lists.sourceforge.net
Subject: RE: [Middlegen-user] Incorrect weblogic attribute value on
concurrency-strategy
-----Original Message-----
Macpherson
Sent: 28. januar 2003 17:32
Subject: [Middlegen-user] Incorrect weblogic attribute value on
concurrency-strategy
Preamble
I am specifying "false" for the readonly attribute of the cmp20 task
and 90% plus of my generated EJBs have the correct
concurrency-strategy: Database
* concurrency-strategy="Database"
Middlegen never generates tags like that
(concurrency-strategy="Database") . Look at the template:
http://tinyurl.com/5031
You're running against your own hacked template, right?
http://sourceforge.net/mailarchive/message.php?msg_id=3571935
Problem
There are a handful of tables that are defined as ReadOnly which
introduces a bug in our application - I will spare you the details of
the bug. What rule is middlegen using to decide a particular table
should be designated as read-only? This substitution happens in
#if( $table.readOnly ) corresponds to Entity20Table.isReadOnly()
http://tinyurl.com/5038
A table is considered read-only if there are no enabled setters in the
remote or local interfaces. This is something you can adjust in the gui,
but also at the ant level. (The gui settings will override the ant
setting, and it will also be persisted in the prefsdir).
entity-cmp-20.vm but I do not know why specific tables have the
read-only state to begin with.
* concurrency-strategy="ReadOnly"
Solution
?
If you don't want a certain EJB to be read only, just make sure it has
an enabled setter somewhere (use the gui). Have you tried the merge file
approach i suggested?
Aslak
(aside from a simple substitution in our post-generate ant task)
-------------------------------------------------------
SourceForge Enterprise Edition + IBM + LinuxWorld =omething 2 See!
http://www.vasoftware.com
_______________________________________________
https://lists.sourceforge.net/lists/listinfo/middlegen-user
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
middlegen-user mailing list middlegen-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/middlegen-user