in 2 different queries! I found via my usage statistics today that both "j2ee designs" and "raible" (of course) turn up this website as it's first choices. Cool, and after checking the cached versions, that was before adding new meta tags last week!
From the struts-dev list and Erik Hatcher:
My XDoclet Struts Validator validation.xml (for Struts 1.1) has been
posted to the XDoclet tracker.
I'm hoping it will be added to the codebase and put into the upcoming
new release of XDoclet (although I'm using XDoclet from CVS builds).
Read the HTML file attachment on the issue page above for an example of how it works.
If you're hand-coding validation.xml and using ValidatorForm extensions then this is for you!
I can't wait to use XDoclet in my next project! On my current project, I've already written most of the ValidationForms I need. I used the Generator package to do this, but I hope to either (1) refactor my current project to use Castor/XDoclet like Roller, or (2) use it on my next project.
I ordered an Ant book this evening in hopes of learning a lot more about Ant. I think I know a lot, but there's always room for more knowledge.
I've used a "quick and dirty" technique for making a private roller weblog for family members only. Maybe Lance can use this to create a private weblog for his mom ;-)
- Create a new roller user: i.e. "mom"
- Create a user for user's to login with (I just created another roller user): i.e. "kids"
- Add a new role (i.e. "family") to the "role" table in your database
- Add two new records to the role table so the "mom" and "kids" roles have the "family" role
- Add the following to web.xml:
<security-constraint>
<web-resource-collection>
<web-resource-name>My Family</web-resource-name>
<description>Restricted to Family Members Only</description>
<url-pattern>/page/mom/*</url-pattern>
<url-pattern>/rss/mom</url-pattern>
<http-method>POST</http-method>
<http-method>GET</http-method>
</web-resource-collection>
<auth-constraint>
<role-name>editor</role-name>
<role-name>family</role-name>
</auth-constraint>
</security-constraint>
- Distribute the "kids" username/password to the appropriate parties.
Hope this helps!