----- Original Message ----- From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, September 30, 2002 2:44 AM Subject: JBoss-user digest, Vol 1 #3116 - 7 msgs
> Send JBoss-user mailing list submissions to > [EMAIL PROTECTED] > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.sourceforge.net/lists/listinfo/jboss-user > or, via email, send a message with subject or body 'help' to > [EMAIL PROTECTED] > > You can reach the person managing the list at > [EMAIL PROTECTED] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of JBoss-user digest..." > > > Today's Topics: > > 1. RE: JBOSS - Components library (Pete Beck) > 2. RE: ExternalContext and HA-JNDI weirdness (Sacha Labourey) > 3. Re: Gosling has Web Services right... (Pete Beck) > 4. RE: Gosling has Web Services right... (Sacha Labourey) > 5. Re: Can Finder Methods Use Cache? (Pete Beck) > 6. Re: TR: [JBoss-user] many-many CMR relationships for JBoss with XDoclet > 1.1.2 (=?ISO-8859-1?Q?R=E9mi_NODET?=) > > --__--__-- > > Message: 1 > Subject: RE: [JBoss-user] JBOSS - Components library > From: Pete Beck <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Date: 30 Sep 2002 10:00:23 +0100 > Reply-To: [EMAIL PROTECTED] > > This sounds like a good idea except for one immediate problem: > integration. > > Any components would have to be developed as a suite (including the data > model) as it is not usually possible to integrate Order A with Product B > if they are not compatible. Of course you could use the facade design > pattern, but this would get messy quickly and would negate the advantage > of having a ready made component. > > I suspect that such a component library would require an overall design > to be maintained. It is unlikely that the addition of components in an > ad-hoc manner would work effectively.=20 > > On Fri, 2002-09-27 at 10:39, wonder sonic wrote: > > Hi Saroj, > >=20 > > 1 & 2)=20 > > In fact the kind of components can be sorted by > > domain: > > - network: > > - SSL Connection management component > > - Chat component > > - Forum component > > - Multicast component (JXTA...) > > - accounting: > > - Order component > > - invoice component > > - login/security: > > - User component > > - Administrator component (extends User...) > > - Director component (extends User, link with > > Address component (CMP...)) > > - bio data-processing: > > - BLAST algorithm processing component > > - MMC algorithm processinc component > >=20 > > As you see, the domains can be infinite and the > > associated components too :) > >=20 > > Imagine the gained time all around the world... > >=20 > > To be continued... (I hope) > >=20 > > --- Saroj Kumar <[EMAIL PROTECTED]> a =E9crit : > > > Hi Wonder Sonic, > > >=20 > > > Yeah, this seems to be a good idea. > > >=20 > > > Certainly it can be done. > > >=20 > > > Let us discuss it in depth. > > >=20 > > > Q- > > > 1) What kind of components are u thinking about? > > > 2) Which domain they work in? > > >=20 > > > -Saroj > > >=20 > > > -----Original Message----- > > > From: [EMAIL PROTECTED] > > > [mailto:[EMAIL PROTECTED]] On > > > Behalf Of wonder > > > sonic > > > Sent: Friday, September 27, 2002 1:51 PM > > > To: [EMAIL PROTECTED] > > > Subject: [JBoss-user] JBOSS - Components library > > >=20 > > >=20 > > > Hi, > > > I was wondering: > > > -1- JBoss seems to be free > > > -2- JBoss seems to be the most downloaded > > > Application > > > Server > > > -3- JBoss seems to be the most used by developpers > > > -4- A part of these developpers seems to be involved > > > in > > > the development of the open source community > > > -5- These developers develop things, particularly > > > EJBs... > > >=20 > > > So, according to the number of developers. How many > > > of > > > them have RE-developed an EJB? > > >=20 > > > My question is: How about add to JBoss a Components > > > library (ie: a set of EJBs) that could be reused by > > > others? Imagine the time spent to RE-develop the > > > same > > > things each time... > > >=20 > > > Waiting for replies... :) > > >=20 > > > Best regards to the JBoss and the Open Source > > > community, > > > Wonder Sonic > > >=20 > > > > > ___________________________________________________________ > > > Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et > > > en fran=E7ais ! > > > Yahoo! Mail : http://fr.mail.yahoo.com > > >=20 > > >=20 > > > > > ------------------------------------------------------- > > > This sf.net email is sponsored by:ThinkGeek > > > Welcome to geek heaven. > > > http://thinkgeek.com/sf > > > _______________________________________________ > > > JBoss-user mailing list > > > [EMAIL PROTECTED] > > > > > https://lists.sourceforge.net/lists/listinfo/jboss-user > > >=20 > > >=20 > > >=20 > > > > > ------------------------------------------------------- > > > This sf.net email is sponsored by:ThinkGeek > > > Welcome to geek heaven. > > > http://thinkgeek.com/sf > > > _______________________________________________ > > > JBoss-user mailing list > > > [EMAIL PROTECTED] > > > > > https://lists.sourceforge.net/lists/listinfo/jboss-user=20 > >=20 > > ___________________________________________________________ > > Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en fran=E7ais ! > > Yahoo! Mail : http://fr.mail.yahoo.com > >=20 > >=20 > > ------------------------------------------------------- > > This sf.net email is sponsored by:ThinkGeek > > Welcome to geek heaven. > > http://thinkgeek.com/sf > > _______________________________________________ > > JBoss-user mailing list > > [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/jboss-user > >=20 > --=20 > Peter Beck BEng (hons) - Managing Director, Electrostrata Ltd. > http://www.electrostrata.com --+-+-+-+-- Experts in e-business and > e-commerce > > > > --__--__-- > > Message: 2 > From: "Sacha Labourey" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Subject: RE: [JBoss-user] ExternalContext and HA-JNDI weirdness > Date: Mon, 30 Sep 2002 10:59:26 +0200 > Reply-To: [EMAIL PROTECTED] > > Hello, > > That would be great if you could directly give me the complete stacktrace. > Thank you. > > Cheers, > > > Sacha > > > > -----Message d'origine----- > > De : [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED]]De la part de Brian > > Towles > > Envoy� : samedi, 28 septembre 2002 20:49 > > � : [EMAIL PROTECTED] > > Objet : RE: [JBoss-user] ExternalContext and HA-JNDI weirdness > > > > > > Sorry too little sleep I'm not communicating effectively.. > > > > Heres a quick sketch out > > > > Using JBoss 3.0.2 > > > > > > -Situation A - Works > > > > JBoss Instance A JBoss Instance B > > ExternalConext points to ---> Standard JNDI Port > > > > -Situation B - Does not Work (NameNotFoundException) > > > > Cluster A Cluster B > > JBoss Instance A JBoss Instance B > > DefaultPartition A DefaultPartition B > > ExternalContext points to --> HA-JNDI Port > > > > (Different Multicast IPs for DefaultPartions A and B as well as for > > Different Multicast IPs and Names for Other Partitions for EJBs.) > > > > -Situation C - Does Work > > Cluster A Cluster B > > JBoss Instance A JBoss Instance B > > Default Partition <---------> Default Partition > > ExternalContext points to -----| > > HA-JNDI Port (localhost:1100 <-| > > > > (Same Multicast IP for DefaultPatition on both A and B Different > > Multicast IPs and Partition names for EJBs in each cluster) > > > > *Note JNDIView shows an empty tree under the entry for the > > ExternalContext in both Situation B and C > > > > A failure in this case means that a NameNotFoundException (NNF) is being > > returned from the HA-JNDI in the case of Situation B. I have not > > verified but I believe that it is the Local HA-JNDI returning NNF in > > case B. Since the ExternalContext uses a simple InitialContext inside > > of it why would that be going through the local HA-JNDI? > > > > If its not local to Instance A then why would Instance B fail to look up > > in one case (B) but not the other (C). > > > > Im going to stick with Situation C anyways ass it lets me drop machines > > in Cluster B without any configuration to cluster A like situation B > > would make me do. Depending on the network traffic generated of course. > > > > > > Hope that explains it a bit better... im operating on 3 hours of sleep > > in the past 48. crunch time. > > > > Nice work on the clustering btw Sacha, Bill and crew works like a > > fscking champ. Our arch even has a farm of Resin instances in front of > > Cluster A load balancing and and failing over. > > > > Thanks > > -=Brian > > > > On Sat, 2002-09-28 at 12:06, Sacha Labourey wrote: > > > What do you mean by "It doesn't work"? and "It fails"? > > > > > > > -----Message d'origine----- > > > > De : [EMAIL PROTECTED] > > > > [mailto:[EMAIL PROTECTED]]De la part de Brian > > > > Towles > > > > Envoy� : samedi, 28 septembre 2002 18:44 > > > > � : [EMAIL PROTECTED] > > > > Objet : [JBoss-user] ExternalContext and HA-JNDI weirdness > > > > > > > > > > > > Howdy all > > > > > > > > I having an issue using ExternalContext to point to a a > > HAJNDI instance > > > > on a separate cluster of jboss machines. > > > > > > > > I have JBoss to JBoss communication working fine with tyrex on an > > > > instance to instance basis. And I have ExternalContext working fine > > > > when I point it to the normal JNDI port. > > > > > > > > But when I point it to a HA-JNDI port on the other instance it fails. > > > > > > > > To get around this I can place all of the instances in the > > same Default > > > > Partition and point the external context to the localhost HA-JNDI port > > > > and it works. > > > > > > > > > > > > Im just confused as to why pointing to the HA-JNDI port of a separate > > > > cluster doesnt work.... any hints? > > > > > > > > > > > > Thanks > > > > -=Brian > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > > This sf.net email is sponsored by:ThinkGeek > > > > Welcome to geek heaven. > > > > http://thinkgeek.com/sf > > > > _______________________________________________ > > > > JBoss-user mailing list > > > > [EMAIL PROTECTED] > > > > https://lists.sourceforge.net/lists/listinfo/jboss-user > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > This sf.net email is sponsored by:ThinkGeek > > > Welcome to geek heaven. > > > http://thinkgeek.com/sf > > > _______________________________________________ > > > JBoss-user mailing list > > > [EMAIL PROTECTED] > > > https://lists.sourceforge.net/lists/listinfo/jboss-user > > > > > > > > > > ------------------------------------------------------- > > This sf.net email is sponsored by:ThinkGeek > > Welcome to geek heaven. > > http://thinkgeek.com/sf > > _______________________________________________ > > JBoss-user mailing list > > [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/jboss-user > > > > > > --__--__-- > > Message: 3 > Subject: Re: [JBoss-user] Gosling has Web Services right... > From: Pete Beck <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Date: 30 Sep 2002 10:25:28 +0100 > Reply-To: [EMAIL PROTECTED] > > On Fri, 2002-09-27 at 19:15, Bill Burke wrote: > > What I've been saying all along... > > > > "People have been building Web services under different names for 20 or 30 > > years," he explains. "We've been building distributed systems for years out > > using CORBA and RMI and all of that." > > Except of course for the fact that the "Web" hasn't existed for 20 or 30 years. > It is true that distributed computing has been around for a long time, > but Web services are definitely a new approach to the problem. The > marketing machine behind it should make it far more widespread than > previous efforts and that is IMHO a good thing. > > > > -- > Peter Beck BEng (hons) - Managing Director, Electrostrata Ltd. > http://www.electrostrata.com --+-+-+-+-- Experts in e-business and > e-commerce > > > > --__--__-- > > Message: 4 > From: "Sacha Labourey" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Subject: RE: [JBoss-user] Gosling has Web Services right... > Date: Mon, 30 Sep 2002 11:37:30 +0200 > Reply-To: [EMAIL PROTECTED] > > Hello, > > > It is true that distributed computing has been around for a long time, > > but Web services are definitely a new approach to the problem. > > For example? > > > marketing machine behind it should make it far more widespread than > > previous efforts and that is IMHO a good thing. > > Yes, that's most probably a good thing. At the same time, it is a risk: the > risk this technology be considered as "old" before it is actual/real because > of too much marketing noise. > > Cheers, > > > Sacha > > > > --__--__-- > > Message: 5 > Subject: Re: [JBoss-user] Can Finder Methods Use Cache? > From: Pete Beck <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Date: 30 Sep 2002 10:41:33 +0100 > Reply-To: [EMAIL PROTECTED] > > I wrote a post on this some time back, but alas didn't get any > responses. > > I think having an in-memory implementation of EJB-QL could provide a > huge optimisation to JBoss and would also make it possible to use > non-JDBC datastores. > > As Peter notes, it wouldn't make sense for all entities, but of the 100+ > entity beans in my application, I think maybe 98% of them would benefit > from such an approach. > > > On Sat, 2002-09-28 at 01:49, Dain Sundstrom wrote: > > Luttrell, Peter wrote: > > > My app runs on a slow database. To compensate i have a > > > longer-then-normal bean-cache lifetime and use commit option A - thus > > > once they are loaded, they are always in cache. > > > > > > This works great except for finder methods, because they hit the > > > database to select ids based on query parameters. > > > > > > Is there any way for the cmp engine to use the cache for finder methods? > > > I'm thinking that you'd need all records loaded to make it work - is > > > there anyway to tell jboss to do this? Of course this optimization would > > > only be make sense for small tables, which in certain cases is what I have. > > > > Sure, if you want to write an in memory query engine, and some code that > > can guarantee the claim that all of the data is in cache. All kidding > > aside, it wouldn't be that hard. > > -- > Peter Beck BEng (hons) - Managing Director, Electrostrata Ltd. > http://www.electrostrata.com --+-+-+-+-- Experts in e-business and > e-commerce > > > > --__--__-- > > Message: 6 > Date: Mon, 30 Sep 2002 11:48:35 +0200 > From: =?ISO-8859-1?Q?R=E9mi_NODET?= <[EMAIL PROTECTED]> > Organization: Odile Jacob =?ISO-8859-1?Q?Multim=E9dia?= > To: [EMAIL PROTECTED] > Subject: Re: TR: [JBoss-user] many-many CMR relationships for JBoss with XDoclet > 1.1.2 > Reply-To: [EMAIL PROTECTED] > > This is a multi-part message in MIME format. > --------------010206030609030408040406 > Content-Type: multipart/alternative; > boundary="------------060207050202020703030408" > > > --------------060207050202020703030408 > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > Content-Transfer-Encoding: 8bit > > Hi, > > I've had some difficulties to make it work as well.... > > Here are the xdoclet comments I used ( for a many-many relationship > between users and roles ). > To get this work, I had to modify the file jbosscmp-jdbc.j in > xdoclet.jar ( I suspect a bug there, because the field names where > interverted only for many-many relationships ...). The modified > jbosscmp-jdbc.j is attached to this email > > Bean Role : > > /** > *@jboss.relation-table > * table-name="user_role_relation" > * > *@jboss.relation > * fk-constraint="true" > * fk-column="role_id" > * related-pk-field="RoleId" > */ > public abstract java.util.Collection getUsers(); > > Bean User : > > > /** > * @jboss.relation-table > * table-name="user_role_relation" > * > * @jboss.relation > * fk-constraint="true" > * fk-column="user_id" > * related-pk-field="userId" > * > */ > public abstract java.util.Collection getBabelRoles(); > > >Hi, > > > >Can anyone explain to me how many-many relationships are defined for > >JBoss using XDoclet 1.1.2 ? > > > >I can see how this is done for Weblogic (using @weblogic:relation), but > >the @jboss:relation tag doesn't appear to allow the mapping table name > >to be specified - so I don't see how a many-many relationship can be > >defined for JBoss. > > > >Any pointers would be much appreciated. > > > >Gavin. > > > > > >------------------------------------------------------- > >This sf.net email is sponsored by:ThinkGeek > >Welcome to geek heaven. > >http://thinkgeek.com/sf > >_______________________________________________ > >JBoss-user mailing list > >[EMAIL PROTECTED] > >https://lists.sourceforge.net/lists/listinfo/jboss-user > > > > > > > > > > > > -- > R�mi NODET > > ----------------------------------- > Odile Jacob Multim�dia > 15 rue Soufflot > 75005 Paris > > tel : 01 44 41 64 93 > fax : 01 44 41 46 90 > > > > --------------060207050202020703030408 > Content-Type: text/html; charset=us-ascii > Content-Transfer-Encoding: 7bit > > <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> > <html> > <head> > <meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1"> > <title></title> > </head> > <body> > Hi,<br> > <br> > I've had some difficulties to make it work as well.... <br> > <br> > Here are the xdoclet comments I used ( for a many-many relationship between > users and roles ).<br> > To get this work, I had to modify the file jbosscmp-jdbc.j in xdoclet.jar > ( I suspect a bug there, because the field names where interverted only for > many-many relationships ...). The modified jbosscmp-jdbc.j is attached to > this email<br> > <br> > <u>Bean Role :</u><br> > <br> > /**<br> > *@jboss.relation-table<br> > * table-name="user_role_relation"<br> > * <br> > *@jboss.relation<br> > * fk-constraint="true"<br> > * fk-column="role_id"<br> > * related-pk-field="RoleId"<br> > */<br> > public abstract java.util.Collection getUsers();<br> > <br> > <u>Bean User : <br> > <br> > <br> > </u> /**<br> > * @jboss.relation-table<br> > * table-name="user_role_relation"<br> > *<br> > * @jboss.relation<br> > * fk-constraint="true"<br> > * fk-column="user_id"<br> > * related-pk-field="userId"<br> > *<br> > */<br> > public abstract java.util.Collection getBabelRoles();<br> > <br> > <blockquote type="cite" > cite="[EMAIL PROTECTED]"> > <pre wrap="">Hi, > > Can anyone explain to me how many-many relationships are defined for > JBoss using XDoclet 1.1.2 ? > > I can see how this is done for Weblogic (using @weblogic:relation), but > the @jboss:relation tag doesn't appear to allow the mapping table name > to be specified - so I don't see how a many-many relationship can be > defined for JBoss. > > Any pointers would be much appreciated. > > Gavin. > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > <a class="moz-txt-link-freetext" href="http://thinkgeek.com/sf";>http://thinkgeek.com/sf</a> > _______________________________________________ > JBoss-user mailing list > <a class="moz-txt-link-abbreviated" href="mailto:[EMAIL PROTECTED]";>[EMAIL PROTECTED] net</a> > <a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/jboss-user";>https://lists .sourceforge.net/lists/listinfo/jboss-user</a> > > > > </pre> > </blockquote> > <br> > <pre class="moz-signature" cols="$mailwrapcol">-- > Rémi NODET > > ----------------------------------- > Odile Jacob Multimédia > 15 rue Soufflot > 75005 Paris > > tel : 01 44 41 64 93 > fax : 01 44 41 46 90</pre> > <br> > </body> > </html> > > --------------060207050202020703030408-- > > --------------010206030609030408040406 > Content-Type: text/plain; > name="jbosscmp-jdbc_xml.j" > Content-Transfer-Encoding: 7bit > Content-Disposition: inline; > filename="jbosscmp-jdbc_xml.j" > > <?xml version="1.0" encoding="<XDtConfig:configParameterValue paramName='Xmlencoding'/>"?> > <!DOCTYPE jbosscmp-jdbc PUBLIC "<XDtXml:publicId/>" "<XDtXml:systemId/>"> > > <jbosscmp-jdbc> > <defaults> > <datasource><XDtConfig:configParameterValue paramName="Datasource"/></datasource> > <datasource-mapping><XDtConfig:configParameterValue paramName="Typemapping"/></datasource-mapping> > </defaults> > > <enterprise-beans> > > <XDtEjbCmp:forAllCmpEntityBeans> > <XDtEjb:ifIsAConcreteEJBean> > <entity> > <XDtMerge:merge file="jbosscmp-jdbc-db-settings-{0}.xml"> > <ejb-name><XDtEjb:ejbName/></ejb-name> > <XDtClass:ifHasClassTag tagName="jboss:create-table"> > <create-table><XDtClass:classTagValue tagName="jboss:create-table" paramName="create" paramNum="0"/></create-table> > </XDtClass:ifHasClassTag> > <XDtClass:ifHasClassTag tagName="jboss:remove-table"> > <remove-table><XDtClass:classTagValue tagName="jboss:remove-table" paramName="remove" paramNum="0"/></remove-table> > </XDtClass:ifHasClassTag> > <XDtClass:ifHasClassTag tagName="jboss:read-only"> > <read-only><XDtClass:classTagValue tagName="jboss:read-only" paramName="read-only" paramNum="0"/></read-only> > </XDtClass:ifHasClassTag> > <XDtClass:ifHasClassTag tagName="jboss:time-out"> > <time-out><XDtClass:classTagValue tagName="jboss:time-out" paramName="time-out" paramNum="0"/></time-out> > </XDtClass:ifHasClassTag> > <XDtClass:ifHasClassTag tagName="jboss:row-locking"> > <row-locking><XDtClass:classTagValue tagName="jboss:row-locking" paramName="row-locking" paramNum="0"/></row-locking> > </XDtClass:ifHasClassTag> > <XDtClass:ifHasClassTag tagName="jboss:pk-constraint"> > <pk-constraint><XDtClass:classTagValue tagName="jboss:pk-constraint" paramName="pk-constraint" paramNum="0"/></pk-constraint> > </XDtClass:ifHasClassTag> > <XDtClass:ifHasClassTag tagName="jboss:table-name"> > <table-name><XDtClass:classTagValue tagName="jboss:table-name" paramName="table-name" paramNum="0"/></table-name> > </XDtClass:ifHasClassTag> > </XDtMerge:merge> > > <XDtMerge:merge file="jbosscmp-jdbc-{0}.xml"> > > <XDtMethod:forAllMethods> > <XDtMethod:ifDoesntHaveMethodTag tagName="jboss:not-persisted-field"> > <XDtMethod:forAllMethodTags tagName="ejb:persistent-field"> > <cmp-field> > <field-name><XDtMethod:propertyName/></field-name> > <XDtMethod:ifDoesntHaveMethodTag tagName="jboss:property"> > <XDtMethod:ifHasMethodTag tagName="jboss:column-name"> > <column-name><XDtMethod:methodTagValue tagName="jboss:column-name" paramName="name" paramNum="0"/></column-name> > </XDtMethod:ifHasMethodTag> > <XDtMethod:ifDoesntHaveMethodTag tagName="jboss:column-name"> > <column-name><XDtMethod:propertyName/></column-name> > </XDtMethod:ifDoesntHaveMethodTag> > <XDtMethod:ifHasMethodTag tagName="jboss:jdbc-type"> > <jdbc-type><XDtMethod:methodTagValue tagName="jboss:jdbc-type" paramName="type" paramNum="0"/></jdbc-type> > </XDtMethod:ifHasMethodTag> > <XDtMethod:ifHasMethodTag tagName="jboss:sql-type"> > <sql-type><XDtMethod:methodTagValue tagName="jboss:sql-type" paramName="type" paramNum="0"/></sql-type> > </XDtMethod:ifHasMethodTag> > </XDtMethod:ifDoesntHaveMethodTag> > > <XDtMethod:ifHasMethodTag tagName="jboss:property"> > <XDtMethod:forAllMethodTags tagName="jboss:property"> > <property> > <property-name><XDtMethod:methodTagValue tagName="jboss:property" paramName="name"/></property-name> > <XDtMethod:ifHasMethodTag tagName="jboss:property" paramName="column-name"> > <column-name><XDtMethod:methodTagValue tagName="jboss:property" paramName="column-name"/></column-name> > </XDtMethod:ifHasMethodTag> > <XDtMethod:ifDoesntHaveMethodTag tagName="jboss:property" paramName="column-name"> > <column-name><XDtMethod:methodTagValue tagName="jboss:property" paramName="name"/></column-name> > </XDtMethod:ifDoesntHaveMethodTag> > <XDtMethod:ifMethodTagValueEquals tagName="jboss:property" paramName="not-null" value="yes"> > <not-null/> > </XDtMethod:ifMethodTagValueEquals> > <XDtMethod:ifHasMethodTag tagName="jboss:property" paramName="jdbc-type"> > <jdbc-type><XDtMethod:methodTagValue tagName="jboss:property" paramName="jdbc-type"></jdbc-type> > </XDtMethod:ifHasMethodTag> > <XDtMethod:ifHasMethodTag tagName="jboss:property" paramName="sql-type"> > <sql-type><XDtMethod:methodTagValue tagName="jboss:property" paramName="sql-type"></sql-type> > </XDtMethod:ifHasMethodTag> > </property> > </XDtMethod:forAllMethodTags> > </XDtMethod:ifHasMethodTag> > </cmp-field> > </XDtMethod:forAllMethodTags> > </XDtMethod:ifDoesntHaveMethodTag> > </XDtMethod:forAllMethods> > <XDtClass:forAllClassTags tagName="jboss:cmp-field"> > <cmp-field> > <field-name><XDtClass:classTagValue tagName="jboss:cmp-field" paramName="field-name"/></field-name> > <column-name><XDtClass:classTagValue tagName="jboss:cmp-field" paramName="column-name"/></column-name> > </cmp-field> > </XDtClass:forAllClassTags> > > <XDtMerge:merge file="jbosscmp-jdbc-load-{0}.xml"> > <!-- > To define load groups for this entity, write a file named > jbosscmp-jdbc-load-<XDtClass:className/>.xml and put it in > your mergedir. Write it according to the following DTD slice: > > <!ELEMENT load-groups (load-group+)> > <!ELEMENT load-group (load-group-name, description?, field-name+)> > <!ELEMENT load-group-name (#PCDATA)> > <!ELEMENT description (#PCDATA)> > <!ELEMENT field-name (#PCDATA)> > <!ELEMENT eager-load-group (#PCDATA)> > <!ELEMENT lazy-load-groups (load-group-name+)> > --> > </XDtMerge:merge> > > <XDtClass:forAllClassTags tagName="jboss:declared-sql"> > <XDtClass:ifHasClassTag tagName="jboss:declared-sql" paramName="signature"> > <query> > <XDtClass:ifHasClassTag tagName="jboss:declared-sql" paramName="description"> > <description><XDtClass:classTagValue tagName="jboss:declared-sql" param-name="description"/></description> > </XDtClass:ifHasClassTag> > <XDtClass:ifDoesntHaveClassTag tagName="jboss:declared-sql" paramName="description"> > <description/> > </XDtClass:ifDoesntHaveClassTag> > <query-method> > <method-name><XDtClass:classTagValue tagName="jboss:declared-sql" paramName="signature" delimiter=" (" tokenNumber="1"/></method-name> > <method-params> > <XDtParameter:forAllParameterTypes paramName="signature"> > <method-param><XDtParameter:currentToken/></method-param> > </XDtParameter:forAllParameterTypes> > </method-params> > </query-method> > > <XDtClass:ifHasClassTag tagName="jboss:declared-sql" paramName ="result-type-mapping"> > <result-type-mapping><XDtClass:classTagValue tagName ="jboss:declared-sql" paramName="result-type-mapping" values ="Local,Remote"/></result-type-mapping> > </XDtClass:ifHasClassTag> > <declared-sql> > <XDtClass:ifHasClassTag tagName="jboss:declared-sql" paramName="where"> > <where><![CDATA[<XDtClass:classTagValue tagName="jboss:declared-sql" paramName="where"/>]]></where> > </XDtClass:ifHasClassTag> > <XDtClass:ifHasClassTag tagName="jboss:declared-sql" paramName="order"> > <order><![CDATA[<XDtClass:classTagValue tagName="jboss:declared-sql" paramName="order"/>]]></order> > </XDtClass:ifHasClassTag> > <XDtClass:ifHasClassTag tagName="jboss:declared-sql" paramName="other"> > <other><![CDATA[<XDtClass:classTagValue tagName="jboss:declared-sql" paramName="other"/>]]></other> > </XDtClass:ifHasClassTag> > </declared-sql> > </query> > </XDtClass:ifHasClassTag> > </XDtClass:forAllClassTags> > </XDtMerge:merge> > </entity> > > </XDtEjb:ifIsAConcreteEJBean> > </XDtEjbCmp:forAllCmpEntityBeans> > > </enterprise-beans> > > <XDtEjbRel:ifHasRelationships> > <relationships> > <XDtEjbRel:forAllRelationships> > <ejb-relation> > <ejb-relation-name><XDtMethod:methodTagValue tagName="ejb:relation" paramName="name"/></ejb-relation-name> > <XDtEjbRel:ifIsMany2Many> > <relation-table-mapping> > <XDtMethod:ifHasMethodTag tagName="jboss:relation-table" paramName="table-name"> > <table-name><XDtMethod:methodTagValue tagName="jboss:relation-table" paramName="table-name"/></table-name> > </XDtMethod:ifHasMethodTag> > <XDtMethod:ifHasMethodTag tagName="jboss:relation-table" paramName="datasource"> > <datasource><XDtMethod:methodTagValue tagName="jboss:relation-table" paramName="datasource"/></datasource> > </XDtMethod:ifHasMethodTag> > <XDtMethod:ifHasMethodTag tagName="jboss:relation-table" paramName="create-table"> > <create-table><XDtMethod:methodTagValue tagName="jboss:relation-table" paramName="create-table"/></create-table> > </XDtMethod:ifHasMethodTag> > <XDtMethod:ifHasMethodTag tagName="jboss:relation-table" paramName="remove-table"> > <remove-table><XDtMethod:methodTagValue tagName="jboss:relation-table" paramName="remove-table"/></remove-table> > </XDtMethod:ifHasMethodTag> > <XDtMethod:ifHasMethodTag tagName="jboss:relation-table" paramName="row-locking"> > <row-locking><XDtMethod:methodTagValue tagName="jboss:relation-table" paramName="row-locking"/></row-locking> > </XDtMethod:ifHasMethodTag> > <XDtMethod:ifHasMethodTag tagName="jboss:relation-table" paramName="pk-constraint"> > <pk-constraint><XDtMethod:methodTagValue tagName="jboss:relation-table" paramName="pk-constraint"/></pk-constraint> > </XDtMethod:ifHasMethodTag> > </relation-table-mapping> > </XDtEjbRel:ifIsMany2Many> > <XDtEjbRel:ifNotIsMany2Many> > <foreign-key-mapping/> > </XDtEjbRel:ifNotIsMany2Many> > <ejb-relationship-role> > <ejb-relationship-role-name><XDtEjbRel:leftRoleName/></ejb-relationship-role -name> > <XDtJBEjbRel:ifLeftHasFKConstraint> > <fk-constraint><XDtJBEjbRel:leftFKConstraint/></fk-constraint> > </XDtJBEjbRel:ifLeftHasFKConstraint> > <XDtMethod:ifDoesntHaveMethodTag tagName="jboss:auto-key-fields"> > <XDtEjbRel:ifNotIsMany2Many> > <XDtJBEjbRel:ifRightHasFK> > <key-fields> > <XDtJBEjbRel:forAllRightForeignKeys> > <key-field> > <field-name><XDtJBEjbRel:relatedPKField/></field-name> > <column-name><XDtJBEjbRel:fkColumn/></column-name> > </key-field> > </XDtJBEjbRel:forAllRightForeignKeys> > </key-fields> > </XDtJBEjbRel:ifRightHasFK> > <XDtJBEjbRel:ifNotRightHasFK> > <key-fields/> > </XDtJBEjbRel:ifNotRightHasFK> > </XDtEjbRel:ifNotIsMany2Many> > <XDtEjbRel:ifIsMany2Many> > <XDtJBEjbRel:ifLeftHasFK> > <key-fields> > <XDtJBEjbRel:forAllLeftForeignKeys> > <key-field> > <field-name><XDtJBEjbRel:relatedPKField/></field-name> > <column-name><XDtJBEjbRel:fkColumn/></column-name> > </key-field> > </XDtJBEjbRel:forAllLeftForeignKeys> > </key-fields> > </XDtJBEjbRel:ifLeftHasFK> > </XDtEjbRel:ifIsMany2Many> > </XDtMethod:ifDoesntHaveMethodTag> > </ejb-relationship-role> > <ejb-relationship-role> > <ejb-relationship-role-name><XDtEjbRel:rightRoleName/></ejb-relationship-rol e-name> > <XDtJBEjbRel:ifRightHasFKConstraint> > <fk-constraint><XDtJBEjbRel:rightFKConstraint/></fk-constraint> > </XDtJBEjbRel:ifRightHasFKConstraint> > <XDtMethod:ifDoesntHaveMethodTag tagName="jboss:auto-key-fields"> > <XDtEjbRel:ifIsMany2Many> > <XDtJBEjbRel:ifRightHasFK> > <key-fields> > <XDtJBEjbRel:forAllRightForeignKeys> > <key-field> > <field-name><XDtJBEjbRel:relatedPKField/></field-name> > <column-name><XDtJBEjbRel:fkColumn/></column-name> > </key-field> > </XDtJBEjbRel:forAllRightForeignKeys> > </key-fields> > </XDtJBEjbRel:ifRightHasFK> > </XDtEjbRel:ifIsMany2Many> > <XDtEjbRel:ifNotIsMany2Many> > <XDtJBEjbRel:ifLeftHasFK> > <key-fields> > <XDtJBEjbRel:forAllLeftForeignKeys> > <key-field> > <field-name><XDtJBEjbRel:relatedPKField/></field-name> > <column-name><XDtJBEjbRel:fkColumn/></column-name> > </key-field> > </XDtJBEjbRel:forAllLeftForeignKeys> > </key-fields> > </XDtJBEjbRel:ifLeftHasFK> > <XDtJBEjbRel:ifNotLeftHasFK> > <key-fields/> > </XDtJBEjbRel:ifNotLeftHasFK> > </XDtEjbRel:ifNotIsMany2Many> > </XDtMethod:ifDoesntHaveMethodTag> > </ejb-relationship-role> > </ejb-relation> > </XDtEjbRel:forAllRelationships> > </relationships> > </XDtEjbRel:ifHasRelationships> > > <dependent-value-classes> > <XDtClass:forAllClasses> > <XDtClass:ifHasClassTag tagName="jboss:dvc"> > <dependent-value-class> > <description><XDtClass:firstSentenceDescription/></description> > <class><XDtClass:fullClassName/></class> > <XDtMethod:forAllMethods> > <XDtMethod:ifHasMethodTag tagName="jboss:property"> > <property> > <property-name><XDtMethod:propertyName/></property-name> > <XDtMethod:ifHasMethodTag tagName="jboss:column-name"> > <column-name><XDtMethod:methodTagValue tagName="jboss:column-name" paramName="name" paramNum="0"/></column-name> > </XDtMethod:ifHasMethodTag> > <XDtMethod:ifDoesntHaveMethodTag tagName="jboss:column-name"> > <column-name><XDtMethod:propertyName/></column-name> > </XDtMethod:ifDoesntHaveMethodTag> > <XDtMethod:ifHasMethodTag tagName="jboss:jdbc-type"> > <jdbc-type><XDtMethod:methodTagValue tagName="jboss:jdbc-type" paramName="type" paramNum="0"/></jdbc-type> > </XDtMethod:ifHasMethodTag> > <XDtMethod:ifHasMethodTag tagName="jboss:sql-type"> > <sql-type><XDtMethod:methodTagValue tagName="jboss:sql-type" paramName="type" paramNum="0"/></sql-type> > </XDtMethod:ifHasMethodTag> > </property> > </XDtMethod:ifHasMethodTag> > </XDtMethod:forAllMethods> > </dependent-value-class> > </XDtClass:ifHasClassTag> > </XDtClass:forAllClasses> > </dependent-value-classes> > > <XDtMerge:merge file="jbosscmp-typemappings.xml"> > </XDtMerge:merge> > </jbosscmp-jdbc> > > --------------010206030609030408040406-- > > > > > --__--__-- > > _______________________________________________ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user > > > End of JBoss-user Digest ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
