[jira] Assigned: (GRFT-1) "Maven Goals" page does not exist
[ http://issues.apache.org/jira/browse/GRFT-1?page=history ] Christophe Lombart reassigned GRFT-1: - Assign To: Christophe Lombart > "Maven Goals" page does not exist > - > > Key: GRFT-1 > URL: http://issues.apache.org/jira/browse/GRFT-1 > Project: Graffito > Type: Bug > Reporter: Stephane Bailliez > Assignee: Christophe Lombart > Priority: Minor > > The link on the left menu: "maven goals" does not exist > http://incubator.apache.org/graffito/maven-goals.html is a 404 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[jira] Updated: (GRFT-4) Support other DB in the OJB Store
[ http://issues.apache.org/jira/browse/GRFT-4?page=history ] Christophe Lombart updated GRFT-4: -- Fix Version: 1.0-a1-dev > Support other DB in the OJB Store > - > > Key: GRFT-4 > URL: http://issues.apache.org/jira/browse/GRFT-4 > Project: Graffito > Type: Task > Components: OJB Store > Reporter: Christophe Lombart > Fix For: 1.0-a1-dev > > Currently all unit test are made with MySql. Need to check with other DB : > Oracle, Sybase, HSQL, Postgres, ... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[jira] Updated: (GRFT-3) Connection already closed warning
[ http://issues.apache.org/jira/browse/GRFT-3?page=history ] Christophe Lombart updated GRFT-3: -- Fix Version: 1.0-a1-dev > Connection already closed warning > - > > Key: GRFT-3 > URL: http://issues.apache.org/jira/browse/GRFT-3 > Project: Graffito > Type: Bug > Components: OJB Store > Reporter: Christophe Lombart > Fix For: 1.0-a1-dev > > There is a "connection already closed" in the unit test for > getCollectionByQuery -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[jira] Created: (GRFT-7) Use checkstyle
Use checkstyle -- Key: GRFT-7 URL: http://issues.apache.org/jira/browse/GRFT-7 Project: Graffito Type: Task Components: Project Build Versions: 1.0-a1-dev Reporter: Christophe Lombart Priority: Minor Fix For: 1.0-a1-dev When build all subproject, we have to use checkstyle Add a page in the site about the code style & naming convention -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[jira] Created: (GRFT-10) Add unit tests for the OJB store iterator
Add unit tests for the OJB store iterator - Key: GRFT-10 URL: http://issues.apache.org/jira/browse/GRFT-10 Project: Graffito Type: Task Components: OJB Store Reporter: Christophe Lombart Assigned to: Christophe Lombart Fix For: 1.0-a1-dev Unit test on OJB store iterator doesn't exist -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[jira] Created: (GRFT-9) Add a Event Handler service
Add a Event Handler service --- Key: GRFT-9 URL: http://issues.apache.org/jira/browse/GRFT-9 Project: Graffito Type: Task Components: Event Handler Reporter: Christophe Lombart Fix For: 1.0-a1-dev It should be nice to add at runtime some handlers to execute processes when something it happening in one content store like create a document, delete a folder, ... This is mainly used for process like indexing, replication, not for workflow management. I think AOP can help in this area. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[jira] Created: (GRFT-3) Connection already closed warning
Connection already closed warning - Key: GRFT-3 URL: http://issues.apache.org/jira/browse/GRFT-3 Project: Graffito Type: Bug Components: OJB Store Reporter: Christophe Lombart There is a "connection already closed" in the unit test for getCollectionByQuery -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[jira] Created: (GRFT-4) Support other DB in the OJB Store
Support other DB in the OJB Store - Key: GRFT-4 URL: http://issues.apache.org/jira/browse/GRFT-4 Project: Graffito Type: Task Components: OJB Store Reporter: Christophe Lombart Currently all unit test are made with MySql. Need to check with other DB : Oracle, Sybase, HSQL, Postgres, ... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[jira] Created: (GRFT-8) Better Transaction management in the persistence store
Better Transaction management in the persistence store -- Key: GRFT-8 URL: http://issues.apache.org/jira/browse/GRFT-8 Project: Graffito Type: Task Components: Persistence Reporter: Christophe Lombart Fix For: 1.0-a1-dev support 2 tx phase-commit across all registered stores. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[jira] Created: (GRFT-11) Some important unit tests are missing
Some important unit tests are missing - Key: GRFT-11 URL: http://issues.apache.org/jira/browse/GRFT-11 Project: Graffito Type: Task Components: Unit tests Reporter: Christophe Lombart Fix For: 1.0-a1-dev * More unit test on security - permissions * Unit Test on multiple store features like queries, multistore iterator, ... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[jira] Created: (GRFT-5) Create a new Graffito Valve for Jetspeed 2
Create a new Graffito Valve for Jetspeed 2 -- Key: GRFT-5 URL: http://issues.apache.org/jira/browse/GRFT-5 Project: Graffito Type: Task Components: Jetspeed 2 integration Versions: 1.0-a1-dev Reporter: Christophe Lombart Assigned to: Christophe Lombart Fix For: 1.0-a1-dev Creating a new valve can help to initialise the CmsRequestContext. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[jira] Created: (GRFT-6) Managing permission with the J2 components services
Managing permission with the J2 components services --- Key: GRFT-6 URL: http://issues.apache.org/jira/browse/GRFT-6 Project: Graffito Type: Task Components: Jetspeed 2 integration Reporter: Christophe Lombart Assigned to: Christophe Lombart Fix For: 1.0-a1-dev Use in the Graffito assembly script the class CmsAccessControllerImpl instead of EmptyCmsAccessControllerImpl. By this way, find grained access control will be used -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[jira] Updated: (GRFT-2) Mailing list archives are not accessible
[ http://issues.apache.org/jira/browse/GRFT-2?page=history ] Christophe Lombart updated GRFT-2: -- Fix Version: 1.0-a1-dev > Mailing list archives are not accessible > > > Key: GRFT-2 > URL: http://issues.apache.org/jira/browse/GRFT-2 > Project: Graffito > Type: Bug > Reporter: Stephane Bailliez > Priority: Minor > Fix For: 1.0-a1-dev > > http://incubator.apache.org/graffito/mail-lists.html > Looking into the archives (mbox ?) is not permitted -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[jira] Updated: (GRFT-11) Some important unit tests are missing
[ http://issues.apache.org/jira/browse/GRFT-11?page=history ] Christophe Lombart updated GRFT-11: --- Fix Version: 1.0-a1-dev > Some important unit tests are missing > - > > Key: GRFT-11 > URL: http://issues.apache.org/jira/browse/GRFT-11 > Project: Graffito > Type: Task > Components: Unit tests > Reporter: Christophe Lombart > Fix For: 1.0-a1-dev > > * More unit test on security - permissions > * Unit Test on multiple store features like queries, multistore iterator, ... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[jira] Updated: (GRFT-1) "Maven Goals" page does not exist
[ http://issues.apache.org/jira/browse/GRFT-1?page=history ] Christophe Lombart updated GRFT-1: -- Fix Version: 1.0-a1-dev > "Maven Goals" page does not exist > - > > Key: GRFT-1 > URL: http://issues.apache.org/jira/browse/GRFT-1 > Project: Graffito > Type: Bug > Reporter: Stephane Bailliez > Assignee: Christophe Lombart > Priority: Minor > Fix For: 1.0-a1-dev > > The link on the left menu: "maven goals" does not exist > http://incubator.apache.org/graffito/maven-goals.html is a 404 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[jira] Created: (GRFT-12) Don't allow some operations on the Graffito Master Store
Don't allow some operations on the Graffito Master Store - Key: GRFT-12 URL: http://issues.apache.org/jira/browse/GRFT-12 Project: Graffito Type: Bug Components: Persistence Reporter: Christophe Lombart Fix For: 1.0-a1-dev The Graffito Master Store is quite sensitive. So, it is important to limit the operations made on this store : - It can not be deleted. - It should not be possible to add another Graffito Master Store. - It can ne be updated. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[jira] Closed: (GRFT-1) "Maven Goals" page does not exist
[ http://issues.apache.org/jira/browse/GRFT-1?page=history ] Christophe Lombart closed GRFT-1: - Resolution: Fixed Now, this page is defined correctly > "Maven Goals" page does not exist > - > > Key: GRFT-1 > URL: http://issues.apache.org/jira/browse/GRFT-1 > Project: Graffito > Type: Bug > Reporter: Stephane Bailliez > Assignee: Christophe Lombart > Priority: Minor > Fix For: 1.0-a1-dev > > The link on the left menu: "maven goals" does not exist > http://incubator.apache.org/graffito/maven-goals.html is a 404 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[jira] Assigned: (GRFT-13) Specify the maven repositories needed
[ http://issues.apache.org/jira/browse/GRFT-13?page=history ] Christophe Lombart reassigned GRFT-13: -- Assign To: Christophe Lombart > Specify the maven repositories needed > - > > Key: GRFT-13 > URL: http://issues.apache.org/jira/browse/GRFT-13 > Project: Graffito > Type: Improvement > Components: Project Build > Versions: 1.0-a1-dev > Reporter: Stephane Bailliez > Assignee: Christophe Lombart > > You would probably want to specify which repositories are needed to actually > build Graffito and fetch dependencies. It took me an incredible long time to > figure out a list of remote repositories that would work and fetch: > jetspeed-persistence-2.0-a1-dev.jar > jetspeed-api-2.0-a1-dev.jar > jetspeed-security-2.0-a1-dev.jar > jetspeed-cm-2.0-a1-dev.jar > jetspeed-rdbms-2.0-a1-dev.jar > jetspeed-commons-2.0-a1-dev.jar > jta1.0.1.jar > jdbc-se2.0.jar > maven-torque-plugin-3.2.jar > ibiblio.org for instance certainly do not have them at the time of this > writing. So a default maven configuration will certainly not work without > specifying the proper repos. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[jira] Commented: (GRFT-2) Mailing list archives are not accessible
[ http://issues.apache.org/jira/browse/GRFT-2?page=comments#action_57937 ] Christophe Lombart commented on GRFT-2: --- Raphaël is going to check what is the problem with the mail archive. > Mailing list archives are not accessible > > > Key: GRFT-2 > URL: http://issues.apache.org/jira/browse/GRFT-2 > Project: Graffito > Type: Bug > Reporter: Stephane Bailliez > Priority: Minor > Fix For: 1.0-a1-dev > > http://incubator.apache.org/graffito/mail-lists.html > Looking into the archives (mbox ?) is not permitted -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[jira] Commented: (GRFT-13) Specify the maven repositories needed
[ http://issues.apache.org/jira/browse/GRFT-13?page=comments#action_57949 ] Christophe Lombart commented on GRFT-13: Can you give more info on what is wrong when build the project ? See in the project.properties, there is a reference to http://www.bluesunrise.com/maven. This server contains all necessary jars for Graffito. I tested with an empty local repo on my pc, it works correctly. > Specify the maven repositories needed > - > > Key: GRFT-13 > URL: http://issues.apache.org/jira/browse/GRFT-13 > Project: Graffito > Type: Improvement > Components: Project Build > Versions: 1.0-a1-dev > Reporter: Stephane Bailliez > Assignee: Christophe Lombart > > You would probably want to specify which repositories are needed to actually > build Graffito and fetch dependencies. It took me an incredible long time to > figure out a list of remote repositories that would work and fetch: > jetspeed-persistence-2.0-a1-dev.jar > jetspeed-api-2.0-a1-dev.jar > jetspeed-security-2.0-a1-dev.jar > jetspeed-cm-2.0-a1-dev.jar > jetspeed-rdbms-2.0-a1-dev.jar > jetspeed-commons-2.0-a1-dev.jar > jta1.0.1.jar > jdbc-se2.0.jar > maven-torque-plugin-3.2.jar > ibiblio.org for instance certainly do not have them at the time of this > writing. So a default maven configuration will certainly not work without > specifying the proper repos. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[jira] Created: (GRFT-15) Support for Fusion
Support for Fusion -- Key: GRFT-15 URL: http://issues.apache.org/jira/browse/GRFT-15 Project: Graffito Type: Improvement Reporter: Christophe Lombart Assigned to: Christophe Lombart Fix For: 1.0-a1-dev Graffito is not working correclty with Fusion. New maven goal is required to deploy into Fusion. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[jira] Created: (GRFT-16) Graffito schema is not create correctly for HSQL
Graffito schema is not create correctly for HSQL Key: GRFT-16 URL: http://issues.apache.org/jira/browse/GRFT-16 Project: Graffito Type: Bug Components: OJB Store Reporter: Christophe Lombart Assigned to: Christophe Lombart Fix For: 1.0-a1-dev The maven goal "db.scripts.gen" doesn't create correctly the sql scripts for HSQL. The type "OBJECT" is not used for binary columns. The problem seems to come from Torque. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[jira] Assigned: (GRFT-17) messages.properties for Japanese
[ http://issues.apache.org/jira/browse/GRFT-17?page=history ] Christophe Lombart reassigned GRFT-17: -- Assign To: Christophe Lombart > messages.properties for Japanese > > > Key: GRFT-17 > URL: http://issues.apache.org/jira/browse/GRFT-17 > Project: Graffito > Type: Improvement > Environment: Linux > J2SE 1.4.2_07 > Reporter: Shinsuke SUGAYA > Assignee: Christophe Lombart > Fix For: 1.0-a1-dev > Attachments: messages_ja.properties > > Please add Japanese messages_ja.properties -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[jira] Resolved: (GRFT-17) messages.properties for Japanese
[ http://issues.apache.org/jira/browse/GRFT-17?page=history ] Christophe Lombart resolved GRFT-17: Resolution: Fixed Fix Version: 1.0-a1-dev Added into the svn repo. This files has be reviewed later because new messages are going to be added (sorry). > messages.properties for Japanese > > > Key: GRFT-17 > URL: http://issues.apache.org/jira/browse/GRFT-17 > Project: Graffito > Type: Improvement > Environment: Linux > J2SE 1.4.2_07 > Reporter: Shinsuke SUGAYA > Assignee: Christophe Lombart > Fix For: 1.0-a1-dev > Attachments: messages_ja.properties > > Please add Japanese messages_ja.properties -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[jira] Closed: (GRFT-6) Managing permission with the J2 components services
[ http://issues.apache.org/jira/browse/GRFT-6?page=history ] Christophe Lombart closed GRFT-6: - Resolution: Fixed Done. A Graffito valve has been developed for J2 > Managing permission with the J2 components services > --- > > Key: GRFT-6 > URL: http://issues.apache.org/jira/browse/GRFT-6 > Project: Graffito > Type: Task > Components: Jetspeed 2 integration > Reporter: Christophe Lombart > Assignee: Christophe Lombart > Fix For: 1.0-a1-dev > > Use in the Graffito assembly script the class CmsAccessControllerImpl instead > of EmptyCmsAccessControllerImpl. By this way, find grained access control > will be used -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[jira] Closed: (GRFT-5) Create a new Graffito Valve for Jetspeed 2
[ http://issues.apache.org/jira/browse/GRFT-5?page=history ] Christophe Lombart closed GRFT-5: - Resolution: Fixed Done > Create a new Graffito Valve for Jetspeed 2 > -- > > Key: GRFT-5 > URL: http://issues.apache.org/jira/browse/GRFT-5 > Project: Graffito > Type: Task > Components: Jetspeed 2 integration > Versions: 1.0-a1-dev > Reporter: Christophe Lombart > Assignee: Christophe Lombart > Fix For: 1.0-a1-dev > > Creating a new valve can help to initialise the CmsRequestContext. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[jira] Closed: (GRFT-14) Classloader issue when deploying graffito the first time
[ http://issues.apache.org/jira/browse/GRFT-14?page=history ] Christophe Lombart closed GRFT-14: -- Resolution: Fixed Fix Version: 1.0-a1-dev This problem is fixed with the J2 M2 or M3 > Classloader issue when deploying graffito the first time > > > Key: GRFT-14 > URL: http://issues.apache.org/jira/browse/GRFT-14 > Project: Graffito > Type: Bug > Components: Jetspeed 2 integration > Environment: Tomcat 5.0.28 > Reporter: DerShung Yang > Priority: Minor > Fix For: 1.0-a1-dev > > I did an allClean,allBuild,allDeploy build and then launched Tomcat (Jetspeed > 2 was already built and deployed). I logged in as admin and then clicked on > the Graffito tab. The following exception occured. After I shutdown and > re-launched Tomcat the second time, the problem went away. > VelocityViewServlet : Error processing the template > Invocation of method 'getTitle' in class > org.apache.jetspeed.velocity.JetspeedPowerTool threw exception class > java.lang.IllegalStateException : No classloader has been defined for portlet > application 1 > java.lang.IllegalStateException: No classloader has been defined for portlet > application 1 > at > org.apache.jetspeed.factory.JetspeedPortletFactory.getPortletClassLoader(JetspeedPortletFactory.java:216) > at > org.apache.jetspeed.request.JetspeedRequestContext.getPreferedLanguage(JetspeedRequestContext.java:497) > at > org.apache.jetspeed.velocity.JetspeedPowerTool.getTitle(JetspeedPowerTool.java:993) > at > org.apache.jetspeed.velocity.JetspeedPowerTool.getTitle(JetspeedPowerTool.java:972) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:324) > at > org.apache.velocity.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:267) > at > org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:197) > at > org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:175) > at > org.apache.velocity.runtime.parser.node.ASTReference.render(ASTReference.java:220) > at > org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:230) > at org.apache.velocity.runtime.directive.Parse.render(Parse.java:181) > at > org.apache.velocity.runtime.parser.node.ASTDirective.render(ASTDirective.java:114) > at > org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:55) > at > org.apache.velocity.runtime.parser.node.ASTIfStatement.render(ASTIfStatement.java:70) > at > org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:55) > at > org.apache.velocity.runtime.directive.Foreach.render(Foreach.java:166) > at > org.apache.velocity.runtime.parser.node.ASTDirective.render(ASTDirective.java:114) > at > org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:55) > at > org.apache.velocity.runtime.directive.Foreach.render(Foreach.java:166) > at > org.apache.velocity.runtime.parser.node.ASTDirective.render(ASTDirective.java:114) > at > org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:230) > at org.apache.velocity.Template.merge(Template.java:256) > at > org.apache.portals.bridges.velocity.BridgesVelocityViewServlet.mergeTemplate(BridgesVelocityViewServlet.java:118) > at > org.apache.velocity.tools.view.servlet.VelocityViewServlet.doRequest(Unknown > Source) > at > org.apache.velocity.tools.view.servlet.VelocityViewServlet.doGet(Unknown > Source) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:689) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157) > at > org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:704) > at > org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:590) > at > org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:510) > at > org.apache.jetspeed.dispatcher.JetspeedRequestDispatcher.include(JetspeedRequestDispatcher.java:65) > at > org.apache.portals.bridges.common.GenericServletPortlet.doView(GenericServletPortlet.java:363) > at > org.apache.jetspeed.portlets.layout.LayoutPortlet.doView(LayoutPortlet.java:134) > at > org.apache.jetspeed.portlets.layout.MultiColumnPortlet.doVie
[jira] Assigned: (GRFT-18) Proof of concept for mapping Java beans to JCR nodetypes
[ http://issues.apache.org/jira/browse/GRFT-18?page=history ] Christophe Lombart reassigned GRFT-18: -- Assign To: Christophe Lombart > Proof of concept for mapping Java beans to JCR nodetypes > > > Key: GRFT-18 > URL: http://issues.apache.org/jira/browse/GRFT-18 > Project: Graffito > Type: New Feature > Components: JCR-Mapping > Reporter: Sandro Boehme > Assignee: Christophe Lombart > Attachments: GraffitoJcrMappingTest.zip > > Hello, > attached there are (hopefully all) the files for a proof of concept > of three usecases for the JCR Mapping(I could not sent it to the mailing list > because it does not allow attachments): > 1. Registering custom nodetypes according to a Java Bean model. > 2. Persist a Java Bean. > 3. Loading a Java Bean from the repository. > ==>1. Creating the custom nodetypes is realized with JAXB. The > BeanConverter class maps the Java structure to the > nodetype structure and marshalls the custom_nodetypes.xml to the > configured nodetype folder. I attached the /lib folder > with the jaxb libraries, a XML schema and the command line call (in the > generateNodeTypeDTD.bat file) if somebody want > to generate a new custom_nodetypes.xml file. I did not check the schema > against the spec yet, because it will change anyway. > Once the definition of the custom_nodetypes.xml file is stable, I would > like to create an Ant target and a seperate library > for generating custom nodetypes out of Java Beans. > ==>2. Persisting simply works like that: > PersistenceManager pm = new PersistenceManager(session); > String relPath = pm.insert(folder); > ==>3. Loading can be implemented this way: > Folder loadedFolder = (Folder) pm.getObject(relPath); > All information for reading and writing a bean can be gained by the > class itself except the path where the > object is stored in the repository. This path acts like a unambiguous > database id. > ++ limitations ++ > o no complex properties can be saved (Folder.getDocument()) > o collections are not yet supported > o deletion is not yet supported > o only the basic JCR Types (String, boolean,...) and java.util.Date are > supported > o the bean converter is not yet adapted to Graffito converter handling > o mixin's/Interfaces are not yet supported > ++ next steps ++ > o much more test cases need to be added and I'm sure according bug's > need to be fixed ;-) > o also delete the data created in the test cases > o pm.update and pm.delete() need to be added > o more atomic types (like Character,...) need to be added > o support for complex types > o support for collections > o support for interfaces > o make the namespace "graffito" configurable > o support for JCR features like searching, versioning,... > o creating an Ant target for registering Java classes as nodetypes > o refactor some responsibilties and names of some classes > o ... > ++ configuration ++ > I don't think it is ready for check in because the configuration is not > very clean at the > moment. I needed to delete the repository data (repotest/versions and > repotest/workspaces/default) > in order to get the tests to run. I've not very much experience with > maven. Your information for this > issue are very much appreciated. > Regards, > Sandro -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[jira] Created: (GRFT-25) PROPOSAL : New Graffito Object Model
PROPOSAL : New Graffito Object Model Key: GRFT-25 URL: http://issues.apache.org/jira/browse/GRFT-25 Project: Graffito Type: Improvement Components: Model Versions: 1.0-a1-dev Reporter: Christophe Lombart Assigned to: Christophe Lombart Fix For: 1.0-a1-dev Attachments: graffito-model.png Introduction This document describes a proposal for a new Graffito Object Model. In my point of view, the model has the following weaknesses : 1. The CmsObject interface contains too many attributes. Title, description and owner should be not mandatory. Futhermore, this interface contains getObjects() and getProperties() which could be duplicate attributes. 2. The Document interface forces to have a binary content. Binary content is only interesting for Document management & asset management. We can expect to use Graffito for a CMS application containing only articles. In a such case, an article can be composed only of a set of String : title, summary, content, authors, ... and not binary content. 3. The Content interface is not an appropriate name. DocumentStream seems to be more explicit. 4. We need to have a better internationalisation support. 5. It is difficult to extend the model. The New Object Model The proposed model is splitted into different modules (see in attachement the UML class diagram) : * The Graffito code module. * A series of optional modules. 1. The Graffito Core Module --- This module contains all ancestor objects like CmsObject, Folder, Content. Content is the ancestor of any kind of content object (Document, topic, article, ...). Versionning is not mandatory is all case. The "VersionnedContent" is the ancestor used in a version management context. As you can see, only content can be versionned. Later, we can support versionning on Folders. 2. Optional modules --- Depending on the application requirements, the Graffito users can select one or more optional modules. If the Graffito model doesn't fit to the application requirements, it should be possible to plug a customized module. One subproject per module has to be defined in the Graffito project. 2.1 Document Management module -- This module manage any kind of binary documents (Ms Word, pdf, ...). By default, this DM module is supporting internationalisation. In order to increase the performance, the DocumentStream should be defined as a proxy. All documents are versionned. 2.2 Article Management module - This module can manage translated articles or single language articles. All articles are versionned. 2.3. Forum -- This module is a simple object model that can be used for a Forum application. Obviously, topic (the forum content) are not versionned. 2.4. Other modules -- Now, it should be easy to extend the Core Graffito module or any other optional modules. For example, someone can add a news management, asset management or customize the article module. 3.Open points -- * Review the project structure in order to support modules. * CmsObject interface : getProperties, getObjects() : David, are you using both attributes ? * Internationalisation : providing by default in the different module or not ? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GRFT-25) PROPOSAL : New Graffito Object Model
[ http://issues.apache.org/jira/browse/GRFT-25?page=all ] Christophe Lombart updated GRFT-25: --- Attachment: graffito-model.png Add the UML Class Diagram > PROPOSAL : New Graffito Object Model > > > Key: GRFT-25 > URL: http://issues.apache.org/jira/browse/GRFT-25 > Project: Graffito > Type: Improvement > Components: Model > Versions: 1.0-a1-dev > Reporter: Christophe Lombart > Assignee: Christophe Lombart > Fix For: 1.0-a1-dev > Attachments: graffito-model.png > > Introduction > > This document describes a proposal for a new Graffito Object Model. > In my point of view, the model has the following weaknesses : > 1. The CmsObject interface contains too many attributes. Title, description > and owner should be not mandatory. Futhermore, this interface contains > getObjects() and getProperties() which could be duplicate attributes. > 2. The Document interface forces to have a binary content. Binary content is > only interesting for Document management & asset management. We can expect to > use Graffito for a CMS application containing only articles. In a such case, > an article can be composed only of a set of String : title, summary, content, > authors, ... and not binary content. > 3. The Content interface is not an appropriate name. DocumentStream seems to > be more explicit. > 4. We need to have a better internationalisation support. > 5. It is difficult to extend the model. > The New Object Model > > The proposed model is splitted into different modules (see in attachement the > UML class diagram) : > * The Graffito code module. > * A series of optional modules. > 1. The Graffito Core Module > --- > This module contains all ancestor objects like CmsObject, Folder, Content. > Content is the ancestor of any kind of content object (Document, topic, > article, ...). Versionning is not mandatory is all case. The > "VersionnedContent" is the ancestor used in a version management context. As > you can see, only content can be versionned. Later, we can support > versionning on Folders. > 2. Optional modules > --- > Depending on the application requirements, the Graffito users can select one > or more optional modules. If the Graffito model doesn't fit to the > application requirements, it should be possible to plug a customized module. > One subproject per module has to be defined in the Graffito project. > 2.1 Document Management module > -- > This module manage any kind of binary documents (Ms Word, pdf, ...). By > default, this DM module is supporting internationalisation. In order to > increase the performance, the DocumentStream should be defined as a proxy. > All documents are versionned. > 2.2 Article Management module > - > This module can manage translated articles or single language articles. All > articles are versionned. > 2.3. Forum > -- > This module is a simple object model that can be used for a Forum > application. Obviously, topic (the forum content) are not versionned. > 2.4. Other modules > -- > Now, it should be easy to extend the Core Graffito module or any other > optional modules. For example, someone can add a news management, asset > management or customize the article module. > > 3.Open points > -- > * Review the project structure in order to support modules. > * CmsObject interface : getProperties, getObjects() : David, are you using > both attributes ? > * Internationalisation : providing by default in the different module or not > ? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GRFT-26) Review project structure
Review project structure Key: GRFT-26 URL: http://issues.apache.org/jira/browse/GRFT-26 Project: Graffito Type: Improvement Versions: 1.0-a1-dev Reporter: Christophe Lombart Assigned to: Christophe Lombart Fix For: 1.0-a1-dev Review the project structure in order to support Graffito extension (modules). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GRFT-25) PROPOSAL : New Graffito Object Model
[ http://issues.apache.org/jira/browse/GRFT-25?page=comments#action_66827 ] Christophe Lombart commented on GRFT-25: Comments for comments :-) I use getProperties only. When you say title, description, and owner should not be mandatory, are you saying to move them to properties? Yes, I propose to move them to the new Document interface (description & title). For me, owner is too specific. I can imagine to build a DM application without the need of this attributes. I would like to make another proposal on how to extend the Grafitto model and organise the project on severals modules. I'm going to post something today. 5. It is difficult to extend the model. well it requires writing Java code, but it hasnt been that difficult from the Java POV correct and we can write a maven pluging used to initialise a new Graffito module ? In fact, a module can be used by an Graffito user in order to extend the Graffito model, add services or customise a core module. > PROPOSAL : New Graffito Object Model > > > Key: GRFT-25 > URL: http://issues.apache.org/jira/browse/GRFT-25 > Project: Graffito > Type: Improvement > Components: Model > Versions: 1.0-a1-dev > Reporter: Christophe Lombart > Assignee: Christophe Lombart > Fix For: 1.0-a1-dev > Attachments: graffito-model.png > > Introduction > > This document describes a proposal for a new Graffito Object Model. > In my point of view, the model has the following weaknesses : > 1. The CmsObject interface contains too many attributes. Title, description > and owner should be not mandatory. Futhermore, this interface contains > getObjects() and getProperties() which could be duplicate attributes. > 2. The Document interface forces to have a binary content. Binary content is > only interesting for Document management & asset management. We can expect to > use Graffito for a CMS application containing only articles. In a such case, > an article can be composed only of a set of String : title, summary, content, > authors, ... and not binary content. > 3. The Content interface is not an appropriate name. DocumentStream seems to > be more explicit. > 4. We need to have a better internationalisation support. > 5. It is difficult to extend the model. > The New Object Model > > The proposed model is splitted into different modules (see in attachement the > UML class diagram) : > * The Graffito code module. > * A series of optional modules. > 1. The Graffito Core Module > --- > This module contains all ancestor objects like CmsObject, Folder, Content. > Content is the ancestor of any kind of content object (Document, topic, > article, ...). Versionning is not mandatory is all case. The > "VersionnedContent" is the ancestor used in a version management context. As > you can see, only content can be versionned. Later, we can support > versionning on Folders. > 2. Optional modules > --- > Depending on the application requirements, the Graffito users can select one > or more optional modules. If the Graffito model doesn't fit to the > application requirements, it should be possible to plug a customized module. > One subproject per module has to be defined in the Graffito project. > 2.1 Document Management module > -- > This module manage any kind of binary documents (Ms Word, pdf, ...). By > default, this DM module is supporting internationalisation. In order to > increase the performance, the DocumentStream should be defined as a proxy. > All documents are versionned. > 2.2 Article Management module > - > This module can manage translated articles or single language articles. All > articles are versionned. > 2.3. Forum > -- > This module is a simple object model that can be used for a Forum > application. Obviously, topic (the forum content) are not versionned. > 2.4. Other modules > -- > Now, it should be easy to extend the Core Graffito module or any other > optional modules. For example, someone can add a news management, asset > management or customize the article module. > > 3.Open points > -- > * Review the project structure in order to support modules. > * CmsObject interface : getProperties, getObjects() : David, are you using > both attributes ? > * Internationalisation : providing by default in the different module or not > ? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GRFT-27) PROPOSAL : Graffito Modules
PROPOSAL : Graffito Modules --- Key: GRFT-27 URL: http://issues.apache.org/jira/browse/GRFT-27 Project: Graffito Type: New Feature Versions: 1.0-a1-dev Reporter: Christophe Lombart Assigned to: Christophe Lombart Fix For: 1.0-a1-dev I would like to add the Graffito module concept in the project. This can help to add new extersions into Graffito and gives some facilities to contribute to the Graffito project. This is also a great help to customize the Graffito services. What is a Graffito module ? --- A module is composed of some java codes, resources and deployment scripts. It is mainly used to add more features in Graffito. Eg. we can plan to add modules for document management, asset management, scheduler application, forum, news management, ... The Graffito core object model & services are the foundation for all Graffito modules. It should be also possible to customise a existing module. The deployment artifact is composed only of a set of jars and one assembly script. New project structure - We have to review the project structure in order to support the Graffito modules. A proposal will be made in another Jira issue. Graffito Maven plugin - I'm not the Maven expert but we can imagine to build a plugin used for the module management. We can start with simple maven goals like initialise a subproject module with some default deployment scripts, replace a deployed module, Issues -- The more important issue for building new module is the modification of the DB schema (content repository structure). This issue is quite limited if we are using JCR by default. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GRFT-26) Review project structure
[ http://issues.apache.org/jira/browse/GRFT-26?page=comments#action_66915 ] Christophe Lombart commented on GRFT-26: In order to support the Graffito modules, a new subproject "modules" is required. Here is the proposed project structure : trunk/api (Graffito core api : interfaces, services, exception) trunk/components (Graffito core components & services implementation) trunk/commons (utility classes used in different subprojects) trunk/doc : tempory doc/draft/discussion trunk/site : official information on Graffito used to build the internet site. trunk/engine : Utility classes used to integrate Graffito in any kind of J2EE application (not necessary for Jetspeed 2). trunk/jcr-mapping : object mapping tools for JCR. trunk/jetspeed2-deploy : scripts & resources used to deploy the Graffito core services into Jetspeed 2. trunk/modules : Graffito extensions trunk/modules/dm (Document management module) trunk/modules/dm/api (module api) trunk/modules/dm/components (module components et services) trunk/modules/dm/jetspeed2-deploy (scripts to deploy the module into J2) project.properties maven.xml project.xml trunk/modules/news (News management module) trunk/modules/news/api (module api) trunk/modules/news/components (module components et services) trunk/modules/news/jetspeed2-deploy (scripts to deploy the module into J2) project.properties maven.xml project.xml ... other modules (forum, article management, ...) trunk/application (war portlets) trunk/application/browser (admin browser portlets) trunk/application/graffito-portlets (common graffito portlets) * Doc Viewer portlet * Treeview portlet * Search portlet ... trunk/application/framework-portlets (declarative page & tab page, Graffito tools, utility classes, portlet flow...) other portlets apps > Review project structure > > > Key: GRFT-26 > URL: http://issues.apache.org/jira/browse/GRFT-26 > Project: Graffito > Type: Improvement > Versions: 1.0-a1-dev > Reporter: Christophe Lombart > Assignee: Christophe Lombart > Fix For: 1.0-a1-dev > > Review the project structure in order to support Graffito extension > (modules). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GRFT-28) Add support for cmsObject.properties
Add support for cmsObject.properties Key: GRFT-28 URL: http://issues.apache.org/jira/browse/GRFT-28 Project: Graffito Type: Improvement Components: Model, OJB Store, Portlets Versions: 1.0-a1-dev Reporter: Christophe Lombart Fix For: 1.0-a1-dev Add support for CmsObject.properties in : * The Graffito db schema * Services * Browser portlet -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (GRFT-29) Build failure with HSQLDB
[ http://issues.apache.org/jira/browse/GRFT-29?page=all ]
Christophe Lombart reassigned GRFT-29:
--
Assign To: Christophe Lombart
> Build failure with HSQLDB
> -
>
> Key: GRFT-29
> URL: http://issues.apache.org/jira/browse/GRFT-29
> Project: Graffito
> Type: Bug
> Components: Project Build
> Versions: 1.0-a1-dev
> Environment: HSQLDB, JDK 1.4.2, Maven 1.0.2
> Reporter: Martin Maisey
> Assignee: Christophe Lombart
>
> I attempted to build Maven as per
> http://incubator.apache.org/graffito/getting-started.html, and used HSQLDB as
> a quick and easy option that the getting started instructions say is
> supported. So I have
> org.apache.portals.graffito.test.database.default.name=hsql
> in my build.properties.
> However, the build fails with
> BUILD FAILED
> File.. C:\cygwin\home\martin.maisey\graffito\maven.xml
> Element... maven:reactor
> Line.. 77
> Column 40
> Unable to obtain goal [test:test] --
> C:\cygwin\home\martin.maisey\graffito\components\maven.xml:97:33:
> Source file does not exist!
> The problem appears to be that the file referenced in the database.arg.script
> parameter set at line 267 in the maven.xml file mentioned does not exist.
> This is defined as
> ./src/sql/GraffitoServer/${org.apache.portals.graffito.database.default.name}/drop-db.sql
> Looking at Subversion, this appears to be a manually created file, and there
> is no file src/sql/GraffitoServer/hsql/drop-db.sql in Subversion hence the
> error. In fact, the only database these files are present for is MySQL. I'm
> moving to MySQL now as a workaround, but raising the issue as it might be a
> good idea to either
> * Update the 'Getting Started' page to indicate that the other databases
> aren't currently supported, or
> * Check in the relevant SQL files
> This may be related to GRFT-4 but really is related to the Getting Started
> page, which seems to be a bit misleading at the moment.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (GRFT-29) Build failure with HSQLDB
[
http://issues.apache.org/jira/browse/GRFT-29?page=comments#action_12313053 ]
Christophe Lombart commented on GRFT-29:
Some pieces of code & config files are missing if we want to support HSQL DB.
I'm working on that. It should be solve this week.
Now, config files are defined.
I'm reviewing the unit tests and deployment on J2.
> Build failure with HSQLDB
> -
>
> Key: GRFT-29
> URL: http://issues.apache.org/jira/browse/GRFT-29
> Project: Graffito
> Type: Bug
> Components: Project Build
> Versions: 1.0-a1-dev
> Environment: HSQLDB, JDK 1.4.2, Maven 1.0.2
> Reporter: Martin Maisey
> Assignee: Christophe Lombart
>
> I attempted to build Maven as per
> http://incubator.apache.org/graffito/getting-started.html, and used HSQLDB as
> a quick and easy option that the getting started instructions say is
> supported. So I have
> org.apache.portals.graffito.test.database.default.name=hsql
> in my build.properties.
> However, the build fails with
> BUILD FAILED
> File.. C:\cygwin\home\martin.maisey\graffito\maven.xml
> Element... maven:reactor
> Line.. 77
> Column 40
> Unable to obtain goal [test:test] --
> C:\cygwin\home\martin.maisey\graffito\components\maven.xml:97:33:
> Source file does not exist!
> The problem appears to be that the file referenced in the database.arg.script
> parameter set at line 267 in the maven.xml file mentioned does not exist.
> This is defined as
> ./src/sql/GraffitoServer/${org.apache.portals.graffito.database.default.name}/drop-db.sql
> Looking at Subversion, this appears to be a manually created file, and there
> is no file src/sql/GraffitoServer/hsql/drop-db.sql in Subversion hence the
> error. In fact, the only database these files are present for is MySQL. I'm
> moving to MySQL now as a workaround, but raising the issue as it might be a
> good idea to either
> * Update the 'Getting Started' page to indicate that the other databases
> aren't currently supported, or
> * Check in the relevant SQL files
> This may be related to GRFT-4 but really is related to the Getting Started
> page, which seems to be a bit misleading at the moment.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Closed: (GRFT-29) Build failure with HSQLDB
[ http://issues.apache.org/jira/browse/GRFT-29?page=all ]
Christophe Lombart closed GRFT-29:
--
Resolution: Fixed
Linked to issues GRFT-16.
* All HSQL specific scripts has been added.
* Running Graffito with HSQL required HSQL version 1.8
> Build failure with HSQLDB
> -
>
> Key: GRFT-29
> URL: http://issues.apache.org/jira/browse/GRFT-29
> Project: Graffito
> Type: Bug
> Components: Project Build
> Versions: 1.0-a1-dev
> Environment: HSQLDB, JDK 1.4.2, Maven 1.0.2
> Reporter: Martin Maisey
> Assignee: Christophe Lombart
>
> I attempted to build Maven as per
> http://incubator.apache.org/graffito/getting-started.html, and used HSQLDB as
> a quick and easy option that the getting started instructions say is
> supported. So I have
> org.apache.portals.graffito.test.database.default.name=hsql
> in my build.properties.
> However, the build fails with
> BUILD FAILED
> File.. C:\cygwin\home\martin.maisey\graffito\maven.xml
> Element... maven:reactor
> Line.. 77
> Column 40
> Unable to obtain goal [test:test] --
> C:\cygwin\home\martin.maisey\graffito\components\maven.xml:97:33:
> Source file does not exist!
> The problem appears to be that the file referenced in the database.arg.script
> parameter set at line 267 in the maven.xml file mentioned does not exist.
> This is defined as
> ./src/sql/GraffitoServer/${org.apache.portals.graffito.database.default.name}/drop-db.sql
> Looking at Subversion, this appears to be a manually created file, and there
> is no file src/sql/GraffitoServer/hsql/drop-db.sql in Subversion hence the
> error. In fact, the only database these files are present for is MySQL. I'm
> moving to MySQL now as a workaround, but raising the issue as it might be a
> good idea to either
> * Update the 'Getting Started' page to indicate that the other databases
> aren't currently supported, or
> * Check in the relevant SQL files
> This may be related to GRFT-4 but really is related to the Getting Started
> page, which seems to be a bit misleading at the moment.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Closed: (GRFT-16) Graffito schema is not create correctly for HSQL
[ http://issues.apache.org/jira/browse/GRFT-16?page=all ] Christophe Lombart closed GRFT-16: -- Resolution: Fixed Patch Apply. Running with HSQL 1.7.n doens't work. It requires HSQL 1.8 > Graffito schema is not create correctly for HSQL > > > Key: GRFT-16 > URL: http://issues.apache.org/jira/browse/GRFT-16 > Project: Graffito > Type: Bug > Components: OJB Store > Reporter: Christophe Lombart > Assignee: Christophe Lombart > Fix For: 1.0-a1-dev > Attachments: graffito_for_hsql.tar.gz > > The maven goal "db.scripts.gen" doesn't create correctly the sql scripts for > HSQL. The type "OBJECT" is not used for binary columns. The problem seems to > come from Torque. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (GRFT-25) PROPOSAL : New Graffito Object Model
[ http://issues.apache.org/jira/browse/GRFT-25?page=all ] Christophe Lombart closed GRFT-25: -- Resolution: Fixed The object model has been reviewed. I'm going to add the class diagram on the Graffito site. > PROPOSAL : New Graffito Object Model > > > Key: GRFT-25 > URL: http://issues.apache.org/jira/browse/GRFT-25 > Project: Graffito > Type: Improvement > Components: Model > Versions: 1.0-a1-dev > Reporter: Christophe Lombart > Assignee: Christophe Lombart > Fix For: 1.0-a1-dev > Attachments: graffito-model.png > > Introduction > > This document describes a proposal for a new Graffito Object Model. > In my point of view, the model has the following weaknesses : > 1. The CmsObject interface contains too many attributes. Title, description > and owner should be not mandatory. Futhermore, this interface contains > getObjects() and getProperties() which could be duplicate attributes. > 2. The Document interface forces to have a binary content. Binary content is > only interesting for Document management & asset management. We can expect to > use Graffito for a CMS application containing only articles. In a such case, > an article can be composed only of a set of String : title, summary, content, > authors, ... and not binary content. > 3. The Content interface is not an appropriate name. DocumentStream seems to > be more explicit. > 4. We need to have a better internationalisation support. > 5. It is difficult to extend the model. > The New Object Model > > The proposed model is splitted into different modules (see in attachement the > UML class diagram) : > * The Graffito code module. > * A series of optional modules. > 1. The Graffito Core Module > --- > This module contains all ancestor objects like CmsObject, Folder, Content. > Content is the ancestor of any kind of content object (Document, topic, > article, ...). Versionning is not mandatory is all case. The > "VersionnedContent" is the ancestor used in a version management context. As > you can see, only content can be versionned. Later, we can support > versionning on Folders. > 2. Optional modules > --- > Depending on the application requirements, the Graffito users can select one > or more optional modules. If the Graffito model doesn't fit to the > application requirements, it should be possible to plug a customized module. > One subproject per module has to be defined in the Graffito project. > 2.1 Document Management module > -- > This module manage any kind of binary documents (Ms Word, pdf, ...). By > default, this DM module is supporting internationalisation. In order to > increase the performance, the DocumentStream should be defined as a proxy. > All documents are versionned. > 2.2 Article Management module > - > This module can manage translated articles or single language articles. All > articles are versionned. > 2.3. Forum > -- > This module is a simple object model that can be used for a Forum > application. Obviously, topic (the forum content) are not versionned. > 2.4. Other modules > -- > Now, it should be easy to extend the Core Graffito module or any other > optional modules. For example, someone can add a news management, asset > management or customize the article module. > > 3.Open points > -- > * Review the project structure in order to support modules. > * CmsObject interface : getProperties, getObjects() : David, are you using > both attributes ? > * Internationalisation : providing by default in the different module or not > ? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GRFT-35) Review Localization
Review Localization --- Key: GRFT-35 URL: http://issues.apache.org/jira/browse/GRFT-35 Project: Graffito Type: Improvement Components: Model, Portlets Versions: 1.0-a1-dev Reporter: Christophe Lombart Assigned to: Christophe Lombart Fix For: 1.0-a1-dev Better support for localization : 1. Review translated messages in the portlets. 2. Review the object model in order to support multi language properties : The CmsObject has a collection of property. I propose to add a local attribute in the interface "Property" which can be null for properties which are not local dependant. 3. Review the portlets in order to manage CMS object properties. A new tab page can manage the CmsObject properties and their translations. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GRFT-35) Review Localization
[ http://issues.apache.org/jira/browse/GRFT-35?page=all ] Christophe Lombart updated GRFT-35: --- Description: Better support for localization : 1. Review translated messages in the portlets. 2. Review the object model in order to support multi language properties : The CmsObject has a collection of properties (see the new object model). I propose to add a local attribute in the class "PropertyImpl" which can be null for properties which are not local dependant. 3. Review the portlets in order to manage CMS object properties. A new tab page can manage the CmsObject properties and their translations. The Browser portlet view mode has to check the request local. was: Better support for localization : 1. Review translated messages in the portlets. 2. Review the object model in order to support multi language properties : The CmsObject has a collection of property. I propose to add a local attribute in the interface "Property" which can be null for properties which are not local dependant. 3. Review the portlets in order to manage CMS object properties. A new tab page can manage the CmsObject properties and their translations. > Review Localization > --- > > Key: GRFT-35 > URL: http://issues.apache.org/jira/browse/GRFT-35 > Project: Graffito > Type: Improvement > Components: Model, Portlets > Versions: 1.0-a1-dev > Reporter: Christophe Lombart > Assignee: Christophe Lombart > Fix For: 1.0-a1-dev > > Better support for localization : > 1. Review translated messages in the portlets. > 2. Review the object model in order to support multi language properties : > The CmsObject has a collection of properties (see the new object model). I > propose to add a local attribute in the class "PropertyImpl" which can be > null for properties which are not local dependant. > 3. Review the portlets in order to manage CMS object properties. A new tab > page can manage the CmsObject properties and their translations. The Browser > portlet view mode has to check the request local. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GRFT-36) Issues with PostgreSQL
Issues with PostgreSQL -- Key: GRFT-36 URL: http://issues.apache.org/jira/browse/GRFT-36 Project: Graffito Type: Bug Components: OJB Store Versions: 1.0-a1-dev Reporter: Christophe Lombart Fix For: 1.0-a1-dev Hi, I'm trying Graffito on PostgreSQL - it works, I found only two problems: 1) graffito-schema.xml contains: but after generating SQL create script generated graffito-schema.sql contains: CREATE TABLE DOCUMENT_STREAM ( DOCUMENT_STREAM_ID integer NOT NULL, -->> CONTENT, <<-- datatype is missing, it has to be 'bytea' ISO_CODE varchar (5), ENCODING varchar (30), PRIMARY KEY (DOCUMENT_STREAM_ID) ); maybe Torque/Maven plugin issue? 2) Column ISO_CODE is defined twice in graffito-schema.xml - for table DOCUMENT_STREAM and for table CMS_OBJECT. But repository.xml contains no mapping for ISO_CODE on CMS_OBJECT. I think ISO_CODE should be defined only for DOCUMENT_STREAM because neither CmsObject.class nor it's children havent property 'isoCode', only DocumentStream.class has such property. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GRFT-37) Final JCR Mapping Document PROPOSAL
Final JCR Mapping Document PROPOSAL --- Key: GRFT-37 URL: http://issues.apache.org/jira/browse/GRFT-37 Project: Graffito Type: Task Components: Documentation Versions: 1.0-a1-dev Reporter: Christophe Lombart Fix For: 1.0-a1-dev I would like to write a document which can group the different ideas in order to have only one final proposal for : * The subproject goals * the component structures (I added in this doc the Sandro proposal) and API. * The mapping file structure. * ... Feel free the modify the document in attachement and add it the new version in this issue. This is not a simple project, so a working doc like this should help us to work on the same foundations. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GRFT-37) Final JCR Mapping Document PROPOSAL
[ http://issues.apache.org/jira/browse/GRFT-37?page=all ] Christophe Lombart updated GRFT-37: --- Attachment: jcr-mapping proposal.txt > Final JCR Mapping Document PROPOSAL > --- > > Key: GRFT-37 > URL: http://issues.apache.org/jira/browse/GRFT-37 > Project: Graffito > Type: Task > Components: Documentation > Versions: 1.0-a1-dev > Reporter: Christophe Lombart > Fix For: 1.0-a1-dev > Attachments: jcr-mapping proposal.txt > > I would like to write a document which can group the different ideas in order > to have only one final proposal for : > * The subproject goals > * the component structures (I added in this doc the Sandro proposal) and API. > * The mapping file structure. > * ... > Feel free the modify the document in attachement and add it the new version > in this issue. This is not a simple project, so a working doc like this > should help us to work on the same foundations. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (GRFT-37) Final JCR Mapping Document PROPOSAL
[ http://issues.apache.org/jira/browse/GRFT-37?page=all ] Christophe Lombart reassigned GRFT-37: -- Assign To: Christophe Lombart > Final JCR Mapping Document PROPOSAL > --- > > Key: GRFT-37 > URL: http://issues.apache.org/jira/browse/GRFT-37 > Project: Graffito > Type: Task > Components: Documentation > Versions: 1.0-a1-dev > Reporter: Christophe Lombart > Assignee: Christophe Lombart > Fix For: 1.0-a1-dev > Attachments: jcr-mapping proposal.txt > > I would like to write a document which can group the different ideas in order > to have only one final proposal for : > * The subproject goals > * the component structures (I added in this doc the Sandro proposal) and API. > * The mapping file structure. > * ... > Feel free the modify the document in attachement and add it the new version > in this issue. This is not a simple project, so a working doc like this > should help us to work on the same foundations. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GRFT-37) Final JCR Mapping Document PROPOSAL
[ http://issues.apache.org/jira/browse/GRFT-37?page=all ] Christophe Lombart updated GRFT-37: --- Attachment: JCR Mapping proposal.pdf JCR Mapping proposal.sxw graffito-jcr-mapping.dtd Update document proposal : * Add more info the tools (Java Class Generator and JCR Node Type Registration) * xml mapping file proposal > Final JCR Mapping Document PROPOSAL > --- > > Key: GRFT-37 > URL: http://issues.apache.org/jira/browse/GRFT-37 > Project: Graffito > Type: Task > Components: Documentation > Versions: 1.0-a1-dev > Reporter: Christophe Lombart > Assignee: Christophe Lombart > Fix For: 1.0-a1-dev > Attachments: JCR Mapping proposal.pdf, JCR Mapping proposal.sxw, > graffito-jcr-mapping.dtd > > I would like to write a document which can group the different ideas in order > to have only one final proposal for : > * The subproject goals > * the component structures (I added in this doc the Sandro proposal) and API. > * The mapping file structure. > * ... > Feel free the modify the document in attachement and add it the new version > in this issue. This is not a simple project, so a working doc like this > should help us to work on the same foundations. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GRFT-37) Final JCR Mapping Document PROPOSAL
[ http://issues.apache.org/jira/browse/GRFT-37?page=all ] Christophe Lombart updated GRFT-37: --- Attachment: (was: jcr-mapping proposal.txt) > Final JCR Mapping Document PROPOSAL > --- > > Key: GRFT-37 > URL: http://issues.apache.org/jira/browse/GRFT-37 > Project: Graffito > Type: Task > Components: Documentation > Versions: 1.0-a1-dev > Reporter: Christophe Lombart > Assignee: Christophe Lombart > Fix For: 1.0-a1-dev > Attachments: JCR Mapping proposal.pdf, JCR Mapping proposal.sxw, > graffito-jcr-mapping.dtd > > I would like to write a document which can group the different ideas in order > to have only one final proposal for : > * The subproject goals > * the component structures (I added in this doc the Sandro proposal) and API. > * The mapping file structure. > * ... > Feel free the modify the document in attachement and add it the new version > in this issue. This is not a simple project, so a working doc like this > should help us to work on the same foundations. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (GRFT-18) Proof of concept for mapping Java beans to JCR nodetypes
[ http://issues.apache.org/jira/browse/GRFT-18?page=all ] Christophe Lombart closed GRFT-18: -- Resolution: Fixed The prototype is finished > Proof of concept for mapping Java beans to JCR nodetypes > > > Key: GRFT-18 > URL: http://issues.apache.org/jira/browse/GRFT-18 > Project: Graffito > Type: New Feature > Components: JCR-Mapping > Reporter: Sandro Boehme > Assignee: Christophe Lombart > Attachments: GraffitoJcrMappingTest.zip > > Hello, > attached there are (hopefully all) the files for a proof of concept > of three usecases for the JCR Mapping(I could not sent it to the mailing list > because it does not allow attachments): > 1. Registering custom nodetypes according to a Java Bean model. > 2. Persist a Java Bean. > 3. Loading a Java Bean from the repository. > ==>1. Creating the custom nodetypes is realized with JAXB. The > BeanConverter class maps the Java structure to the > nodetype structure and marshalls the custom_nodetypes.xml to the > configured nodetype folder. I attached the /lib folder > with the jaxb libraries, a XML schema and the command line call (in the > generateNodeTypeDTD.bat file) if somebody want > to generate a new custom_nodetypes.xml file. I did not check the schema > against the spec yet, because it will change anyway. > Once the definition of the custom_nodetypes.xml file is stable, I would > like to create an Ant target and a seperate library > for generating custom nodetypes out of Java Beans. > ==>2. Persisting simply works like that: > PersistenceManager pm = new PersistenceManager(session); > String relPath = pm.insert(folder); > ==>3. Loading can be implemented this way: > Folder loadedFolder = (Folder) pm.getObject(relPath); > All information for reading and writing a bean can be gained by the > class itself except the path where the > object is stored in the repository. This path acts like a unambiguous > database id. > ++ limitations ++ > o no complex properties can be saved (Folder.getDocument()) > o collections are not yet supported > o deletion is not yet supported > o only the basic JCR Types (String, boolean,...) and java.util.Date are > supported > o the bean converter is not yet adapted to Graffito converter handling > o mixin's/Interfaces are not yet supported > ++ next steps ++ > o much more test cases need to be added and I'm sure according bug's > need to be fixed ;-) > o also delete the data created in the test cases > o pm.update and pm.delete() need to be added > o more atomic types (like Character,...) need to be added > o support for complex types > o support for collections > o support for interfaces > o make the namespace "graffito" configurable > o support for JCR features like searching, versioning,... > o creating an Ant target for registering Java classes as nodetypes > o refactor some responsibilties and names of some classes > o ... > ++ configuration ++ > I don't think it is ready for check in because the configuration is not > very clean at the > moment. I needed to delete the repository data (repotest/versions and > repotest/workspaces/default) > in order to get the tests to run. I've not very much experience with > maven. Your information for this > issue are very much appreciated. > Regards, > Sandro -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (GRFT-32) The persistence managers object to item converter
[ http://issues.apache.org/jira/browse/GRFT-32?page=all ] Christophe Lombart closed GRFT-32: -- Fix Version: 1.0-a1-dev Resolution: Fixed Done > The persistence managers object to item converter > - > > Key: GRFT-32 > URL: http://issues.apache.org/jira/browse/GRFT-32 > Project: Graffito > Type: New Feature > Components: JCR-Mapping > Reporter: Sandro Boehme > Assignee: Sandro Boehme > Fix For: 1.0-a1-dev > > Creates a path of nodes and child-nodes out of an object path. The conversion > is specified by the the mapping model. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (GRFT-33) The atomic type converter
[ http://issues.apache.org/jira/browse/GRFT-33?page=all ] Christophe Lombart closed GRFT-33: -- Resolution: Fixed The Sandro code is integrated into the current implementation. > The atomic type converter > - > > Key: GRFT-33 > URL: http://issues.apache.org/jira/browse/GRFT-33 > Project: Graffito > Type: New Feature > Components: JCR-Mapping > Reporter: Sandro Boehme > Assignee: Sandro Boehme > > The JCR specifies a limited amount of property types (atomic types). > Application domain models will at least need all atomic types of > Java. We fill the gap with providing an atomic type converter as a flyweight > according to the flyweight pattern. This allows to register classes that can > convert all java types into JCR types. As it maximizes the reuse of the > atomic types it reduces instance creation and type conversion to a minimum. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (GRFT-22) a model for mapping a NodeType to a Java class
[ http://issues.apache.org/jira/browse/GRFT-22?page=all ] Christophe Lombart closed GRFT-22: -- Resolution: Fixed The model is defined in the proposal (see GRFT-37) > a model for mapping a NodeType to a Java class > -- > > Key: GRFT-22 > URL: http://issues.apache.org/jira/browse/GRFT-22 > Project: Graffito > Type: New Feature > Components: JCR-Mapping > Reporter: Sandro Boehme > Assignee: Sandro Boehme > > An XML schema serves as a model for a mapping between JCR node type > definitions and Java classes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (GRFT-24) Persistence Manager
[ http://issues.apache.org/jira/browse/GRFT-24?page=all ] Christophe Lombart closed GRFT-24: -- Resolution: Fixed The present manager (first implementation) is present in the current code. It used ObjectConverter, The AtomicTypeConverts and CollectionConverter. > Persistence Manager > --- > > Key: GRFT-24 > URL: http://issues.apache.org/jira/browse/GRFT-24 > Project: Graffito > Type: New Feature > Components: JCR-Mapping > Reporter: Sandro Boehme > Assignee: Sandro Boehme > > It manages the life cycle of persistence capable instances. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (GRFT-34) An initial code base for the mapping project.
[ http://issues.apache.org/jira/browse/GRFT-34?page=all ] Christophe Lombart closed GRFT-34: -- Resolution: Fixed > An initial code base for the mapping project. > - > > Key: GRFT-34 > URL: http://issues.apache.org/jira/browse/GRFT-34 > Project: Graffito > Type: New Feature > Reporter: Sandro Boehme > Assignee: Sandro Boehme > Attachments: jaxb_libs.zip, src_folder.zip > > As the list does not allow attachments I upload the zip file to this issue. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GRFT-40) Support all JCR types
Support all JCR types - Key: GRFT-40 URL: http://issues.apache.org/jira/browse/GRFT-40 Project: Graffito Type: Task Reporter: Christophe Lombart We have to support the following JCR Types : * PropertyType.NAME * PropertyType.PATH * PropertyType.REFERENCE * PropertyType.UNDEFINED -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GRFT-40) Support all JCR types
[ http://issues.apache.org/jira/browse/GRFT-40?page=all ] Christophe Lombart updated GRFT-40: --- Component: JCR-Mapping Fix Version: 1.0-a1-dev > Support all JCR types > - > > Key: GRFT-40 > URL: http://issues.apache.org/jira/browse/GRFT-40 > Project: Graffito > Type: Task > Components: JCR-Mapping > Reporter: Christophe Lombart > Fix For: 1.0-a1-dev > > We have to support the following JCR Types : >* PropertyType.NAME >* PropertyType.PATH >* PropertyType.REFERENCE >* PropertyType.UNDEFINED -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GRFT-41) Implement other collection converters & Manageable collections
Implement other collection converters & Manageable collections -- Key: GRFT-41 URL: http://issues.apache.org/jira/browse/GRFT-41 Project: Graffito Type: Task Components: JCR-Mapping Reporter: Christophe Lombart Fix For: 1.0-a1-dev * We have to support at least Map, HashMap, ... * We have to implement a collection converter based on node types. By this way, it is not necessary to use an extra jcr node. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GRFT-40) Advanced support for JCR items
[ http://issues.apache.org/jira/browse/GRFT-40?page=all ] Christophe Lombart updated GRFT-40: --- Summary: Advanced support for JCR items (was: Support all JCR types) Description: - We have to support the following JCR Types : * PropertyType.NAME * PropertyType.PATH * PropertyType.REFERENCE * PropertyType.UNDEFINED - Map UUID ? - Check if mandatory & auto created properties are well managed. More unit test are required. was: We have to support the following JCR Types : * PropertyType.NAME * PropertyType.PATH * PropertyType.REFERENCE * PropertyType.UNDEFINED > Advanced support for JCR items > -- > > Key: GRFT-40 > URL: http://issues.apache.org/jira/browse/GRFT-40 > Project: Graffito > Type: Task > Components: JCR-Mapping > Reporter: Christophe Lombart > Fix For: 1.0-a1-dev > > - We have to support the following JCR Types : >* PropertyType.NAME >* PropertyType.PATH >* PropertyType.REFERENCE >* PropertyType.UNDEFINED > - Map UUID ? > - Check if mandatory & auto created properties are well managed. More unit > test are required. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GRFT-42) Increase performance for Bean & collections fields
Increase performance for Bean & collections fields -- Key: GRFT-42 URL: http://issues.apache.org/jira/browse/GRFT-42 Project: Graffito Type: Task Components: JCR-Mapping Reporter: Christophe Lombart Fix For: 1.0-a1-dev when loading or updating bean and collection fields, we can increase the performance by using the following features : * proxy / Lazy loading : load the bean or the collection when the getter is called (not when the main object is retrieved) * auto-update : this attribute can specify if the bean or the collection has to be updated. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GRFT-43) Transaction support in the PersistenceManager
Transaction support in the PersistenceManager - Key: GRFT-43 URL: http://issues.apache.org/jira/browse/GRFT-43 Project: Graffito Type: Task Components: JCR-Mapping Versions: 1.0-a1-dev Reporter: Christophe Lombart -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GRFT-44) Add search capabilities in the PersistenceManager
Add search capabilities in the PersistenceManager - Key: GRFT-44 URL: http://issues.apache.org/jira/browse/GRFT-44 Project: Graffito Type: Task Reporter: Christophe Lombart We can make search with a simple Criteria object or with some JCR expressions. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GRFT-44) Add search capabilities in the PersistenceManager
[ http://issues.apache.org/jira/browse/GRFT-44?page=all ] Christophe Lombart updated GRFT-44: --- Component: JCR-Mapping Fix Version: 1.0-a1-dev > Add search capabilities in the PersistenceManager > - > > Key: GRFT-44 > URL: http://issues.apache.org/jira/browse/GRFT-44 > Project: Graffito > Type: Task > Components: JCR-Mapping > Reporter: Christophe Lombart > Fix For: 1.0-a1-dev > > We can make search with a simple Criteria object or with some JCR expressions. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GRFT-45) Cache framework integration
Cache framework integration --- Key: GRFT-45 URL: http://issues.apache.org/jira/browse/GRFT-45 Project: Graffito Type: Task Reporter: Christophe Lombart The PersistenceManager should work with a cache manager. * The Spring frameworks offer a nice solution to integrate an application with a cache manager (based on AOP). * Which cache framework to use ? oscache, JCS, ... * A more detailled proposal is required -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GRFT-46) Add version control in the PersistenceManager
Add version control in the PersistenceManager - Key: GRFT-46 URL: http://issues.apache.org/jira/browse/GRFT-46 Project: Graffito Type: Task Components: JCR-Mapping Reporter: Christophe Lombart -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GRFT-45) Cache framework integration
[ http://issues.apache.org/jira/browse/GRFT-45?page=all ] Christophe Lombart updated GRFT-45: --- Component: JCR-Mapping Fix Version: 1.0-a1-dev > Cache framework integration > --- > > Key: GRFT-45 > URL: http://issues.apache.org/jira/browse/GRFT-45 > Project: Graffito > Type: Task > Components: JCR-Mapping > Reporter: Christophe Lombart > Fix For: 1.0-a1-dev > > The PersistenceManager should work with a cache manager. > * The Spring frameworks offer a nice solution to integrate an application > with a cache manager (based on AOP). > * Which cache framework to use ? oscache, JCS, ... > * A more detailled proposal is required -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GRFT-46) Add version control in the PersistenceManager
[ http://issues.apache.org/jira/browse/GRFT-46?page=all ] Christophe Lombart updated GRFT-46: --- Fix Version: 1.0-a1-dev > Add version control in the PersistenceManager > - > > Key: GRFT-46 > URL: http://issues.apache.org/jira/browse/GRFT-46 > Project: Graffito > Type: Task > Components: JCR-Mapping > Reporter: Christophe Lombart > Fix For: 1.0-a1-dev > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GRFT-47) Fine grained access control
Fine grained access control --- Key: GRFT-47 URL: http://issues.apache.org/jira/browse/GRFT-47 Project: Graffito Type: Task Components: JCR-Mapping Reporter: Christophe Lombart Fix For: 1.0-a1-dev * The PersistenceManager has to control the permissions applying on the JCR nodes. * Based on JAAS * Graffito has already this kind of features (see the OJBStore implementation). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GRFT-48) Support more than one xml mapping file
Support more than one xml mapping file -- Key: GRFT-48 URL: http://issues.apache.org/jira/browse/GRFT-48 Project: Graffito Type: Improvement Components: JCR-Mapping Reporter: Christophe Lombart Fix For: 1.0-a1-dev Supporting more than one xml mapping file found in one forlder or an array of file references can give more flexibility to deploy Graffito modules. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GRFT-49) Add support for inheritance and interfaces
[ http://issues.apache.org/jira/browse/GRFT-49?page=comments#action_12324484 ] Christophe Lombart commented on GRFT-49: How to manager secondary node types ? > Add support for inheritance and interfaces > -- > > Key: GRFT-49 > URL: http://issues.apache.org/jira/browse/GRFT-49 > Project: Graffito > Type: New Feature > Components: JCR-Mapping > Reporter: Christophe Lombart > Fix For: 1.0-a1-dev > > The Persistence Manager has to manage interfaces and inheritance : > * It should be possible to declare in the mapping file an ancestor and > reference it in other ClassDescriptors. > * It should be possible to make queries based on interface. The result set > should contains the interface implementation objects. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GRFT-49) Add support for inheritance and interfaces
Add support for inheritance and interfaces -- Key: GRFT-49 URL: http://issues.apache.org/jira/browse/GRFT-49 Project: Graffito Type: New Feature Components: JCR-Mapping Reporter: Christophe Lombart Fix For: 1.0-a1-dev The Persistence Manager has to manage interfaces and inheritance : * It should be possible to declare in the mapping file an ancestor and reference it in other ClassDescriptors. * It should be possible to make queries based on interface. The result set should contains the interface implementation objects. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GRFT-50) Update to a more recent Jackrabbit snapshot
Update to a more recent Jackrabbit snapshot --- Key: GRFT-50 URL: http://issues.apache.org/jira/browse/GRFT-50 Project: Graffito Type: Improvement Components: JCR-Mapping Reporter: Christophe Lombart Fix For: 1.0-a1-dev -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (GRFT-50) Update to a more recent Jackrabbit snapshot
[ http://issues.apache.org/jira/browse/GRFT-50?page=all ] Christophe Lombart reassigned GRFT-50: -- Assign To: Christophe Lombart > Update to a more recent Jackrabbit snapshot > --- > > Key: GRFT-50 > URL: http://issues.apache.org/jira/browse/GRFT-50 > Project: Graffito > Type: Improvement > Components: JCR-Mapping > Reporter: Christophe Lombart > Assignee: Christophe Lombart > Fix For: 1.0-a1-dev > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GRFT-51) Review the PersistenceManager API
Review the PersistenceManager API - Key: GRFT-51 URL: http://issues.apache.org/jira/browse/GRFT-51 Project: Graffito Type: Improvement Components: JCR-Mapping Reporter: Christophe Lombart Fix For: 1.0-a1-dev >From Oliver : First of all,the Persistence Manager looks fine to me except that I am not sure if it should contain the methods setupRepository(), getRepository(), getSession(), getUser(), setJcrCustomNodeTypeCreator() and getJcrCustomNodeTypeCreator() because they allow direct access to the underlying JCR API and the JCR repository itself. I believe the PersistenceManager should avoid allowing methods that circumvent the use of the graffito object persistence mechanism. These methods would be better off somewhere else. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GRFT-52) JCR Mapping Documentation
JCR Mapping Documentation -- Key: GRFT-52 URL: http://issues.apache.org/jira/browse/GRFT-52 Project: Graffito Type: Task Components: JCR-Mapping Reporter: Christophe Lombart Fix For: 1.0-a1-dev Add documentation and tutorial on JCR Mapping : - API Overview - Map simple fields - Map bean fields - Map collection - How to mofigy the Collection mapping strategy - Use any kind of Collection with the ManageableCollections ... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (GRFT-41) Implement other collection converters & Manageable collections
[ http://issues.apache.org/jira/browse/GRFT-41?page=all ] Christophe Lombart closed GRFT-41: -- Resolution: Fixed Now, there is a new converter class : NTCollectionConverterImpl and it is possible to use any kind of Java collection (eg. an hashMap). One exemple can be found in : HashMapTest.java > Implement other collection converters & Manageable collections > -- > > Key: GRFT-41 > URL: http://issues.apache.org/jira/browse/GRFT-41 > Project: Graffito > Type: Task > Components: JCR-Mapping > Reporter: Christophe Lombart > Fix For: 1.0-a1-dev > > * We have to support at least Map, HashMap, ... > * We have to implement a collection converter based on node types. By this > way, it is not necessary to use an extra jcr node. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (GRFT-51) Review the PersistenceManager API
[ http://issues.apache.org/jira/browse/GRFT-51?page=all ] Christophe Lombart closed GRFT-51: -- Resolution: Fixed Done > Review the PersistenceManager API > - > > Key: GRFT-51 > URL: http://issues.apache.org/jira/browse/GRFT-51 > Project: Graffito > Type: Improvement > Components: JCR-Mapping > Reporter: Christophe Lombart > Fix For: 1.0-a1-dev > > From Oliver : > First of all,the Persistence Manager looks fine to me except that I am not > sure if it should contain the methods setupRepository(), getRepository(), > getSession(), getUser(), setJcrCustomNodeTypeCreator() and > getJcrCustomNodeTypeCreator() because they allow direct access to the > underlying JCR API and the JCR repository itself. I believe the > PersistenceManager should avoid allowing methods that circumvent the use of > the graffito object persistence mechanism. These methods would be better off > somewhere else. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (GRFT-50) Update to a more recent Jackrabbit snapshot
[ http://issues.apache.org/jira/browse/GRFT-50?page=all ] Christophe Lombart closed GRFT-50: -- Resolution: Fixed Done. It seems that Lucene integration is better. we have not some exception related to the Lucene index > Update to a more recent Jackrabbit snapshot > --- > > Key: GRFT-50 > URL: http://issues.apache.org/jira/browse/GRFT-50 > Project: Graffito > Type: Improvement > Components: JCR-Mapping > Reporter: Christophe Lombart > Assignee: Christophe Lombart > Fix For: 1.0-a1-dev > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (GRFT-44) Add search capabilities in the PersistenceManager
[ http://issues.apache.org/jira/browse/GRFT-44?page=all ] Christophe Lombart reassigned GRFT-44: -- Assign To: Christophe Lombart > Add search capabilities in the PersistenceManager > - > > Key: GRFT-44 > URL: http://issues.apache.org/jira/browse/GRFT-44 > Project: Graffito > Type: Task > Components: JCR-Mapping > Reporter: Christophe Lombart > Assignee: Christophe Lombart > Fix For: 1.0-a1-dev > > We can make search with a simple Criteria object or with some JCR expressions. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GRFT-53) Support for multi value fields
Support for multi value fields -- Key: GRFT-53 URL: http://issues.apache.org/jira/browse/GRFT-53 Project: Graffito Type: Improvement Components: JCR-Mapping Versions: 1.0-a1-dev Reporter: Christophe Lombart Fix For: 1.0-a1-dev A collection field can be a multivalue property (see the JCR spec) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GRFT-54) Add more flexibility in the mapping
Add more flexibility in the mapping
Key: GRFT-54
URL: http://issues.apache.org/jira/browse/GRFT-54
Project: Graffito
Type: Improvement
Reporter: Christophe Lombart
Sometime, it should be interesting to map to a different jcr node structure.
Here is an example, for a class "File", we can have :
public class File
{
private String mimeType;
private String encoding;
private InputStream data;
private Calendar lastModified;
// Add getters/setters
}
and in terms of JCR structure, we can have :
nt:file
jcr:content
jcr:mimeType
jcr:encoding
jcr:data
jcr:lastModified
So, the jcr:content node is an extra node to specify in the mapping file.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (GRFT-54) Add more flexibility in the mapping
[ http://issues.apache.org/jira/browse/GRFT-54?page=all ]
Christophe Lombart updated GRFT-54:
---
Component: JCR-Mapping
Fix Version: 1.0-a1-dev
Version: 1.0-a1-dev
> Add more flexibility in the mapping
> ---
>
> Key: GRFT-54
> URL: http://issues.apache.org/jira/browse/GRFT-54
> Project: Graffito
> Type: Improvement
> Components: JCR-Mapping
> Versions: 1.0-a1-dev
> Reporter: Christophe Lombart
> Fix For: 1.0-a1-dev
>
> Sometime, it should be interesting to map to a different jcr node structure.
> Here is an example, for a class "File", we can have :
> public class File
> {
> private String mimeType;
> private String encoding;
> private InputStream data;
> private Calendar lastModified;
> // Add getters/setters
> }
> and in terms of JCR structure, we can have :
> nt:file
> jcr:content
> jcr:mimeType
> jcr:encoding
> jcr:data
> jcr:lastModified
> So, the jcr:content node is an extra node to specify in the mapping file.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Closed: (GRFT-39) Dont use File file = new File() for reading file, use InputStream
[ http://issues.apache.org/jira/browse/GRFT-39?page=all ] Christophe Lombart closed GRFT-39: -- Fix Version: 1.0-a1-dev Resolution: Fixed Apply patch provided by Costin > Dont use File file = new File() for reading file, use InputStream > - > > Key: GRFT-39 > URL: http://issues.apache.org/jira/browse/GRFT-39 > Project: Graffito > Type: Bug > Components: JCR-Mapping > Versions: 1.0-a1-dev > Reporter: Martin Koci > Priority: Minor > Fix For: 1.0-a1-dev > Attachments: DisgesterDescriptorReader.patch, DisgesterMapperImpl.patch > > See http://www.javaworld.com/javaworld/javaqa/2003-08/01-qa-0808-property.html > File file = new File() dont work in jar. > I use Spring framework org.springframework.core.io.Resource abstraction - it > works in jar, servlet, test ... everywhere. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (GRFT-55) persistence manager signature changed
[ http://issues.apache.org/jira/browse/GRFT-55?page=all ] Christophe Lombart closed GRFT-55: -- Fix Version: 1.0-a1-dev Resolution: Fixed Apply patch provided by Costin > persistence manager signature changed > - > > Key: GRFT-55 > URL: http://issues.apache.org/jira/browse/GRFT-55 > Project: Graffito > Type: Improvement > Components: JCR-Mapping > Versions: 1.0-a1-dev > Reporter: Costin Leau > Fix For: 1.0-a1-dev > Attachments: PersistenceManagerImpl.patch > > the patch removes the repository signature from the constructor. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (GRFT-56) Support inheritance from org.apache.portals.graffito.jcr.persistence.impl.PersistenceManagerImpl
[ http://issues.apache.org/jira/browse/GRFT-56?page=all ] Christophe Lombart resolved GRFT-56: Resolution: Fixed Now all attributes are protected > Support inheritance from > org.apache.portals.graffito.jcr.persistence.impl.PersistenceManagerImpl > > > Key: GRFT-56 > URL: http://issues.apache.org/jira/browse/GRFT-56 > Project: Graffito > Type: Improvement > Components: JCR-Mapping > Versions: 1.0-a1-dev > Reporter: Martin Koci > Priority: Trivial > Attachments: PersistenceManagerImpl.patch > > Make properties protected or provide protected getter methods -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (GRFT-53) Support for multi value fields
[ http://issues.apache.org/jira/browse/GRFT-53?page=all ] Christophe Lombart reassigned GRFT-53: -- Assign To: Christophe Lombart > Support for multi value fields > -- > > Key: GRFT-53 > URL: http://issues.apache.org/jira/browse/GRFT-53 > Project: Graffito > Type: Improvement > Components: JCR-Mapping > Versions: 1.0-a1-dev > Reporter: Christophe Lombart > Assignee: Christophe Lombart > Fix For: 1.0-a1-dev > > A collection field can be a multivalue property (see the JCR spec) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (GRFT-57) org.apache.portals.graffito.jcr.mapper.Mapper#getClassDescriptor doesn't need to throw JcrMappingException
[ http://issues.apache.org/jira/browse/GRFT-57?page=all ] Christophe Lombart resolved GRFT-57: Resolution: Fixed Fixed - Patch applied > org.apache.portals.graffito.jcr.mapper.Mapper#getClassDescriptor doesn't need > to throw JcrMappingException > -- > > Key: GRFT-57 > URL: http://issues.apache.org/jira/browse/GRFT-57 > Project: Graffito > Type: Improvement > Components: JCR-Mapping > Versions: 1.0-a1-dev > Reporter: Martin Koci > Priority: Trivial > Attachments: DigesterMapperImpl.patch, Mapper.patch > > That method can simply return class descriptor if class is mapped or null if > not. > And of cource can throw runtime exception indicating programmer bug. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (GRFT-48) Support more than one xml mapping file
[ http://issues.apache.org/jira/browse/GRFT-48?page=all ] Christophe Lombart resolved GRFT-48: Resolution: Fixed Done in the MapperDigesterImpl. Now, it is possible to load multiple files > Support more than one xml mapping file > -- > > Key: GRFT-48 > URL: http://issues.apache.org/jira/browse/GRFT-48 > Project: Graffito > Type: Improvement > Components: JCR-Mapping > Reporter: Christophe Lombart > Fix For: 1.0-a1-dev > > Supporting more than one xml mapping file found in one forlder or an array of > file references can give more flexibility to deploy Graffito modules. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (GRFT-53) Support for multi value fields
[ http://issues.apache.org/jira/browse/GRFT-53?page=all ] Christophe Lombart resolved GRFT-53: Resolution: Fixed Now, it is possible to use a collection to store a multiple value field and also search on it. Unit test contains one example. Following the JCR spec, all collection elements has to be the same types (String, int, ...). > Support for multi value fields > -- > > Key: GRFT-53 > URL: http://issues.apache.org/jira/browse/GRFT-53 > Project: Graffito > Type: Improvement > Components: JCR-Mapping > Versions: 1.0-a1-dev > Reporter: Christophe Lombart > Assignee: Christophe Lombart > Fix For: 1.0-a1-dev > > A collection field can be a multivalue property (see the JCR spec) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (GRFT-44) Add search capabilities in the PersistenceManager
[ http://issues.apache.org/jira/browse/GRFT-44?page=all ] Christophe Lombart resolved GRFT-44: Resolution: Fixed First release has be done. We will add new search features later (after receiving community feedback) > Add search capabilities in the PersistenceManager > - > > Key: GRFT-44 > URL: http://issues.apache.org/jira/browse/GRFT-44 > Project: Graffito > Type: Task > Components: JCR-Mapping > Reporter: Christophe Lombart > Assignee: Christophe Lombart > Fix For: 1.0-a1-dev > > We can make search with a simple Criteria object or with some JCR expressions. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (GRFT-58) Can be JcrMappingException type of RUNTIME exception?
[ http://issues.apache.org/jira/browse/GRFT-58?page=all ] Christophe Lombart reassigned GRFT-58: -- Assign To: Christophe Lombart > Can be JcrMappingException type of RUNTIME exception? > - > > Key: GRFT-58 > URL: http://issues.apache.org/jira/browse/GRFT-58 > Project: Graffito > Type: Improvement > Components: JCR-Mapping > Versions: 1.0-a1-dev > Reporter: Martin Koci > Assignee: Christophe Lombart > > http://www.mindview.net/Etc/Discussions/CheckedExceptions > http://www-128.ibm.com/developerworks/java/library/j-jtp05254.html > HibernateException is runtime too (from version 3.0) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GRFT-59) Review PersistenceManager methods
Review PersistenceManager methods - Key: GRFT-59 URL: http://issues.apache.org/jira/browse/GRFT-59 Project: Graffito Type: Improvement Components: JCR-Mapping Versions: 1.0-a1-dev Reporter: Christophe Lombart Review method in pm : insert, delete, ... The "path" argument can be dropped if we accept to set into the pojo (and of course in the xml mapping file) the path reference and/or the UUID. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GRFT-40) Advanced support for JCR properties and node
[ http://issues.apache.org/jira/browse/GRFT-40?page=all ] Christophe Lombart updated GRFT-40: --- Summary: Advanced support for JCR properties and node (was: Advanced support for JCR items) Description: - We have to support the following JCR Types : * PropertyType.NAME * PropertyType.PATH * PropertyType.REFERENCE * PropertyType.UNDEFINED - Map UUID and the path into the POJO object - Check if mandatory & auto created properties are well managed. More unit test are required. - Support for same-name siblings : the query service should supported it ans we have also to support the method : node.getNodes(nodepattern). We have also to check if the insert, update and delete methods support correctly the same-name sibling. was: - We have to support the following JCR Types : * PropertyType.NAME * PropertyType.PATH * PropertyType.REFERENCE * PropertyType.UNDEFINED - Map UUID ? - Check if mandatory & auto created properties are well managed. More unit test are required. > Advanced support for JCR properties and node > > > Key: GRFT-40 > URL: http://issues.apache.org/jira/browse/GRFT-40 > Project: Graffito > Type: Task > Components: JCR-Mapping > Reporter: Christophe Lombart > Fix For: 1.0-a1-dev > > - We have to support the following JCR Types : >* PropertyType.NAME >* PropertyType.PATH >* PropertyType.REFERENCE >* PropertyType.UNDEFINED > - Map UUID and the path into the POJO object > - Check if mandatory & auto created properties are well managed. More unit > test are required. > - Support for same-name siblings : the query service should supported it ans > we have also to support the method : node.getNodes(nodepattern). We have > also to check if the insert, update and delete methods support correctly the > same-name sibling. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GRFT-60) Advanced search features
Advanced search features Key: GRFT-60 URL: http://issues.apache.org/jira/browse/GRFT-60 Project: Graffito Type: Improvement Components: JCR-Mapping Versions: 1.0-a1-dev Reporter: Christophe Lombart * Add method getReport (similar to the OJB method getReportByQuery) * support for jcr:score() & jcr: defref * Full text seach on binary * Support filter based on collection fields and bean fields : impossible to do with the current Jackrabbit version see in Jackrabbit JIRA : JCR-246, JSR-247 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GRFT-61) Review the Mapper Service
Review the Mapper Service - Key: GRFT-61 URL: http://issues.apache.org/jira/browse/GRFT-61 Project: Graffito Type: Improvement Components: JCR-Mapping Versions: 1.0-a1-dev Reporter: Christophe Lombart * Add more check when loading the mapping file : - Check if the referenced class exist in the classpath and has a classdescriptor - Error when duplicate class-descriptor are loaded (same for field & collections descriptors). * throws an exception when class descriptor, field/bean/collection descriptor are not found. (getxxx methods defined in the object mapper model). * Add converter attribute in the xml config file for atomicfields. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GRFT-62) Clean-up the unit tests
Clean-up the unit tests --- Key: GRFT-62 URL: http://issues.apache.org/jira/browse/GRFT-62 Project: Graffito Type: Improvement Reporter: Christophe Lombart Use startup / tearDown to init and remove the data -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (GRFT-62) Clean-up the unit tests
[ http://issues.apache.org/jira/browse/GRFT-62?page=all ] Christophe Lombart reassigned GRFT-62: -- Assign To: Christophe Lombart > Clean-up the unit tests > --- > > Key: GRFT-62 > URL: http://issues.apache.org/jira/browse/GRFT-62 > Project: Graffito > Type: Improvement > Reporter: Christophe Lombart > Assignee: Christophe Lombart > > Use startup / tearDown to init and remove the data -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GRFT-63) Move & copy objects
Move & copy objects --- Key: GRFT-63 URL: http://issues.apache.org/jira/browse/GRFT-63 Project: Graffito Type: Improvement Components: JCR-Mapping Reporter: Christophe Lombart Add new methods in the persistence manager to move and copy objects -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GRFT-63) Move & copy objects
[ http://issues.apache.org/jira/browse/GRFT-63?page=all ] Christophe Lombart updated GRFT-63: --- Component: JCR-Mapping > Move & copy objects > --- > > Key: GRFT-63 > URL: http://issues.apache.org/jira/browse/GRFT-63 > Project: Graffito > Type: Improvement > Components: JCR-Mapping > Reporter: Christophe Lombart > > Add new methods in the persistence manager to move and copy objects -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GRFT-62) Clean-up the unit tests
[ http://issues.apache.org/jira/browse/GRFT-62?page=all ] Christophe Lombart updated GRFT-62: --- Component: JCR-Mapping Version: 1.0-a1-dev > Clean-up the unit tests > --- > > Key: GRFT-62 > URL: http://issues.apache.org/jira/browse/GRFT-62 > Project: Graffito > Type: Improvement > Components: JCR-Mapping > Versions: 1.0-a1-dev > Reporter: Christophe Lombart > Assignee: Christophe Lombart > > Use startup / tearDown to init and remove the data -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GRFT-64) Add support for JCR Lock
Add support for JCR Lock Key: GRFT-64 URL: http://issues.apache.org/jira/browse/GRFT-64 Project: Graffito Type: New Feature Components: JCR-Mapping Versions: 1.0-a1-dev Reporter: Christophe Lombart -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
