Hippo CMS
Locked
1234
1234
Re: Hippo CMS
 
|
Hi Sascha,
Any help would of course be very much appreciated. I think regardless of what approach we take, everyone is mostly in agreement that we will be integrating with Jackrabbit or more importantly we will be making use of the JCR interface (in theory the actual JCR implementation should be irrelevant). One thing I'm fairly sure we will need is a JAAS authentication module (and probably authorization) that we can plug in to the jackrabbit repository so that it can authenticate users via OFBiz. That should be fairly straightforward I think, I'm less certain about what an authorization mechanism would look like. I guess we're also going to need to some sort of session provider interface that allows OFBiz to retrieve sessions from either an embedded repo or remote server repo and once again, it needs to be able to work with any JCR implementation. I'm not entirely sure what that would look like at this stage but any thoughts on the topic would be useful. Most of the other questions come back to the content model and who controls it, will it be OFBiz or a random CMS or perhaps they will have separate models with some sort of jackrabbit internal synchronization between the two? We need to look at these options and understand the pros and cons of each before we can move forward with any sort of certainty. Regards Scott On 22/06/2010, at 6:26 PM, Sascha Rodekamp wrote: > +1 > > i like the idea integrating a full featured CMS in ofbiz, a few weeks ago we > started working with JCR but i think the Hippo way is a good one too :-) > So Scott i would volunteer to help you :-) ... > > Have a good day > Sascha > > 2010/6/19 Scott Gray <[hidden email]> > >> Anybody using or considered using Hippo CMS (onehippo.org) in conjunction >> with OFBiz? >> - Apache Licensed >> - Uses Jackrabbit as its repository >> - Supports Versioning, Internationalization, Publishing Workflows and more >> >> We could start out by using Hippo's UI to manage content and retrieve it >> for display within OFBiz using the JCR API. As the various document types >> needed by the OFBiz base applications begin to take shape we could look at >> ways to allow the content to be modified directly from within OFBiz (once >> again using the JCR API). >> >> Any thoughts, alternatives, ideas or whatever would be appreciated. I'm >> considering working on a POC in my spare time, not sure how long that might >> take at this stage. I already have a copy of Hippo running inside OFBiz but >> that was just a matter of expanding their WAR distribution and wrapping it >> in a component, next step would be gaining access to the repo from OFBiz >> code. >> >> Thanks >> Scott >> >> HotWax Media >> http://www.hotwaxmedia.com > > > > > -- > Sascha Rodekamp > Lynx-Consulting GmbH > Johanniskirchplatz 6 > D-33615 Bielefeld > http://www.lynx.de |
smime.p7s (3K)
Re: Hippo CMS
|
|
Re: Hippo CMS
|
|
Re: Hippo CMS
|
|
On 24/06/2010, at 12:06 PM, Ean Schuessler wrote:
> Scott Gray wrote: >> Not necessarily, OFBiz need only know the location of a given piece of >> content and how to interact with it. So instead of entities being >> related to Content records, they would instead have pointers to >> locations in the content repository. > Correct, from the OFBiz side. From the CMS side, the content will be a > collection of leaf nodes and the connective structure that organize them > will be invisible. That was my point. Queries across these two disparate > repositories will also be more painful. This is why personally I would prefer it if we didn't go the route of trying to support any JSR-283 compliant CMS. I would prefer it if we selected a single CMS and then basically used it as a stand-in while we work to create tightly integrated CMS features from within OFBiz. Because hippo is Apache licensed, we can take their features and bring them into OFBiz one by one until we simply don't need their app anymore. If people want to be able to use other CMS apps then they would need to take care of mapping, mirroring, synchronizing and locking between the two repo's themselves. I really think that trying to support any CMS is just too bug of bite for us to sallow at this stage. So in short I agree with you that OFBiz should define the content model, but perhaps we should borrow from the work of others (i.e. hippo). >> The answer to that question is up to the individual, if OFBiz offers a >> blog, wiki, forum or whatever it doesn't mean that anyone is going to >> be forced to use it. If any of those things were to be developed it >> would only be because someone needed it, same as anything in else >> OFBiz. OFBiz has accounting functionality, but that doesn't prevent >> anyone from using alternative accounting systems. > My point is that JSR-283 doesn't seem to provide mech leverage in terms > of actual blog/wiki/forum code. Are you aware of any frameworks suitable for use in OFBiz that do? >> How did you just segue into JSR-286? >> > Hippo CMS is a JSR-286 provider. Ah okay sorry, I doubt that we'd actually try and use it in that manner though. >> You're welcome to work on that but it certainly won't be anything I'm >> going to touch. To borrow from you a bit, our content application is a >> maze of confusion and dead code. The best I would be willing to offer >> is migration services for importing data from the Content model into >> the new repository. > I think we are in agreement that a JSR-283 wrapper is a difficult and > not terribly interesting thing to pursue. Yeah I'd say it might be worthwhile if the existing content stuff were in better shape but I just don't see it being worth the effort unfortunately. Regards Scott |
Re: Hippo CMS
|
|
Re: Hippo CMS
|
|
On 24/06/2010, at 4:25 PM, Raj Saini wrote:
> >> of actual blog/wiki/forum code. >> >>> How did you just segue into JSR-286? >>> >>> >> Hippo CMS is a JSR-286 provider. >> > I don't think Hippo is JSR-186 provider. Hippo Portal is using Apache Jetspeed which is JSR 168/286 (Portlet API) provider and Hippo is JSR 170/283 provider. > They have a few different products available, it's not entirely clear to me where they overlap: CMS, Site Toolkit, JetSpeed Integration and Portal. Regards Scott |
Re: Hippo CMS
|
|
Re: Hippo CMS
Administrator
|
Re: Hippo CMS
|
|
Re: Hippo CMS
|
|
Re: Hippo CMS
|
|
Re: Hippo CMS
|
|
Re: Hippo CMS
|
|
In reply to this post by Brett
Hi Brett,
I was looking at CMS 7 (which overlays Repository 2). I didn't really look too closely at their other stuff since CMS 7 was really all I was interested in. Regards Scott On 8/07/2010, at 4:27 PM, Brett Palmer wrote: > Scott, > > I like the idea of integrating with existing CMS applications. When we are > talking about hippo what of their various products are we considering here: > > Hippo CMS7 > Hippo Repository 2 > Hippo Site Toolkit 2 > or > Hippo Portal 2.0 > > from www.onehippo.org > > > Brett > > On Fri, Jun 18, 2010 at 7:57 PM, Scott Gray <[hidden email]>wrote: > >> Anybody using or considered using Hippo CMS (onehippo.org) in conjunction >> with OFBiz? >> - Apache Licensed >> - Uses Jackrabbit as its repository >> - Supports Versioning, Internationalization, Publishing Workflows and more >> >> We could start out by using Hippo's UI to manage content and retrieve it >> for display within OFBiz using the JCR API. As the various document types >> needed by the OFBiz base applications begin to take shape we could look at >> ways to allow the content to be modified directly from within OFBiz (once >> again using the JCR API). >> >> Any thoughts, alternatives, ideas or whatever would be appreciated. I'm >> considering working on a POC in my spare time, not sure how long that might >> take at this stage. I already have a copy of Hippo running inside OFBiz but >> that was just a matter of expanding their WAR distribution and wrapping it >> in a component, next step would be gaining access to the repo from OFBiz >> code. >> >> Thanks >> Scott >> >> HotWax Media >> http://www.hotwaxmedia.com |
Re: Hippo CMS
|
|
In reply to this post by Michael Xu (xudong)
Hi Michael,
The idea was to add hippo as a component and use their webapp as an interim CMS while we build out similar functionality in OFBiz. OFBiz would use the JCR API to interact with the underlying repository. In terms of progress... none. In my spare time I'll be playing around with a jackrabbit integration for OFBiz and reading all the articles I can find. I feel like I need to better understand the JCR and content models in general before doing anything concrete. Regards Scott On 8/07/2010, at 5:27 PM, Michael Xu (xudong) wrote: > "Integrating" here means to put Hippo as a ofbiz component or let it as a > standalone application but integrating over data/service layer? > > -- > Regards, > Michael Xu (xudong) > www.wizitsoft.com | Office: (8610) 6267 0615 ext 806 | Mobile: (86) 135 0135 > 9807 | Fax: (8610) 62670096 > > > On Thu, Jul 8, 2010 at 12:27 PM, Brett Palmer <[hidden email]>wrote: > >> Scott, >> >> I like the idea of integrating with existing CMS applications. When we are >> talking about hippo what of their various products are we considering here: >> >> Hippo CMS7 >> Hippo Repository 2 >> Hippo Site Toolkit 2 >> or >> Hippo Portal 2.0 >> >> from www.onehippo.org >> >> >> Brett >> >> On Fri, Jun 18, 2010 at 7:57 PM, Scott Gray <[hidden email] >>> wrote: >> >>> Anybody using or considered using Hippo CMS (onehippo.org) in >> conjunction >>> with OFBiz? >>> - Apache Licensed >>> - Uses Jackrabbit as its repository >>> - Supports Versioning, Internationalization, Publishing Workflows and >> more >>> >>> We could start out by using Hippo's UI to manage content and retrieve it >>> for display within OFBiz using the JCR API. As the various document >> types >>> needed by the OFBiz base applications begin to take shape we could look >> at >>> ways to allow the content to be modified directly from within OFBiz (once >>> again using the JCR API). >>> >>> Any thoughts, alternatives, ideas or whatever would be appreciated. I'm >>> considering working on a POC in my spare time, not sure how long that >> might >>> take at this stage. I already have a copy of Hippo running inside OFBiz >> but >>> that was just a matter of expanding their WAR distribution and wrapping >> it >>> in a component, next step would be gaining access to the repo from OFBiz >>> code. >>> >>> Thanks >>> Scott >>> >>> HotWax Media >>> http://www.hotwaxmedia.com >> |
Re: Hippo CMS
|
|
Re: Hippo CMS
|
|
Hi Michael,
Personally, I wouldn't do anymore than the most basic CMS work with the existing OFBiz component, but maybe I'm biased because I want to see it replaced :-) In regards to working together, my spare time is pretty limited so I doubt that I'll be working very fast and probably nowhere near fast enough for your needs. If people are interested in helping out with my POC then we can always consider creating a jackrabbit branch in the OFBiz repo that people can use to collaborate. The main reason I'm looking at a direct Jackrabbit integration is simply for learning purposes and to get a better understanding of what the best long term approach will be, there is every chance that it would never get merged back into the trunk if we later decide to take a different route. Regards Scott On 8/07/2010, at 6:07 PM, Michael Xu (xudong) wrote: > hi Scott, > > Thanks. > > We are customizing ofbiz for a customer here in China. Party, Order, > Agreement, AP/AR, Birt, Catalog are in the current scope and we feel very > comfortable with the flexibility offered by ofbiz. Now customer needs CMS. > However, current CMS component is not that ready in ofbiz. We are evaluating > which way to go: > > 1) enhance current ofbiz CMS component > 2) embed a 3-party CMS as a component > 3) integrate with a standalone 3-party CMS > > Option 1 seems very risky, as we have to re-invent the CMS wheel; Option 3 > seems also very risky, as there are many integration points, like > user/permission, etc. Now I tend to using option 2 just like what you are > doing. Maybe we can work together on this. > > -- > Regards, > Michael Xu (xudong) > > > On Thu, Jul 8, 2010 at 1:52 PM, Scott Gray <[hidden email]>wrote: > >> Hi Michael, >> >> The idea was to add hippo as a component and use their webapp as an interim >> CMS while we build out similar functionality in OFBiz. OFBiz would use the >> JCR API to interact with the underlying repository. >> >> In terms of progress... none. In my spare time I'll be playing around with >> a jackrabbit integration for OFBiz and reading all the articles I can find. >> I feel like I need to better understand the JCR and content models in >> general before doing anything concrete. >> >> Regards >> Scott >> >> On 8/07/2010, at 5:27 PM, Michael Xu (xudong) wrote: >> >>> "Integrating" here means to put Hippo as a ofbiz component or let it as a >>> standalone application but integrating over data/service layer? >>> >>> -- >>> Regards, >>> Michael Xu (xudong) >>> www.wizitsoft.com | Office: (8610) 6267 0615 ext 806 | Mobile: (86) 135 >> 0135 >>> 9807 | Fax: (8610) 62670096 >>> >>> >>> On Thu, Jul 8, 2010 at 12:27 PM, Brett Palmer <[hidden email] >>> wrote: >>> >>>> Scott, >>>> >>>> I like the idea of integrating with existing CMS applications. When we >> are >>>> talking about hippo what of their various products are we considering >> here: >>>> >>>> Hippo CMS7 >>>> Hippo Repository 2 >>>> Hippo Site Toolkit 2 >>>> or >>>> Hippo Portal 2.0 >>>> >>>> from www.onehippo.org >>>> >>>> >>>> Brett >>>> >>>> On Fri, Jun 18, 2010 at 7:57 PM, Scott Gray <[hidden email] >>>>> wrote: >>>> >>>>> Anybody using or considered using Hippo CMS (onehippo.org) in >>>> conjunction >>>>> with OFBiz? >>>>> - Apache Licensed >>>>> - Uses Jackrabbit as its repository >>>>> - Supports Versioning, Internationalization, Publishing Workflows and >>>> more >>>>> >>>>> We could start out by using Hippo's UI to manage content and retrieve >> it >>>>> for display within OFBiz using the JCR API. As the various document >>>> types >>>>> needed by the OFBiz base applications begin to take shape we could look >>>> at >>>>> ways to allow the content to be modified directly from within OFBiz >> (once >>>>> again using the JCR API). >>>>> >>>>> Any thoughts, alternatives, ideas or whatever would be appreciated. >> I'm >>>>> considering working on a POC in my spare time, not sure how long that >>>> might >>>>> take at this stage. I already have a copy of Hippo running inside >> OFBiz >>>> but >>>>> that was just a matter of expanding their WAR distribution and wrapping >>>> it >>>>> in a component, next step would be gaining access to the repo from >> OFBiz >>>>> code. >>>>> >>>>> Thanks >>>>> Scott >>>>> >>>>> HotWax Media >>>>> http://www.hotwaxmedia.com >>>> >> >> |
Re: Hippo CMS
|
|
Re: Hippo CMS
|
|
Re: Hippo CMS
|
|
Okay well cool, I'll go ahead and create a branch at some point, I know Sascha has expressed interest as well so we may as well get the ball rolling.
Regards Scott On 8/07/2010, at 11:54 PM, Adrian Crum wrote: > My spare time is very limited too, but I would be willing to help. > > -Adrian > > --- On Thu, 7/8/10, Scott Gray <[hidden email]> wrote: > >> From: Scott Gray <[hidden email]> >> Subject: Re: Hippo CMS >> To: [hidden email] >> Date: Thursday, July 8, 2010, 12:04 AM >> Hi Michael, >> >> Personally, I wouldn't do anymore than the most basic CMS >> work with the existing OFBiz component, but maybe I'm biased >> because I want to see it replaced :-) >> >> In regards to working together, my spare time is pretty >> limited so I doubt that I'll be working very fast and >> probably nowhere near fast enough for your needs. >> >> If people are interested in helping out with my POC then we >> can always consider creating a jackrabbit branch in the >> OFBiz repo that people can use to collaborate. The >> main reason I'm looking at a direct Jackrabbit integration >> is simply for learning purposes and to get a better >> understanding of what the best long term approach will be, >> there is every chance that it would never get merged back >> into the trunk if we later decide to take a different >> route. >> >> Regards >> Scott >> >> On 8/07/2010, at 6:07 PM, Michael Xu (xudong) wrote: >> >>> hi Scott, >>> >>> Thanks. >>> >>> We are customizing ofbiz for a customer here in China. >> Party, Order, >>> Agreement, AP/AR, Birt, Catalog are in the current >> scope and we feel very >>> comfortable with the flexibility offered by ofbiz. Now >> customer needs CMS. >>> However, current CMS component is not that ready in >> ofbiz. We are evaluating >>> which way to go: >>> >>> 1) enhance current ofbiz CMS component >>> 2) embed a 3-party CMS as a component >>> 3) integrate with a standalone 3-party CMS >>> >>> Option 1 seems very risky, as we have to re-invent the >> CMS wheel; Option 3 >>> seems also very risky, as there are many integration >> points, like >>> user/permission, etc. Now I tend to using option 2 >> just like what you are >>> doing. Maybe we can work together on this. >>> >>> -- >>> Regards, >>> Michael Xu (xudong) >>> >>> >>> On Thu, Jul 8, 2010 at 1:52 PM, Scott Gray <[hidden email]>wrote: >>> >>>> Hi Michael, >>>> >>>> The idea was to add hippo as a component and use >> their webapp as an interim >>>> CMS while we build out similar functionality in >> OFBiz. OFBiz would use the >>>> JCR API to interact with the underlying >> repository. >>>> >>>> In terms of progress... none. In my spare >> time I'll be playing around with >>>> a jackrabbit integration for OFBiz and reading all >> the articles I can find. >>>> I feel like I need to better understand the JCR >> and content models in >>>> general before doing anything concrete. >>>> >>>> Regards >>>> Scott >>>> >>>> On 8/07/2010, at 5:27 PM, Michael Xu (xudong) >> wrote: >>>> >>>>> "Integrating" here means to put Hippo as a >> ofbiz component or let it as a >>>>> standalone application but integrating over >> data/service layer? >>>>> >>>>> -- >>>>> Regards, >>>>> Michael Xu (xudong) >>>>> www.wizitsoft.com | Office: (8610) 6267 0615 >> ext 806 | Mobile: (86) 135 >>>> 0135 >>>>> 9807 | Fax: (8610) 62670096 >>>>> >>>>> >>>>> On Thu, Jul 8, 2010 at 12:27 PM, Brett Palmer >> <[hidden email] >>>>> wrote: >>>>> >>>>>> Scott, >>>>>> >>>>>> I like the idea of integrating with >> existing CMS applications. When we >>>> are >>>>>> talking about hippo what of their various >> products are we considering >>>> here: >>>>>> >>>>>> Hippo CMS7 >>>>>> Hippo Repository 2 >>>>>> Hippo Site Toolkit 2 >>>>>> or >>>>>> Hippo Portal 2.0 >>>>>> >>>>>> from www.onehippo.org >>>>>> >>>>>> >>>>>> Brett >>>>>> >>>>>> On Fri, Jun 18, 2010 at 7:57 PM, Scott >> Gray <[hidden email] >>>>>>> wrote: >>>>>> >>>>>>> Anybody using or considered using >> Hippo CMS (onehippo.org) in >>>>>> conjunction >>>>>>> with OFBiz? >>>>>>> - Apache Licensed >>>>>>> - Uses Jackrabbit as its repository >>>>>>> - Supports Versioning, >> Internationalization, Publishing Workflows and >>>>>> more >>>>>>> >>>>>>> We could start out by using Hippo's UI >> to manage content and retrieve >>>> it >>>>>>> for display within OFBiz using the JCR >> API. As the various document >>>>>> types >>>>>>> needed by the OFBiz base applications >> begin to take shape we could look >>>>>> at >>>>>>> ways to allow the content to be >> modified directly from within OFBiz >>>> (once >>>>>>> again using the JCR API). >>>>>>> >>>>>>> Any thoughts, alternatives, ideas or >> whatever would be appreciated. >>>> I'm >>>>>>> considering working on a POC in my >> spare time, not sure how long that >>>>>> might >>>>>>> take at this stage. I already >> have a copy of Hippo running inside >>>> OFBiz >>>>>> but >>>>>>> that was just a matter of expanding >> their WAR distribution and wrapping >>>>>> it >>>>>>> in a component, next step would be >> gaining access to the repo from >>>> OFBiz >>>>>>> code. >>>>>>> >>>>>>> Thanks >>>>>>> Scott >>>>>>> >>>>>>> HotWax Media >>>>>>> http://www.hotwaxmedia.com >>>>>> >>>> >>>> >> >> > > > |
Re: Hippo CMS
|
|
| Free forum by Nabble | Edit this page |