RE: BaseValueParser.getInt(String name)

+1 > -Original Message- > From: Scott Eade [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, January 22, 2003 6:10 PM > To: turbine-dev > Subject: BaseValueParser.getInt(String name) > > > Does anyone have any objection to changing > BaseValueParser.getInt(String > name) such that when the

RE: BaseValueParser.getInt(String name)

utterly non-binding +1 > -Original Message- > From: Scott Eade [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, January 22, 2003 4:10 PM > To: turbine-dev > Subject: BaseValueParser.getInt(String name) > > > Does anyone have any objection to changing > BaseValueParser.getInt(String > name

BaseValueParser.getInt(String name)

Does anyone have any objection to changing BaseValueParser.getInt(String name) such that when the name does not exist a null is returned rather than an Integer with the value 0? It makes sense for a 0 to be returned when getInt() is used, but for geInteger() it should surely be a null. I see two

cvs commit: jakarta-turbine-2/src/java/org/apache/turbine/services/schedule TurbineScheduler.java

quintonm2003/01/22 14:04:48 Modified:src/java/org/apache/turbine/services/schedule TurbineScheduler.java Log: - updated javadocs Revision ChangesPath 1.3 +6 -6 jakarta-turbine-2/src/java/org/apache/turbine/services/schedule/TurbineSched

cvs commit: jakarta-turbine-2/src/java/org/apache/turbine/services/schedule TurbineSchedulerService.java

quintonm2003/01/22 14:04:38 Modified:src/java/org/apache/turbine/services/schedule TurbineSchedulerService.java Log: - updated javadocs - adding/modifing/removing a job will not automatically restart the scheduler - combined addJob and updateJob methods

cvs commit: jakarta-turbine-2/src/java/org/apache/turbine/services/schedule TurbineNonPersistentSchedulerService.java

quintonm2003/01/22 14:03:35 Modified:src/java/org/apache/turbine/services/schedule TurbineNonPersistentSchedulerService.java Log: - updated javadocs - TurbineResources.getXXX has been replaced with getConfiguration().getXXX - adding/modifing/removing a job

Re: Core Schema

On 23/01/2003 6:11 AM, "Yuemei Sun" <[EMAIL PROTECTED]> wrote: > There is a table Turbine_Role_Permission, which, according to the > documenation, allows several Roles to share a Permission. Any > particualr reason why the relationship between Role and Permision > is designed as many-to-one, inst

RE: LDAPSecurityService

Yes. -- Humberto > -Original Message- > From: Christian Willy Asmussen [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, January 22, 2003 1:49 PM > To: Turbine Developers List > Subject: LDAPSecurityService > > > Humberto Hernandez Torres wrote: > > >Thanks to Martin, Quinton and Henning f

LDAPSecurityService

Humberto Hernandez Torres wrote: Thanks to Martin, Quinton and Henning for trusting me. I have some improvements to LDAP that need to be included and I would like ... Is this about the ldapsecurity? -- To unsubscribe, e-mail: For additional commands, e-mail:

cvs commit: jakarta-turbine-2/src/java/org/apache/turbine/services/schedule JobEntry.java

quintonm2003/01/22 08:26:20 Modified:src/java/org/apache/turbine/services/schedule JobEntry.java Log: Added a simple log statement at the INOF level to log when the next scheduled execution of a job will occur. Revision ChangesPath 1.10 +8 -1 jakarta-turbine-2

Core Schema

There is a table Turbine_Role_Permission, which, according to the documenation, allows several Roles to share a Permission. Any particualr reason why the relationship between Role and Permision is designed as many-to-one, instead of one-to-one? Thanks -- To unsubscribe, e-mail:

cvs commit: jakarta-turbine-2/src/java/org/apache/turbine/om/security TurbineUser.java

quintonm2003/01/22 07:22:12 Modified:src/java/org/apache/turbine/om/security TurbineUser.java Log: Fix to TTWS30:TURBINE_USER is updated on when the session is unbound causing changes to be lost - A new method called saveOnSessionUnbind() bas been implemnented in the secuerity

cvs commit: jakarta-turbine-2/src/java/org/apache/turbine/services/security/passive PassiveUserManager.java

quintonm2003/01/22 07:21:39 Modified:src/java/org/apache/turbine/services/security BaseSecurityService.java SecurityService.java TurbineSecurity.java UserManager.java src/java/org/apache/turbine/services/security/db

[SOURCE] Issue #TTWS30 modified

Issue TTWS30 has just been modified by user quintonm You can view the issue detail at the following URL: The following modifications were made to this issue: Status changed from 'New' to 'Closed' Comment: fixed in CVS HEAD Resolution set to 'Fix

Object in servlet context & Turbine initialization

Is there any way to put my designed Runnable object in servlet context AFTER turbine startup and start it? Eugeny N. Dzhurinsky WEB-developer Private cell +380677940549 Inet dept., MARKA L

[GUMP] Build Failure - jakarta-turbine-tdk

This email is autogenerated from the output from: Buildfile: build.xml BUILD FAILED Target `jar' does not exist in this

[GUMP] Build Failure - jakarta-turbine-2

This email is autogenerated from the output from: Buildfile: build-gump.xml jar: [mkdir] Created dir: /home/rubys/jak