One thought regarding Compass. Have you been looking at hibernate-search? It is essential the same thing, but without the Compass dependency.
Regards Ted 2007/10/4, Kalle Korhonen <[EMAIL PROTECTED]>: > Hello "Trailers" :) > > Just as promised, we are happy to announce Trails 1.1.1 release! It feels > it's been so long, even though it was less than six months ago we hit 1.0. > The single biggest difference between 1.0 and 1.1 is the modularized > architecture. The documentation gives you an > overview<http://trailsframework.org/Overview?nocache>of the new > modules; the important thing is it allows Trails to be used in > more heterogenous use cases, independent of whether your project is using > Hibernate or Acegi. One of the other more visible changes we also made is > the new default user interface and layout that's designed to be compatible > with AppFuse so users of that project should feel right at home trying out > our examples. One more super-exciting feature is our first draft of > full-text search based on Trails-Compass integration that we have a whole > section about in the User > Guide<http://trailsframework.org/Querying+entities+and+full-text+search?nocache>. > The release history > <http://trailsframework.org/Release+history?nocache>(also copied > below) gives you a brief overview of the major features and a > summary of the 30 bugs that were fixed in this release. > > While the initial plan for 1.1 was to integrate with Tapestry 4.1.2, > 4.1.3contained important bug fixes for us and since it was released > just > recently, we decided to go with it for 1.1.x. We've also upgraded versions > of several other dependencies, check out the dependency > report<http://www.trailsframework.org/site/modules/trails-core/dependencies.html>to > see exactly what. Trails libraries are already available in > repo1.maven.org <http://repo1.maven.org/maven2/org/trailsframework/trails>. > We've also revamped our website to transparently blend Maven reports with > Confluence-based Codehaus project site. Go visit > http://trailsframework.organd enjoy! > 1.1.1 Release summary (release date 2007-10-02) > * Fixes minor issues in 1.1 release: > o Fixed archetypes referring to snapshot versions > o Added a default exception page to the archetype > o Fixed an issue with validating unique entities when CGLIB > enhanced classes are used > * Branch (1.1.x) available for further maintenance releases > > 1.1 Release summary (release date 2007-09-30) > * Features > o Move to Tapestry 4.1.3 ( DONE) > o Modularization ( DONE) > o Owner instance -based security ( DONE) > o Search refactoring + Compass / Lucene Integration ( DONE) > o Exception handling ( DONE) > o New look & feel, multiple themes ( DONE) > * Fixed bugs in 1.1: > T Key Summary > Bug TRAILS-78 Editing a child object from a indexed list > "child" collection creates duplicates. > New Feature TRAILS-30 @OneToOne needs user interface semantics > > Bug TRAILS-50 Security Bug: infinite loop on special > configuration > Bug TRAILS-49 Security BUG: Login.html does not render > Bug TRAILS-61 Login.html requires username/password entry > twice > New Feature TRAILS-59 ObjectTable needs to be instrumented to > be able to automatically render images > Bug TRAILS-56 Security is broken, ROLE_ANONYMOUS is > constrained from creating users - impact from merge 582 > Bug TRAILS-87 Property Editor is broken ... serious flawed > behavior semantics 4.1.2 Branch > Bug TRAILS-42 Trails is not using success-cancel-refresh > actions listeners in its ObjectForm > Bug TRAILS-85 Trails crashes stale after sitting overnight > Bug TRAILS-86 Custom Editors no longer possible in trails > OGNL-105 OGNL-111 > Bug TRAILS-81 regression:OneToOne decoration faulty...HARD > OneToOne associations broken > Bug TRAILS-33 hasCyclicRelationships solution is merging on > entities not persisted yet > Bug TRAILS-3 trails-archetype generates a ${basedir} directory > New Feature TRAILS-37 remove Tapernate > Task TRAILS-38 re-modularize Trails > Improvement TRAILS-40 upgrade to Spring 2.0.6 and Tapestry > 4.1.2 > Improvement TRAILS-52 The pages ServiceEncoder should use the > extension ".page" (so should the filters) > Improvement TRAILS-66 login page needs a proper tapestry form > New Feature TRAILS-82 SINGLETON Annotation required to > properly manage these at entity level > Improvement TRAILS-48 Manual hand editing is required to > properly integrate security > New Feature TRAILS-27 Provide facility to expose objects as > web services > New Feature TRAILS-31 Required Fields indicator (top of page > and on each field) > Bug TRAILS-80 @Transient should force "searchable = false" > Task TRAILS-46 remove from IPropertyDescriptor, unused and > confusing parentClassDescriptor. > Improvement TRAILS-69 use tapestry @Label component in our > editors > Wish TRAILS-34 create a more compelling web design > Bug TRAILS-77 The Camel casing should be done only to the > fieldname and not to the display name specified in the PropertyDescriptor > Improvement TRAILS-39 reduce checkstyle errors and warnings. > -- /ted --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
