Re: CMS Integration
Hi! Can we talk on Gtalk or something? Actually, I don't have much code, just one-two classes... Igor On 12/14/06, Borut Bolčina [EMAIL PROTECTED] wrote: Hi Igor, I am planning to integrate Tapestry with some portal and CMS solutions available commercially or in open source form. Accessing content repository like Apache Jackrabbit via Tapestry components (and/or portlets) seems a goal to pursue. I am very interested in your work so far. Can you please share some info on your solutions? Regards, Borut 2006/9/5, soir [EMAIL PROTECTED]: Hello, I work on the integration of Jackrabbit repository with Tapestry. So far, I have implemented the loading of localized assets from CMS and now I am working on the loading of message files from CMS. Igor -- View this message in context: http://www.nabble.com/OT%3A-Tacos-issues-tf1875199.html#a6148924 Sent from the Tapestry - User forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: CMS Integration
Hi Igor, I am planning to integrate Tapestry with some portal and CMS solutions available commercially or in open source form. Accessing content repository like Apache Jackrabbit via Tapestry components (and/or portlets) seems a goal to pursue. I am very interested in your work so far. Can you please share some info on your solutions? Regards, Borut 2006/9/5, soir [EMAIL PROTECTED]: Hello, I work on the integration of Jackrabbit repository with Tapestry. So far, I have implemented the loading of localized assets from CMS and now I am working on the loading of message files from CMS. Igor -- View this message in context: http://www.nabble.com/OT%3A-Tacos-issues-tf1875199.html#a6148924 Sent from the Tapestry - User forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: CMS Integration
Hello, I work on the integration of Jackrabbit repository with Tapestry. So far, I have implemented the loading of localized assets from CMS and now I am working on the loading of message files from CMS. Igor -- View this message in context: http://www.nabble.com/OT%3A-Tacos-issues-tf1875199.html#a6148924 Sent from the Tapestry - User forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: CMS Integration
Simeon, it would of course be great if you'd provide your code. I wasn't aware you had already done some work in the area, only today by means of google I read your posting from november 05. What is the status of your code? Is it currently in use with alfresco? Have you tried it with other JCRs, such as jackrabbit? Is it available for download anywhere? Apparently, there is a handful of people interested in JCR access through Tapestry, so I think we should set something up. If it wasn't for you mail, I would have created a tapestry-jcr sourceforge project and would have started working on the functionality your code apparently provides. I have little time to spare for it, though, so to start of with already working code would give it quite a boost. But I don't want to steal your project from you - maybe you want to turn it into a sourceforge project yourself? I'm sure people will use those components and you'll get a lot of credit for it. Well, if you don't, let me know. In that case I'll be happy to start a project based on your implementation. Regards, Lutz On 7/10/06, Simeon Koptelov [EMAIL PROTECTED] wrote: Oh, if you're interested in it, I can give my code for JCR integration as a base :) 2006/7/9, Lutz Hühnken [EMAIL PROTECTED]: Hi, I haven't really looked at it, but I was wondering... as far as I understand, you'd like to integrate CMS-managed content into a Tapestry-based site. You mention Magnolia... afaik, Magnolia uses a JSR 170 compliant content repository, such as Apache Jackrabbit (http://jackrabbit.apache.org/;), to store the content. It provides a number of JSP tags to access that content from within your page templates (http://magnolia.sourceforge.net/30/taglib/intro.html;). It seems getting content out of Jackrabbit is not all that hard. So here's my idea: Why don't we start a project to build some Tapestry components to access content repositories that conform with JSR 170? A possible approach could be to re-implement the Magnolia JSP taglib, or parts of it, as Tapestry components. Or maybe Stitches could be used as a starting point. This way, I would think, you could use any JSR 170 compliant CMS to manage your content, and could integrate the content in a Tapestry based site using this new component library. What do people think? Is that realistic? Would it work? Would such a component library be of interest to anyone? Lutz On 7/1/06, Mike Grundvig [EMAIL PROTECTED] wrote: Has anyone integrated any sort of CMS tool with Tapestry? I've looked into Magnolia and several others, but all seem to require an uphill battle if they are to be tied into Tapestry and I was wondering if someone else has already done this. Thanks! Michael Grundvig - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: CMS Integration
a common CMS component library would be a very nice feature/add-on: - not re-invent the wheel - growing market need - Tapestry will 'sell' more/better - ... I'm interested in contributing/developing on this topic! greetz -Original Message- From: Simeon Koptelov [mailto:[EMAIL PROTECTED] Sent: maandag 10 juli 2006 7:30 To: Tapestry users Subject: Re: CMS Integration Oh, if you're interested in it, I can give my code for JCR integration as a base :) 2006/7/9, Lutz Hühnken [EMAIL PROTECTED]: Hi, I haven't really looked at it, but I was wondering... as far as I understand, you'd like to integrate CMS-managed content into a Tapestry-based site. You mention Magnolia... afaik, Magnolia uses a JSR 170 compliant content repository, such as Apache Jackrabbit (http://jackrabbit.apache.org/;), to store the content. It provides a number of JSP tags to access that content from within your page templates (http://magnolia.sourceforge.net/30/taglib/intro.html;). It seems getting content out of Jackrabbit is not all that hard. So here's my idea: Why don't we start a project to build some Tapestry components to access content repositories that conform with JSR 170? A possible approach could be to re-implement the Magnolia JSP taglib, or parts of it, as Tapestry components. Or maybe Stitches could be used as a starting point. This way, I would think, you could use any JSR 170 compliant CMS to manage your content, and could integrate the content in a Tapestry based site using this new component library. What do people think? Is that realistic? Would it work? Would such a component library be of interest to anyone? Lutz On 7/1/06, Mike Grundvig [EMAIL PROTECTED] wrote: Has anyone integrated any sort of CMS tool with Tapestry? I've looked into Magnolia and several others, but all seem to require an uphill battle if they are to be tied into Tapestry and I was wondering if someone else has already done this. Thanks! Michael Grundvig - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: CMS Integration
I think a CMS component library is a very good idea. I'm searching something like it. I'm trying Stitches, but I'm having some problems building and deploying examples. 2006/7/10, [EMAIL PROTECTED] [EMAIL PROTECTED]: a common CMS component library would be a very nice feature/add-on: - not re-invent the wheel - growing market need - Tapestry will 'sell' more/better - ... I'm interested in contributing/developing on this topic! greetz -Original Message- From: Simeon Koptelov [mailto: [EMAIL PROTECTED] Sent: maandag 10 juli 2006 7:30 To: Tapestry users Subject: Re: CMS Integration Oh, if you're interested in it, I can give my code for JCR integration as a base :) 2006/7/9, Lutz Hühnken [EMAIL PROTECTED]: Hi, I haven't really looked at it, but I was wondering... as far as I understand, you'd like to integrate CMS-managed content into a Tapestry-based site. You mention Magnolia... afaik, Magnolia uses a JSR 170 compliant content repository, such as Apache Jackrabbit (http://jackrabbit.apache.org/;), to store the content. It provides a number of JSP tags to access that content from within your page templates (http://magnolia.sourceforge.net/30/taglib/intro.html;). It seems getting content out of Jackrabbit is not all that hard. So here's my idea: Why don't we start a project to build some Tapestry components to access content repositories that conform with JSR 170? A possible approach could be to re-implement the Magnolia JSP taglib, or parts of it, as Tapestry components. Or maybe Stitches could be used as a starting point. This way, I would think, you could use any JSR 170 compliant CMS to manage your content, and could integrate the content in a Tapestry based site using this new component library. What do people think? Is that realistic? Would it work? Would such a component library be of interest to anyone? Lutz On 7/1/06, Mike Grundvig [EMAIL PROTECTED] wrote: Has anyone integrated any sort of CMS tool with Tapestry? I've looked into Magnolia and several others, but all seem to require an uphill battle if they are to be tied into Tapestry and I was wondering if someone else has already done this. Thanks! Michael Grundvig - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: CMS Integration
Julio C. Rivera wrote: I think a CMS component library is a very good idea. I'm searching something like it. I'm trying Stitches, but I'm having some problems building and deploying examples. 2006/7/10, [EMAIL PROTECTED] [EMAIL PROTECTED]: a common CMS component library would be a very nice feature/add-on: - not re-invent the wheel - growing market need - Tapestry will 'sell' more/better - ... I'm interested in contributing/developing on this topic! greetz -Original Message- From: Simeon Koptelov [mailto: [EMAIL PROTECTED] Sent: maandag 10 juli 2006 7:30 To: Tapestry users Subject: Re: CMS Integration Oh, if you're interested in it, I can give my code for JCR integration as a base :) 2006/7/9, Lutz Hühnken [EMAIL PROTECTED]: Hi, I haven't really looked at it, but I was wondering... as far as I understand, you'd like to integrate CMS-managed content into a Tapestry-based site. You mention Magnolia... afaik, Magnolia uses a JSR 170 compliant content repository, such as Apache Jackrabbit (http://jackrabbit.apache.org/;), to store the content. It provides a number of JSP tags to access that content from within your page templates (http://magnolia.sourceforge.net/30/taglib/intro.html;). It seems getting content out of Jackrabbit is not all that hard. So here's my idea: Why don't we start a project to build some Tapestry components to access content repositories that conform with JSR 170? A possible approach could be to re-implement the Magnolia JSP taglib, or parts of it, as Tapestry components. Or maybe Stitches could be used as a starting point. This way, I would think, you could use any JSR 170 compliant CMS to manage your content, and could integrate the content in a Tapestry based site using this new component library. What do people think? Is that realistic? Would it work? Would such a component library be of interest to anyone? Lutz On 7/1/06, Mike Grundvig [EMAIL PROTECTED] wrote: Has anyone integrated any sort of CMS tool with Tapestry? I've looked into Magnolia and several others, but all seem to require an uphill battle if they are to be tied into Tapestry and I was wondering if someone else has already done this. Thanks! Michael Grundvig - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: CMS Integration
Oh, if you're interested in it, I can give my code for JCR integration as a base :) 2006/7/9, Lutz Hühnken [EMAIL PROTECTED]: Hi, I haven't really looked at it, but I was wondering... as far as I understand, you'd like to integrate CMS-managed content into a Tapestry-based site. You mention Magnolia... afaik, Magnolia uses a JSR 170 compliant content repository, such as Apache Jackrabbit (http://jackrabbit.apache.org/;), to store the content. It provides a number of JSP tags to access that content from within your page templates (http://magnolia.sourceforge.net/30/taglib/intro.html;). It seems getting content out of Jackrabbit is not all that hard. So here's my idea: Why don't we start a project to build some Tapestry components to access content repositories that conform with JSR 170? A possible approach could be to re-implement the Magnolia JSP taglib, or parts of it, as Tapestry components. Or maybe Stitches could be used as a starting point. This way, I would think, you could use any JSR 170 compliant CMS to manage your content, and could integrate the content in a Tapestry based site using this new component library. What do people think? Is that realistic? Would it work? Would such a component library be of interest to anyone? Lutz On 7/1/06, Mike Grundvig [EMAIL PROTECTED] wrote: Has anyone integrated any sort of CMS tool with Tapestry? I've looked into Magnolia and several others, but all seem to require an uphill battle if they are to be tied into Tapestry and I was wondering if someone else has already done this. Thanks! Michael Grundvig - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: CMS Integration
I left this vague to allow any sort of response. Basically, the closer it gets to something like Magnolia the better but anything someone else has done would be a start. Michael Grundvig Electrotank, Inc http://www.electrotank.com - Original Message - From: Phillip Rhodes [EMAIL PROTECTED] To: Tapestry users users@tapestry.apache.org Sent: Wednesday, July 05, 2006 10:59 AM Subject: Re: CMS Integration What are the basic requirements? CMS is a many-faceted beast. Has anyone integrated any sort of CMS tool with Tapestry? I've looked into Magnolia and several others, but all seem to require an uphill battle if they are to be tied into Tapestry and I was wondering if someone else has already done this. Thanks! Michael Grundvig - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: CMS Integration
Michael, The tapestry library that I developed (called stitches) has some cms functionality. It is a suite of tapestry components that provide creation,modify, search (using lucene) of a repository. The idea when I started stitches was to make it so stitches could work with jackrabbit,alfresco, etc. using the java cms api. However, as projects go, I found it quicker to just write the content out to the filesystem finish the project. Since all access to the repository is through an interface, and I have a prevayler and hibernate based implementation, it would not be too difficult to implement one for jackrabbit or some other cms api. The basic problem that I was trying to solve with my library is that there are different business objects (e.g. products, categories) that need to have content associated to them (could be a pdf, html). This library gave me a reusable means by which to associate these content items to the business objects. For example, one application that I have allows users to upload and share images. The images get uploaded to the stitch repo and everyone can search the repo and use the images to build flash galleries or associated the images with biz objects (their businesses, or roadtrips, etc). Let me know if there is anything would you find useful. I may be willing to do some coding around implementing a jackrabbit (or other) cms to stitches if I had someone to help out. Thanks Phillip I left this vague to allow any sort of response. Basically, the closer it gets to something like Magnolia the better but anything someone else has done would be a start. Michael Grundvig Electrotank, Inc http://www.electrotank.com - Original Message - From: Phillip Rhodes [EMAIL PROTECTED] To: Tapestry users users@tapestry.apache.org Sent: Wednesday, July 05, 2006 10:59 AM Subject: Re: CMS Integration What are the basic requirements? CMS is a many-faceted beast. Has anyone integrated any sort of CMS tool with Tapestry? I've looked into Magnolia and several others, but all seem to require an uphill battle if they are to be tied into Tapestry and I was wondering if someone else has already done this. Thanks! Michael Grundvig - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: CMS Integration
What are the basic requirements? CMS is a many-faceted beast. Has anyone integrated any sort of CMS tool with Tapestry? I've looked into Magnolia and several others, but all seem to require an uphill battle if they are to be tied into Tapestry and I was wondering if someone else has already done this. Thanks! Michael Grundvig - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
