Re: [trails-announce] [ANNOUNCEMENT] Tapestry JPA 2.0.0
Excellent job Piero! Kalle On Tue, Jan 26, 2010 at 2:39 AM, Piero Sartini li...@pierosartini.de wrote: I am proud to announce the first release of tapestry-jpa which is now part of the tynamo[1] project. It features full JPA2 integration and provides you with all the functionalities known from tapestry's hibernate support. To get started, you may want to take a look at our Tapestry JPA Guide[2]. Many thanks goes to Pierce T. Wetter who helped out with the code as well as to Kalle Korhonen who made this release possible by guiding me through tynamo's release process. Note that this module is compatible with JPA2 only and that we've changed the naming. Modules are now named tapestry-jpa-core and tapestry-jpa, the version is 2.0.0 which gives you a hint about the JPA version its compatible with. The artifacts are available inside the maven central repository. Piero [1] http://tynamo.org [2] http://tynamo.org/tapestry-jpa+guide - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
trails repo broken overnight
!-- something is going on with their repo repository idtrails.codehaus.org/id nameTrails Repository/name urlhttp://trails.codehaus.org/repository/url /repository -- If your building trails to your local repo, populate javax and build with trails repo commented out as above. This will get you by as a workaround until it is resolved.Best regards Ken in nashua _ Need to know the score, the latest news, or you need your Hotmail®-get your fix. http://www.msnmobilefix.com/Default.aspx
Re: [ANN] Trails 1.1.1 release
Hi Ted,
Yes, I did look at hibernate-search, in fact the very first full-text
search implementation in Trails was based on the first implementation
of hibernate-search. At that time it came bundled with
hibernate-annotations.
Then I moved to Compass because its integration with spring. Among
other benefits is also really easy to integrate Compass with other
persistence technologies besides hibernate.
Alejandro.
On 10/10/07, Ted Steen [EMAIL PROTECTED] wrote:
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
overviewhttp://trailsframework.org/Overview?nocacheof 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
Guidehttp://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
reporthttp://www.trailsframework.org/site/modules/trails-core/dependencies.htmlto
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
Trails or Congnition ;-)
I wanted to use either Trails or Cognition for the next project. However, Cognition seems to have ceased to exist and Trails does not work. Maven does not find everything (Quick Start): Reason: Error getting POM for 'org.apache.myfaces.tobago:maven-apt-plugin' from the repository: Error transferring file org.apache.myfaces.tobago:maven-apt-plugin:pom:1.0.11 from the specified remote repositories: tapestry-snapshots (http://people.apache.org/~hlship/tapestry-snapshot-reposit ory/), central (http://repo1.maven.org/maven2), webobjects.mdimension.com/plugin/snapshots (http://webobjects.mdimension.com/m aven2/snapshots), webobjects.mdimension.com/plugin/releases (http://webobjects.mdimension.com/ma ven2/releases) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Trails or Congnition ;-)
Hi I'm having no problems with Trails. ;-) From your log, it looks like a maven/network problem. Try again, and again, and if you keep having this problem try deleting your local copy of the apt plugin. If you decide to go with Trails you are welcome to join us in our users mailing list: http://xircles.codehaus.org/manage_email/[EMAIL PROTECTED] Saludos. Alejandro. On 10/10/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: I wanted to use either Trails or Cognition for the next project. However, Cognition seems to have ceased to exist and Trails does not work. Maven does not find everything (Quick Start): Reason: Error getting POM for 'org.apache.myfaces.tobago:maven-apt-plugin' from the repository: Error transferring file org.apache.myfaces.tobago:maven-apt-plugin:pom:1.0.11 from the specified remote repositories: tapestry-snapshots (http://people.apache.org/~hlship/tapestry-snapshot-reposit ory/), central (http://repo1.maven.org/maven2), webobjects.mdimension.com/plugin/snapshots (http://webobjects.mdimension.com/m aven2/snapshots), webobjects.mdimension.com/plugin/releases (http://webobjects.mdimension.com/ma ven2/releases) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Trails or Congnition ;-)
But when is the codehaus apt plugin going to be released? I found it much better than the tobago one. Christian. On 10-Oct-07, at 11:18 AM, Kalle Korhonen wrote: On 10/10/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: I wanted to use either Trails or Cognition for the next project. However, Cognition seems to have ceased to exist and Trails does not work. I've talked with the founder of Cognition a few times, and yes, the project was scrapped. Trails works just fine and is stable, but you'll get a better response on our mailing lists. Regarding apt-plugin, it's in repo1: http://repo1.maven.org/maven2/org/apache/myfaces/tobago/maven-apt-plugin/1.0.11/ . I'd check that you don't have a corrupted pom/jar in your local repo. Kalle Maven does not find everything (Quick Start): Reason: Error getting POM for 'org.apache.myfaces.tobago:maven-apt- plugin' from the repository: Error transferring file org.apache.myfaces.tobago:maven-apt-plugin:pom:1.0.11 from the specified remote repositories: tapestry-snapshots ( http://people.apache.org/~hlship/tapestry-snapshot-reposit ory/), central (http://repo1.maven.org/maven2), webobjects.mdimension.com/plugin/snapshots ( http://webobjects.mdimension.com/m aven2/snapshots), webobjects.mdimension.com/plugin/releases ( http://webobjects.mdimension.com/ma ven2/releases) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Trails or Congnition ;-)
On 10/10/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: I wanted to use either Trails or Cognition for the next project. However, Cognition seems to have ceased to exist and Trails does not work. I've talked with the founder of Cognition a few times, and yes, the project was scrapped. Trails works just fine and is stable, but you'll get a better response on our mailing lists. Regarding apt-plugin, it's in repo1: http://repo1.maven.org/maven2/org/apache/myfaces/tobago/maven-apt-plugin/1.0.11/. I'd check that you don't have a corrupted pom/jar in your local repo. Kalle Maven does not find everything (Quick Start): Reason: Error getting POM for 'org.apache.myfaces.tobago:maven-apt-plugin' from the repository: Error transferring file org.apache.myfaces.tobago:maven-apt-plugin:pom:1.0.11 from the specified remote repositories: tapestry-snapshots ( http://people.apache.org/~hlship/tapestry-snapshot-reposit ory/), central (http://repo1.maven.org/maven2), webobjects.mdimension.com/plugin/snapshots ( http://webobjects.mdimension.com/m aven2/snapshots), webobjects.mdimension.com/plugin/releases ( http://webobjects.mdimension.com/ma ven2/releases) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [ANN] Trails 1.1.1 release
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
overviewhttp://trailsframework.org/Overview?nocacheof 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
Guidehttp://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
reporthttp://www.trailsframework.org/site/modules/trails-core/dependencies.htmlto
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
Re: Trails or Congnition ;-)
Heh. I wasn't really asking - more just trying to be funny. I've already asked the codehaus people. Christian. On 10-Oct-07, at 1:34 PM, Kalle Korhonen wrote: Probably not the right list to ask that one. Trails-wise, Tobago's apt plugin has its issues, but suffices for the purpose. Ideally, we'd like to and eventually will get rid of the whole plugin in Trails. Kalle - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [ANN] Trails 1.1.1 release
Thanks for all the effort.
I can tell you that Trails demos pretty darn well when I show it off
as part of No Fluff Just Stuff.
I'm looking forward to Trails 5 for Tapestry 5 !
On 10/4/07, Kalle Korhonen [EMAIL PROTECTED] wrote:
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
overviewhttp://trailsframework.org/Overview?nocacheof 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
Guidehttp://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
reporthttp://www.trailsframework.org/site/modules/trails-core/dependencies.htmlto
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
Trails
Hi everyone, I'm looking for feedback here, I planning of using Trails to help gain speed with my Tapestry 4.0 development. Somebody use it? Should I ? What are the pinfall ? What are your advise... Thanks for your feedback
Re: Trails
I only use trails for my Tapestry-4 development. Mainly because I enjoyed the steep initial learning curve of tapestry and needed something to lean on. The main reason I liked and like trails is because the ant scripts together with hibernate tools generate all tables in my MySQL database automatically from my POJOs. I just need to grok how to @annotate right, which in itself have been interresting, so all lookup tables, collections, relations, etc. gets done. Another big goodie is that trails have a default list, search and edit page for all POJOs, which are plain Tapestry html/page combos. Also, there are ant/maven tasks to generate individual list or edit pages for POJOs. Then theres the fairly easy to use acegi security (I use a separate site to the same database for unsecure pages out of lazyness), with an ant task to add and another to initialize (create default tables for admin, etc.) Really, I can't see why you _souldn't_ use trails for everything and then changes the bits you need to change. If you need to do heavy whiz-bang end-user pages, at least you'll have your administrative pages for free. Cheers, PS On 6/6/06, Carl Pelletier [EMAIL PROTECTED] wrote: Hi everyone, I'm looking for feedback here, I planning of using Trails to help gain speed with my Tapestry 4.0 development. Somebody use it? Should I ? What are the pinfall ? What are your advise... Thanks for your feedback
Re: Trails
Ok, thanks, that help. Last question: Is it easy to change the UI after Trails generate the page ? Because, we have some specific needs. We won't use the simple layout Trails give after the generation. We need to modify the ui to reflect our needs. Thanks ! - Original Message From: Peter Svensson [EMAIL PROTECTED] To: Tapestry users users@tapestry.apache.org; Carl Pelletier [EMAIL PROTECTED] Sent: Tuesday, June 6, 2006 10:19:46 AM Subject: Re: Trails I only use trails for my Tapestry-4 development. Mainly because I enjoyed the steep initial learning curve of tapestry and needed something to lean on. The main reason I liked and like trails is because the ant scripts together with hibernate tools generate all tables in my MySQL database automatically from my POJOs. I just need to grok how to @annotate right, which in itself have been interresting, so all lookup tables, collections, relations, etc. gets done. Another big goodie is that trails have a default list, search and edit page for all POJOs, which are plain Tapestry html/page combos. Also, there are ant/maven tasks to generate individual list or edit pages for POJOs. Then theres the fairly easy to use acegi security (I use a separate site to the same database for unsecure pages out of lazyness), with an ant task to add and another to initialize (create default tables for admin, etc.) Really, I can't see why you _souldn't_ use trails for everything and then changes the bits you need to change. If you need to do heavy whiz-bang end-user pages, at least you'll have your administrative pages for free. Cheers, PS On 6/6/06, Carl Pelletier [EMAIL PROTECTED] wrote: Hi everyone, I'm looking for feedback here, I planning of using Trails to help gain speed with my Tapestry 4.0 development. Somebody use it? Should I ? What are the pinfall ? What are your advise... Thanks for your feedback
Re: Trails
Actually, my first trails (and tapestry) project was for a customer who had an existing database with lots of odd relationships in it, and which I managed to map one class at a time, by creating classes with the same name as the tables and pasting the description into a comment. I didn't have to make it complete but just did a couple of properties at a time by trial and horror, and the pages just popped up, existing data and all. It was a way-beyond-wow moment, to be sure. Cheers, PS On 6/6/06, Kalle Korhonen [EMAIL PROTECTED] wrote: On 6/6/06, Peter Svensson [EMAIL PROTECTED] wrote: Really, I can't see why you _souldn't_ use trails for everything and then changes the bits you need to change. If you need to do heavy whiz-bang end-user pages, at least you'll have your administrative pages for free. Second that, don't see too many reasons why not to use it. If you are starting a new project from scratch (or at least without pre-existing, fixed schema), it's a no-brainer to use Trails to compliment Tapestry and eliminate/reduce the glue code you normally need to write for persistence. Kalle On 6/6/06, Carl Pelletier [EMAIL PROTECTED] wrote: Hi everyone, I'm looking for feedback here, I planning of using Trails to help gain speed with my Tapestry 4.0 development. Somebody use it? Should I ? What are the pinfall ? What are your advise... Thanks for your feedback - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
