Thread: [smartweb-devel] Smartweb Auth and problem with XDoclet/ Hibernate union subclass
Brought to you by:
rlogiacco
Menu
▾
▴
smartweb-devel
|
From: svetrini <st...@gm...> - 2007-11-06 20:58:36
|
At this time smartweb auth has a little problem... Actually union subclass has. hbm generation fails due to a bug on xdoclet union subclass. We have just sended patches to xdoclet team but none new version was released. I recently found another minor problem on auth module. It doesn't create schema on dbs different from PostgreSQL ( I tried on MySQL and HSQL ) this is not our bug but a knowed hibernate problem. So... What do you think about change from union subclass to another subclass type? I'm waiting to your answers... :-) -- View this message in context: http://www.nabble.com/Smartweb-Auth-and--problem-with-XDoclet--Hibernate-union-subclass-tf4761003s17546.html#a13615761 Sent from the SmartWeb Developers mailing list archive at Nabble.com. |
|
From: Pino C. <gco...@gm...> - 2007-11-06 22:07:44
|
I think the choice of a subclass different from the union is excellent. The important thing in this context where you are to release a stable version of auth. Consider a person like me who has always used the old auth and was well to integrate it within their applications to use a version that does not support MySQL. I'll be gonig to use the old version. svetrini wrote: > > At this time smartweb auth has a little problem... Actually union > subclass has. > hbm generation fails due to a bug on xdoclet union subclass. > We have just sended patches to xdoclet team but none new version was > released. > I recently found another minor problem on auth module. It doesn't create > schema on dbs different from PostgreSQL ( I tried on MySQL and HSQL ) this > is not our bug but a knowed hibernate problem. > > So... > > What do you think about change from union subclass to another subclass > type? > > I'm waiting to your answers... :-) > -- View this message in context: http://www.nabble.com/Smartweb-Auth-and--problem-with-XDoclet--Hibernate-union-subclass-tf4761003s17546.html#a13617096 Sent from the SmartWeb Developers mailing list archive at Nabble.com. |
|
From: Roberto Lo G. <rlo...@sm...> - 2007-11-07 01:26:24
|
+1 to switch back to joined-subclass inheritance mapping if this solves our portability problems. 2007/11/6, svetrini <st...@gm...>: > > At this time smartweb auth has a little problem... Actually union subclass > has. > hbm generation fails due to a bug on xdoclet union subclass. > We have just sended patches to xdoclet team but none new version was > released. > I recently found another minor problem on auth module. It doesn't create > schema on dbs different from PostgreSQL ( I tried on MySQL and HSQL ) this > is not our bug but a knowed hibernate problem. > > So... > > What do you think about change from union subclass to another subclass type? > > I'm waiting to your answers... :-) > -- > View this message in context: http://www.nabble.com/Smartweb-Auth-and--problem-with-XDoclet--Hibernate-union-subclass-tf4761003s17546.html#a13615761 > Sent from the SmartWeb Developers mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > smartweb-devel mailing list > sma...@li... > https://lists.sourceforge.net/lists/listinfo/smartweb-devel > |
|
From: Gaetano P. <gpe...@sm...> - 2007-11-07 10:21:57
|
In my opinion the union-subclass actual solution is very fine because it makes the generated database more simple and more "developer-friendly". Then I think it deserves at least an attempt to preserve it. Could we think to identify accurately the hibernate property and try to resolve it?? svetrini wrote: > > At this time smartweb auth has a little problem... Actually union > subclass has. > hbm generation fails due to a bug on xdoclet union subclass. > We have just sended patches to xdoclet team but none new version was > released. > I recently found another minor problem on auth module. It doesn't create > schema on dbs different from PostgreSQL ( I tried on MySQL and HSQL ) this > is not our bug but a knowed hibernate problem. > > So... > > What do you think about change from union subclass to another subclass > type? > > I'm waiting to your answers... :-) > -- View this message in context: http://www.nabble.com/Smartweb-Auth-and--problem-with-XDoclet--Hibernate-union-subclass-tf4761003s17546.html#a13624537 Sent from the SmartWeb Developers mailing list archive at Nabble.com. |
|
From: Gaetano P. <gpe...@sm...> - 2007-11-07 10:23:51
|
Ops i would say the hibernate problem (and not property) sorry.... :-P Gaetano Perrone wrote: > > In my opinion the union-subclass actual solution is very fine because it > makes the generated database more simple and more "developer-friendly". > Then I think it deserves at least an attempt to preserve it. > Could we think to identify accurately the hibernate property and try to > resolve it?? > > > svetrini wrote: >> >> At this time smartweb auth has a little problem... Actually union >> subclass has. >> hbm generation fails due to a bug on xdoclet union subclass. >> We have just sended patches to xdoclet team but none new version was >> released. >> I recently found another minor problem on auth module. It doesn't create >> schema on dbs different from PostgreSQL ( I tried on MySQL and HSQL ) >> this is not our bug but a knowed hibernate problem. >> >> So... >> >> What do you think about change from union subclass to another subclass >> type? >> >> I'm waiting to your answers... :-) >> > > -- View this message in context: http://www.nabble.com/Smartweb-Auth-and--problem-with-XDoclet--Hibernate-union-subclass-tf4761003s17546.html#a13624540 Sent from the SmartWeb Developers mailing list archive at Nabble.com. |
|
From: Roberto Lo G. <rlo...@sm...> - 2007-11-07 11:08:51
|
>From the Hibernate official documentation, chapter 9 "Inheritance Mapping": "Three tables are involved for the subclasses. Each table defines columns for all properties of the class, including inherited properties. The limitation of this approach is that if a property is mapped on the superclass, the column name must be the same on all subclass tables. (We might relax this in a future release of Hibernate.) The identity generator strategy is not allowed in union subclass inheritance, indeed the primary key seed has to be shared accross all unioned subclasses of a hierarchy." As stated in the documentation there's a problem on the id generator, plus we got into a "problem" on the database too: 2007/11/7, Gaetano Perrone <gpe...@sm...>: > > Ops i would say the hibernate problem (and not property) sorry.... > :-P > > > Gaetano Perrone wrote: > > > > In my opinion the union-subclass actual solution is very fine because it > > makes the generated database more simple and more "developer-friendly". > > Then I think it deserves at least an attempt to preserve it. > > Could we think to identify accurately the hibernate property and try to > > resolve it?? > > > > > > svetrini wrote: > >> > >> At this time smartweb auth has a little problem... Actually union > >> subclass has. > >> hbm generation fails due to a bug on xdoclet union subclass. > >> We have just sended patches to xdoclet team but none new version was > >> released. > >> I recently found another minor problem on auth module. It doesn't create > >> schema on dbs different from PostgreSQL ( I tried on MySQL and HSQL ) > >> this is not our bug but a knowed hibernate problem. > >> > >> So... > >> > >> What do you think about change from union subclass to another subclass > >> type? > >> > >> I'm waiting to your answers... :-) > >> > > > > > > -- > View this message in context: http://www.nabble.com/Smartweb-Auth-and--problem-with-XDoclet--Hibernate-union-subclass-tf4761003s17546.html#a13624540 > Sent from the SmartWeb Developers mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > smartweb-devel mailing list > sma...@li... > https://lists.sourceforge.net/lists/listinfo/smartweb-devel > |
|
From: Gaetano P. <gpe...@sm...> - 2007-11-07 10:56:26
|
I delve into the problem and hibernate documentation says that identity generator strategy is not allowed in union subclass inheritance, indeed the primary key seed has to be shared accross all unioned subclasses of a hierarchy. The suggested approch for generating table for concrete class is to use a sequence generator strategy instead of native. With this approch each table defines columns for all properties of the class, including inherited properties. The limitation of this approach is that if a property is mapped on the superclass, the column name must be the same on all subclass tables. (Hibernate group is going to relax this in a future release). This means that a dedicated class tree sequence could be introduced....Otherwise i don't know what happens using the hibernate_sequence as sequence instead of generator native... What do u thing about it?? svetrini wrote: > > At this time smartweb auth has a little problem... Actually union > subclass has. > hbm generation fails due to a bug on xdoclet union subclass. > We have just sended patches to xdoclet team but none new version was > released. > I recently found another minor problem on auth module. It doesn't create > schema on dbs different from PostgreSQL ( I tried on MySQL and HSQL ) this > is not our bug but a knowed hibernate problem. > > So... > > What do you think about change from union subclass to another subclass > type? > > I'm waiting to your answers... :-) > -- View this message in context: http://www.nabble.com/Smartweb-Auth-and--problem-with-XDoclet--Hibernate-union-subclass-tf4761003s17546.html#a13624965 Sent from the SmartWeb Developers mailing list archive at Nabble.com. |
|
From: Roberto Lo G. <rlo...@us...> - 2007-11-07 11:48:48
|
The problem using sequence generator is some database doesn't support
sequences: the consequence will be an unsable auth module on those
databases.
An analysis og pros and cons of the two choices could be more helpful.
Joined Subclass
Pros
# Well known and supported by xdoclet without needing to be patched
# Supported by all databases
# Allows database constraints
# Better performances if a list of Subjects is requested (only id and
display properties)
Cons
# Requires an additional Subject table
# Full queries on Subject, User or Group needs a JOIN on twoor three
tables
# Pessimistical locking need to acquire 2 locks
Union Subclass
Pros
# Better performances on quering User and Group entities as no JOIN is
requested
# No additional table exposed
# Easier to query using plain SQL outside Hibernate
Cons
# Quering Subject needs a UNION, whatever infos you need
# Same field on two tables
# Needs sequence support on the database
Gaetano Perrone wrote:
>
> I delve into the problem and hibernate documentation says that identity
> generator strategy is not allowed in union subclass inheritance, indeed
> the primary key seed has to be shared accross all unioned subclasses of a
> hierarchy.
> The suggested approch for generating table for concrete class is to use a
> sequence generator strategy instead of native. With this approch each
> table defines columns for all properties of the class, including inherited
> properties. The limitation of this approach is that if a property is
> mapped on the superclass, the column name must be the same on all subclass
> tables. (Hibernate group is going to relax this in a future release).
> This means that a dedicated class tree sequence could be
> introduced....Otherwise i don't know what happens using the
> hibernate_sequence as sequence instead of generator native...
> What do u thing about it??
>
--
View this message in context: http://www.nabble.com/Smartweb-Auth-and--problem-with-XDoclet--Hibernate-union-subclass-tf4761003s17546.html#a13625607
Sent from the SmartWeb Developers mailing list archive at Nabble.com.
|
|
From: Stefano V <st...@gm...> - 2007-11-08 13:54:58
|
Thank you for the answers! When i have time, I'll change the code to the joined subclass in auth module... 2007/11/7, Roberto Lo Giacco <rlo...@us...>: > > > The problem using sequence generator is some database doesn't support > sequences: the consequence will be an unsable auth module on those > databases. > > An analysis og pros and cons of the two choices could be more helpful. > > Joined Subclass > Pros > # Well known and supported by xdoclet without needing to be patched > # Supported by all databases > # Allows database constraints > # Better performances if a list of Subjects is requested (only id and > display properties) > Cons > # Requires an additional Subject table > # Full queries on Subject, User or Group needs a JOIN on twoor three > tables > # Pessimistical locking need to acquire 2 locks > > Union Subclass > Pros > # Better performances on quering User and Group entities as no JOIN is > requested > # No additional table exposed > # Easier to query using plain SQL outside Hibernate > Cons > # Quering Subject needs a UNION, whatever infos you need > # Same field on two tables > # Needs sequence support on the database > > > Gaetano Perrone wrote: > > > > I delve into the problem and hibernate documentation says that identity > > generator strategy is not allowed in union subclass inheritance, indeed > > the primary key seed has to be shared accross all unioned subclasses of > a > > hierarchy. > > The suggested approch for generating table for concrete class is to use > a > > sequence generator strategy instead of native. With this approch each > > table defines columns for all properties of the class, including > inherited > > properties. The limitation of this approach is that if a property is > > mapped on the superclass, the column name must be the same on all > subclass > > tables. (Hibernate group is going to relax this in a future release). > > This means that a dedicated class tree sequence could be > > introduced....Otherwise i don't know what happens using the > > hibernate_sequence as sequence instead of generator native... > > What do u thing about it?? > > > > -- > View this message in context: > http://www.nabble.com/Smartweb-Auth-and--problem-with-XDoclet--Hibernate-union-subclass-tf4761003s17546.html#a13625607 > Sent from the SmartWeb Developers mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > smartweb-devel mailing list > sma...@li... > https://lists.sourceforge.net/lists/listinfo/smartweb-devel > |
|
From: Roberto Lo G. <rlo...@sm...> - 2007-11-08 15:33:30
|
Humm... I think you still need the Gaetano's vote, plus you haven't voted yet.... 2007/11/8, Stefano V <st...@gm...>: > Thank you for the answers! > > When i have time, I'll change the code to the joined subclass in auth > module... > > 2007/11/7, Roberto Lo Giacco < rlo...@us...>: > > > > The problem using sequence generator is some database doesn't support > > sequences: the consequence will be an unsable auth module on those > > databases. > > > > An analysis og pros and cons of the two choices could be more helpful. > > > > Joined Subclass > > Pros > > # Well known and supported by xdoclet without needing to be patched > > # Supported by all databases > > # Allows database constraints > > # Better performances if a list of Subjects is requested (only id and > > display properties) > > Cons > > # Requires an additional Subject table > > # Full queries on Subject, User or Group needs a JOIN on twoor three > > tables > > # Pessimistical locking need to acquire 2 locks > > > > Union Subclass > > Pros > > # Better performances on quering User and Group entities as no JOIN is > > requested > > # No additional table exposed > > # Easier to query using plain SQL outside Hibernate > > Cons > > # Quering Subject needs a UNION, whatever infos you need > > # Same field on two tables > > # Needs sequence support on the database > > > > > > Gaetano Perrone wrote: > > > > > > I delve into the problem and hibernate documentation says that identity > > > generator strategy is not allowed in union subclass inheritance, indeed > > > the primary key seed has to be shared accross all unioned subclasses of > a > > > hierarchy. > > > The suggested approch for generating table for concrete class is to use > a > > > sequence generator strategy instead of native. With this approch each > > > table defines columns for all properties of the class, including > inherited > > > properties. The limitation of this approach is that if a property is > > > mapped on the superclass, the column name must be the same on all > subclass > > > tables. (Hibernate group is going to relax this in a future release). > > > This means that a dedicated class tree sequence could be > > > introduced....Otherwise i don't know what happens using the > > > hibernate_sequence as sequence instead of generator native... > > > What do u thing about it?? > > > > > > > -- > > View this message in context: > http://www.nabble.com/Smartweb-Auth-and--problem-with-XDoclet--Hibernate-union-subclass-tf4761003s17546.html#a13625607 > > Sent from the SmartWeb Developers mailing list archive at Nabble.com. > > > > > > > ------------------------------------------------------------------------- > > This SF.net email is sponsored by: Splunk Inc. > > Still grepping through log files to find problems? Stop. > > Now Search log events and configuration files using AJAX and a browser. > > Download your FREE copy of Splunk now >> http://get.splunk.com/ > > _______________________________________________ > > smartweb-devel mailing list > > sma...@li... > > > https://lists.sourceforge.net/lists/listinfo/smartweb-devel > > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > smartweb-devel mailing list > sma...@li... > https://lists.sourceforge.net/lists/listinfo/smartweb-devel > > |
|
From: Stefano V <st...@gm...> - 2007-11-08 17:14:34
|
Ok i vote for joined subclass... And now I'm waiting for Gaetano's vote :-) 2007/11/8, Roberto Lo Giacco <rlo...@sm...>: > > Humm... I think you still need the Gaetano's vote, plus you haven't > voted yet.... > > 2007/11/8, Stefano V <st...@gm...>: > > Thank you for the answers! > > > > When i have time, I'll change the code to the joined subclass in auth > > module... > > > > 2007/11/7, Roberto Lo Giacco < rlo...@us...>: > > > > > > The problem using sequence generator is some database doesn't support > > > sequences: the consequence will be an unsable auth module on those > > > databases. > > > > > > An analysis og pros and cons of the two choices could be more helpful. > > > > > > Joined Subclass > > > Pros > > > # Well known and supported by xdoclet without needing to be > patched > > > # Supported by all databases > > > # Allows database constraints > > > # Better performances if a list of Subjects is requested (only id > and > > > display properties) > > > Cons > > > # Requires an additional Subject table > > > # Full queries on Subject, User or Group needs a JOIN on twoor > three > > > tables > > > # Pessimistical locking need to acquire 2 locks > > > > > > Union Subclass > > > Pros > > > # Better performances on quering User and Group entities as no > JOIN is > > > requested > > > # No additional table exposed > > > # Easier to query using plain SQL outside Hibernate > > > Cons > > > # Quering Subject needs a UNION, whatever infos you need > > > # Same field on two tables > > > # Needs sequence support on the database > > > > > > > > > Gaetano Perrone wrote: > > > > > > > > I delve into the problem and hibernate documentation says that > identity > > > > generator strategy is not allowed in union subclass inheritance, > indeed > > > > the primary key seed has to be shared accross all unioned subclasses > of > > a > > > > hierarchy. > > > > The suggested approch for generating table for concrete class is to > use > > a > > > > sequence generator strategy instead of native. With this approch > each > > > > table defines columns for all properties of the class, including > > inherited > > > > properties. The limitation of this approach is that if a property is > > > > mapped on the superclass, the column name must be the same on all > > subclass > > > > tables. (Hibernate group is going to relax this in a future > release). > > > > This means that a dedicated class tree sequence could be > > > > introduced....Otherwise i don't know what happens using the > > > > hibernate_sequence as sequence instead of generator native... > > > > What do u thing about it?? > > > > > > > > > > -- > > > View this message in context: > > > http://www.nabble.com/Smartweb-Auth-and--problem-with-XDoclet--Hibernate-union-subclass-tf4761003s17546.html#a13625607 > > > Sent from the SmartWeb Developers mailing list archive at Nabble.com. > > > > > > > > > > > > ------------------------------------------------------------------------- > > > This SF.net email is sponsored by: Splunk Inc. > > > Still grepping through log files to find problems? Stop. > > > Now Search log events and configuration files using AJAX and a > browser. > > > Download your FREE copy of Splunk now >> http://get.splunk.com/ > > > _______________________________________________ > > > smartweb-devel mailing list > > > sma...@li... > > > > > https://lists.sourceforge.net/lists/listinfo/smartweb-devel > > > > > > > > > > ------------------------------------------------------------------------- > > This SF.net email is sponsored by: Splunk Inc. > > Still grepping through log files to find problems? Stop. > > Now Search log events and configuration files using AJAX and a browser. > > Download your FREE copy of Splunk now >> http://get.splunk.com/ > > _______________________________________________ > > smartweb-devel mailing list > > sma...@li... > > https://lists.sourceforge.net/lists/listinfo/smartweb-devel > > > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > smartweb-devel mailing list > sma...@li... > https://lists.sourceforge.net/lists/listinfo/smartweb-devel > |
|
From: Gaetano P. <gpe...@sm...> - 2007-11-08 22:17:06
|
I'll take the opportunity to express my vote: +1 to joined subclass Evaluating pros and cons i thing is the best we can do at this time svetrini wrote: > > Ok i vote for joined subclass... > And now I'm waiting for Gaetano's vote > > :-) > > 2007/11/8, Roberto Lo Giacco <rlo...@sm...>: >> >> Humm... I think you still need the Gaetano's vote, plus you haven't >> voted yet.... >> >> 2007/11/8, Stefano V <st...@gm...>: >> > Thank you for the answers! >> > >> > When i have time, I'll change the code to the joined subclass in auth >> > module... >> > >> > 2007/11/7, Roberto Lo Giacco < rlo...@us...>: >> > > >> > > The problem using sequence generator is some database doesn't support >> > > sequences: the consequence will be an unsable auth module on those >> > > databases. >> > > >> > > An analysis og pros and cons of the two choices could be more >> helpful. >> > > >> > > Joined Subclass >> > > Pros >> > > # Well known and supported by xdoclet without needing to be >> patched >> > > # Supported by all databases >> > > # Allows database constraints >> > > # Better performances if a list of Subjects is requested (only id >> and >> > > display properties) >> > > Cons >> > > # Requires an additional Subject table >> > > # Full queries on Subject, User or Group needs a JOIN on twoor >> three >> > > tables >> > > # Pessimistical locking need to acquire 2 locks >> > > >> > > Union Subclass >> > > Pros >> > > # Better performances on quering User and Group entities as no >> JOIN is >> > > requested >> > > # No additional table exposed >> > > # Easier to query using plain SQL outside Hibernate >> > > Cons >> > > # Quering Subject needs a UNION, whatever infos you need >> > > # Same field on two tables >> > > # Needs sequence support on the database >> > > >> > > >> > > Gaetano Perrone wrote: >> > > > >> > > > I delve into the problem and hibernate documentation says that >> identity >> > > > generator strategy is not allowed in union subclass inheritance, >> indeed >> > > > the primary key seed has to be shared accross all unioned >> subclasses >> of >> > a >> > > > hierarchy. >> > > > The suggested approch for generating table for concrete class is >> to >> use >> > a >> > > > sequence generator strategy instead of native. With this approch >> each >> > > > table defines columns for all properties of the class, including >> > inherited >> > > > properties. The limitation of this approach is that if a property >> is >> > > > mapped on the superclass, the column name must be the same on all >> > subclass >> > > > tables. (Hibernate group is going to relax this in a future >> release). >> > > > This means that a dedicated class tree sequence could be >> > > > introduced....Otherwise i don't know what happens using the >> > > > hibernate_sequence as sequence instead of generator native... >> > > > What do u thing about it?? >> > > > >> > > >> > > -- >> > > View this message in context: >> > >> http://www.nabble.com/Smartweb-Auth-and--problem-with-XDoclet--Hibernate-union-subclass-tf4761003s17546.html#a13625607 >> > > Sent from the SmartWeb Developers mailing list archive at Nabble.com. >> > > >> > > >> > > >> > >> ------------------------------------------------------------------------- >> > > This SF.net email is sponsored by: Splunk Inc. >> > > Still grepping through log files to find problems? Stop. >> > > Now Search log events and configuration files using AJAX and a >> browser. >> > > Download your FREE copy of Splunk now >> http://get.splunk.com/ >> > > _______________________________________________ >> > > smartweb-devel mailing list >> > > sma...@li... >> > > >> > https://lists.sourceforge.net/lists/listinfo/smartweb-devel >> > > >> > >> > >> > >> ------------------------------------------------------------------------- >> > This SF.net email is sponsored by: Splunk Inc. >> > Still grepping through log files to find problems? Stop. >> > Now Search log events and configuration files using AJAX and a browser. >> > Download your FREE copy of Splunk now >> http://get.splunk.com/ >> > _______________________________________________ >> > smartweb-devel mailing list >> > sma...@li... >> > https://lists.sourceforge.net/lists/listinfo/smartweb-devel >> > >> > >> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by: Splunk Inc. >> Still grepping through log files to find problems? Stop. >> Now Search log events and configuration files using AJAX and a browser. >> Download your FREE copy of Splunk now >> http://get.splunk.com/ >> _______________________________________________ >> smartweb-devel mailing list >> sma...@li... >> https://lists.sourceforge.net/lists/listinfo/smartweb-devel >> > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > smartweb-devel mailing list > sma...@li... > https://lists.sourceforge.net/lists/listinfo/smartweb-devel > > -- View this message in context: http://www.nabble.com/Smartweb-Auth-and--problem-with-XDoclet--Hibernate-union-subclass-tf4761003s17546.html#a13657083 Sent from the SmartWeb Developers mailing list archive at Nabble.com. |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X