History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: TRAILS-38
Type: Task Task
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Alejandro Scandroli
Reporter: Alejandro Scandroli
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Trails

re-modularize Trails

Created: 02/May/07 06:39 AM   Updated: 30/Sep/07 06:45 PM
Component/s: None
Affects Version/s: 1.0.0
Fix Version/s: 1.1.0

Time Tracking:
Not Specified


 Description  « Hide
In 1.0 is not easy use Trails without hibernate, or to remove a dependency or to replace the default security implementation with a custom implementation due to the high coupling level. To decouple I propose to modularize Trails as follows:
  • trails-core: the 1.0 core but without any hibernate dependency.
  • trails-hibernate: all the hibernate related code including the our Tapestry components with Hibernate dependencies.
  • trails-security: all the security and Acegi related code.
  • trails-test: includes the base classes for testing custom components and custom pages.


 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Ken in nashua - 29/May/07 02:57 PM
I guess I do not understand the need to couple

>trails-hibernate: all the hibernate related code including the our Tapestry >components with Hibernate dependencies.

Why cannot the tapestry components remain segregated in their own separate library?

Certainly they are usable in such a fashion? No?

Why are we adding on a new library?

I am trying to think about reduced confusion. If the tapestry components are packagable then they should remain segregated as such and used as such. For what personal purpose is this for and the likelihood of such usage to occur ? Commercially?

What are the advantages/disadvantages of the coupling? Or is it a hack? No offense I am just trying to get clarification.

Please advise/justify.


Alejandro Scandroli - 29/May/07 05:07 PM
I'm planning not to use hibernate, so I need a core set of components without hibernate dependencies.

Alejandro Scandroli - 05/Jun/07 10:39 AM
It's in the trunk since rev 582