> But allow me one more question: > > Do i have to rebuild (ant) > Jetspeed again, > if I made changes of my classes > (e.g. ThomasSecurityProvider) > or is it just enough to deploy my classes > into WEB-INF/CLASSES ...
You do not need to rebuild Jetspeed with ANT again, just drop your classes to WEB-INF/classes, put your own JetspeedSecurity.properties in WEB-INF/conf and restart the server. Or preferably, put your classes into a JAR archive and drop that in WEB-INF/lib directory. But if your override some original Jetspeed classes, do not put them inside the JAR archive, because the original classes in WEB-INF/classes will be found from the classpath before your own classes, and your code would not be executed. If you plan to write your own implementation for one of the security interfaces, I strongly suggest that you write your own implementation for all of them. Why would you want to use a security implementation in which users are stored in separate place than roles, groups and permissions? This makes no sense to me. If you plan to override many classes (or user interfaces) of Jetspeed, I suggest that you create your own ANT-based build process for it. Dropping a class or two manually to the webapp directory may seem to be a good thing to do for a while, but after doing it N times, you will get annoyed. I use an incremental build process that first calls jakarta-jetspeed's build script, then builds my own stuff and adds it to the pre-existing WAR archive. Then you always get a systematic distribution archive as a result, which includes all the necessary files. When adding things to existing webapp by hand, you will always forget to do some things that you should have done, like updating the JetspeedSecurity.properties file. Use ANT. A Java developer cannot live without it. Regards, Sami -- Sami Leino Software Developer, Netorek Oy, Turku, Finland Email: [EMAIL PROTECTED] Phone: +358 44 0140499 -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
