You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@turbine.apache.org by Jürgen Hoffmann <jh...@byteaction.de> on 2003/06/27 10:23:53 UTC
O.a.t.ObjectUtils.addOnce
Hi,
I would like to get rid of some of the deprecation warnings in current
turbine head.
o.a.t.ObjectUtils.addOnce is deprecated. How should this be replaced by
commons-lang Object Utils?
I do not see a function Commons-lang ObjectUtils that provides this
functionality?
Kind regards
Jürgen Hoffmann
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-dev-help@jakarta.apache.org
Re: AW: O.a.t.ObjectUtils.addOnce
Posted by "Henning P. Schmiedehausen" <hp...@intermeta.de>.
=?iso-8859-1?Q?J=FCrgen_Hoffmann?= <jh...@byteaction.de> writes:
If you compile with Eclipse and not with the Maven build tool (which is
the only recommended and supported way to build the HEAD), you don't
have the torque generated peer classes for database access.
>JobEntry.java
>TurbineNonPersistentSchedulerService.java
>TurbineSchedulerService.java
>WorkerThread.java
Scheduler. Needs the Scheduler peer classes
>GroupPeerManagerConstants.java
>PermissionPeerManager.java
>PermissionPeerManagerConstants.java
>RolePeerManager.java
>RolePeerManagerConstans.java
>UserPeerManager.java
>TorqueSecurityService.java
Torque Security service. Needs the Torque Security Service peer classes.
>Did i miss to checkout something? What would be a good way to implement
Yes. maven torque:om
Regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
hps@intermeta.de +49 9131 50 654 0 http://www.intermeta.de/
Java, perl, Solaris, Linux, xSP Consulting, Web Services
freelance consultant -- Jakarta Turbine Development -- hero for hire
--- Quote of the week: "It is pointless to tell people anything when
you know that they won't process the message." --- Jonathan Revusky
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-dev-help@jakarta.apache.org
Re: AW: O.a.t.ObjectUtils.addOnce
Posted by Peter Courcoux <pe...@courcoux.biz>.
Jurgen,
I am pretty sure that I have seen the same set of errors when I started
building 2.3. I think it is related to the version of maven and the
version of the torque plugin. From memory, which can be dangerous =:-)
I think I compiled the torque-maven plugin from maven b9 and dropped it
into the plugins repo in my maven b8 installation, then compiled turbine
using maven b8.
Hope this helps, but I don't guarantee it!
Regards,
Peter
On Fri, 2003-06-27 at 10:18, Jürgen Hoffmann wrote:
> Hi,
>
> Ok i see =). We have implemented a quartz scheduler service, that i
> would like to share with the community. It is written for turbine 2.2
> and i want to write it for t2.3. This is why I checked out current HEAD.
> And did a maven eclipse. After setting the source path correctly i still
> get 94 errors in:
>
> JobEntry.java
> TurbineNonPersistentSchedulerService.java
> TurbineSchedulerService.java
> WorkerThread.java
> GroupPeerManagerConstants.java
> PermissionPeerManager.java
> PermissionPeerManagerConstants.java
> RolePeerManager.java
> RolePeerManagerConstans.java
> UserPeerManager.java
> TorqueSecurityService.java
>
> Did i miss to checkout something? What would be a good way to implement
> a quartz scheduler service in t2.3 as an AvalonComponent (I don't know
> if that is possible (should be though)), or by extending Service?
>
> Is the community interested in such a scheduler solution or will the
> scheduler code be abandoned?
>
> Kind regards
>
> Jürgen Hoffmann
> ByteACTION GmbH
>
>
> -----Ursprüngliche Nachricht-----
> Von: Henning P. Schmiedehausen [mailto:hps@intermeta.de]
> Gesendet: Freitag, 27. Juni 2003 10:36
> An: turbine-dev@jakarta.apache.org
> Betreff: Re: O.a.t.ObjectUtils.addOnce
>
>
> =?iso-8859-1?Q?J=FCrgen_Hoffmann?= <jh...@byteaction.de> writes:
>
> Ugh, right on the spot. :-)
>
> That's the one where we have no real replacement. Replacement is to use
> a data structure which adds a member only once but keeps its sequence.
>
> I once had such a bugger, called an OrderedSet, and this went into
> commons collections as SequencedSet decorator. However, it will be only
> available with the next commons collections release (the CVS speaks of
> "3.0"). However, I deprecated this so I can remove it in the 2.4-dev
> cycle in favour of the SequencedSet. As far as I know, Martin has a
> similar construct in the Torque code which could be replaced with
> SequencedSet.
>
> If you want to get rid of the deprecation warning, remove the
> @deprecated =;-) Or get a commons-collections snapshot, replace the
> underlying Sets with SequencedSet and replace all "addOnce" with "add".
>
> Regards
> Henning
--
Peter Courcoux <pe...@courcoux.biz>
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-dev-help@jakarta.apache.org
AW: O.a.t.ObjectUtils.addOnce
Posted by Jürgen Hoffmann <jh...@byteaction.de>.
Hi,
Ok i see =). We have implemented a quartz scheduler service, that i
would like to share with the community. It is written for turbine 2.2
and i want to write it for t2.3. This is why I checked out current HEAD.
And did a maven eclipse. After setting the source path correctly i still
get 94 errors in:
JobEntry.java
TurbineNonPersistentSchedulerService.java
TurbineSchedulerService.java
WorkerThread.java
GroupPeerManagerConstants.java
PermissionPeerManager.java
PermissionPeerManagerConstants.java
RolePeerManager.java
RolePeerManagerConstans.java
UserPeerManager.java
TorqueSecurityService.java
Did i miss to checkout something? What would be a good way to implement
a quartz scheduler service in t2.3 as an AvalonComponent (I don't know
if that is possible (should be though)), or by extending Service?
Is the community interested in such a scheduler solution or will the
scheduler code be abandoned?
Kind regards
Jürgen Hoffmann
ByteACTION GmbH
-----Ursprüngliche Nachricht-----
Von: Henning P. Schmiedehausen [mailto:hps@intermeta.de]
Gesendet: Freitag, 27. Juni 2003 10:36
An: turbine-dev@jakarta.apache.org
Betreff: Re: O.a.t.ObjectUtils.addOnce
=?iso-8859-1?Q?J=FCrgen_Hoffmann?= <jh...@byteaction.de> writes:
Ugh, right on the spot. :-)
That's the one where we have no real replacement. Replacement is to use
a data structure which adds a member only once but keeps its sequence.
I once had such a bugger, called an OrderedSet, and this went into
commons collections as SequencedSet decorator. However, it will be only
available with the next commons collections release (the CVS speaks of
"3.0"). However, I deprecated this so I can remove it in the 2.4-dev
cycle in favour of the SequencedSet. As far as I know, Martin has a
similar construct in the Torque code which could be replaced with
SequencedSet.
If you want to get rid of the deprecation warning, remove the
@deprecated =;-) Or get a commons-collections snapshot, replace the
underlying Sets with SequencedSet and replace all "addOnce" with "add".
Regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
hps@intermeta.de +49 9131 50 654 0 http://www.intermeta.de/
Java, perl, Solaris, Linux, xSP Consulting, Web Services
freelance consultant -- Jakarta Turbine Development -- hero for hire
--- Quote of the week: "It is pointless to tell people anything when you
know that they won't process the message." --- Jonathan Revusky
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-dev-help@jakarta.apache.org
Re: O.a.t.ObjectUtils.addOnce
Posted by "Henning P. Schmiedehausen" <hp...@intermeta.de>.
=?iso-8859-1?Q?J=FCrgen_Hoffmann?= <jh...@byteaction.de> writes:
Ugh, right on the spot. :-)
That's the one where we have no real replacement. Replacement is to
use a data structure which adds a member only once but keeps its
sequence.
I once had such a bugger, called an OrderedSet, and this went into
commons collections as SequencedSet decorator. However, it will be
only available with the next commons collections release (the CVS
speaks of "3.0"). However, I deprecated this so I can remove it in the
2.4-dev cycle in favour of the SequencedSet. As far as I know, Martin
has a similar construct in the Torque code which could be replaced
with SequencedSet.
If you want to get rid of the deprecation warning, remove the
@deprecated =;-) Or get a commons-collections snapshot, replace the
underlying Sets with SequencedSet and replace all "addOnce" with
"add".
Regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
hps@intermeta.de +49 9131 50 654 0 http://www.intermeta.de/
Java, perl, Solaris, Linux, xSP Consulting, Web Services
freelance consultant -- Jakarta Turbine Development -- hero for hire
--- Quote of the week: "It is pointless to tell people anything when
you know that they won't process the message." --- Jonathan Revusky
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-dev-help@jakarta.apache.org