Colin Chalmers wrote:

> 1. Would I be correct in saying that for every table in a database there
> should be a Peer Object, for examples PermissionSet, RoleSet and
> CurrencySet (my own one)?

Using Peers is optional in your own code. Still, it may be profitable 
to learn how to use them, because they can provide an abstraction layer 
between your business objects and their underlying data source.

> 2. In the Turbine.properties file there is mention of encrypted
> passwords using SHA, is this working as I can only find an MD5 class.

The code in UserFactory requests SHA message digest from standard java.security
package. There is MD5 implementation in Turbine codebase, with a comment that
there are some JRE implementations (notably Kaffe) that don't have java.security
package. 
I believe that we could safely change UserFactory to use org.apache.java.security.MD5
because for our purpose both algorithms are equaly good.
When talking about LDAP backend for user class, Craig Berry pointed out that 
validate(String password) should be a method in User interface to make 
authentication implementation pluggable.


> 3. I would like to have a (Java) program that gets started from Turbine,
> using the scheduler, and gets it's properties from the same file as
> Turbine. Is this possible/wise?

If you make a class that implemnts ScheduledJob to do what you need, it
will be running inside the same JVM sandbox as the Turbine servlet, and therefore
you could use TurbineResources.getString(String key) etc. to access your config 
options.
Just name your keys so that they wouldn't class with future turbine ouptions 
(myapp.option.defautl=x instead of default.option=x) and you should be fine.

Now. Using TurbineResources.properties for your configuration is possible and easy.
You have to decide for yourself if it's better to have one config file or two.

> 4. I would like to have a (Java) program that gets started from Turbine,
> using the scheduler, and uses the same log files as Turbine. Is this
> possible/wise?

Same as above. Your ScheduledJob implementation can use Log class with no 
problems. There is also possiblilty to use this class to use multiple log
files simultaneously, so you could use standard mechanism, and still
have you own log file.

Hope that this helps
Rafal


------------------------------------------------------------
To subscribe:        [EMAIL PROTECTED]
To unsubscribe:      [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?:           [EMAIL PROTECTED]

Reply via email to