-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Yup. The hard part is to work with in the confines of ofbiz framework.
takes a lot of time to chart the flow of drupal then apply it to ofbiz.

Milind Parikh sent the following on 1/23/2009 4:05 PM:
> I did not mean integration with an PHP based application. Just the design
> philosophy of the data structures and the concept of modules in drupal (of
> course, this is easier in a dynamically typed language like php).
> 
> Regards
> - Milind
> 
> 
> On Fri, Jan 23, 2009 at 3:45 PM, BJ Freeman <bjf...@free-man.net> wrote:
> 
> the problem with integration of a PHP based application is it is a
> completely separate application and coding style.
> 
> Milind Parikh sent the following on 1/22/2009 12:34 PM:
>>>> There is a lot of interest in CMS. I would suggest also looking at
> Drupal's
>>>> way of doing CMS (drupal,org) as I believe that it is very interesting
> and
>>>> flexible. However it is more suited to the web (as opposed to enterprise
>>>> content management).
>>>>
>>>> -- Milind
>>>>
>>>>
>>>> On Thu, Jan 22, 2009 at 12:27 PM, Bruno Busco <bruno.bu...@gmail.com>
> wrote:
>>>>> Hi Al,
>>>>> I do not want to hijack the thread but I think there is more interest in
>>>>> CMS
>>>>> than you could believe.
>>>>>
>>>>> There were also discussions on using OFBiz CMS to host the OFBiz Web
> site
>>>>> itself.
>>>>> This would be great and, may be, now that it seems you are back on-line,
> we
>>>>> could have better chance.
>>>>>
>>>>> Thank you,
>>>>> Bruno
>>>>>
>>>>>
>>>>>
>>>>> 2009/1/22 Al Byers <bye...@automationgroups.com>
>>>>>
>>>>>> Angelo,
>>>>>>
>>>>>> I implemented the CMS years ago per David's design. At the time, I
>>>>> thought
>>>>>> it would be wise to have a single service, persistContentAndAssoc,
> which
>>>>>> did
>>>>>> everything - creating and updating, all types of media and all possible
>>>>>> repositories (ie. database, filesystem, etc). I am not convinced that
> it
>>>>>> would not be nice to have such a tool, even though it tends to go
> against
>>>>>> the "OFBiz way" (I claim that for a T-shirt). I don't think
>>>>>> persistContentAndAssoc is that tool, though I would love someone to
>>>>> improve
>>>>>> on it or simplify it.
>>>>>>
>>>>>> Not having a clear API for working with the CMS is its greatest
> drawback,
>>>>> I
>>>>>> think. Saner heads than mine have broken the persist process into
>>>>> multiple
>>>>>> steps. I drew from what they have done and here is how I recently did a
>>>>>> simple text persist:
>>>>>>               ...
>>>>>>               String localeString = (String)entry.getKey();
>>>>>>                String textData = (String)entry.getValue();
>>>>>>                // Create new content
>>>>>>                mapIn = new HashMap();
>>>>>>                mapIn.put("localeString", localeString);
>>>>>>                mapIn.put("objectInfo", textData);
>>>>>>                mapIn.put("userLogin", userLogin);
>>>>>>                mapIn.put("dataResourceTypeId", "SHORT_TEXT");
>>>>>>                mapIn.put("mimeTypeId", "text/plain");
>>>>>>                result = dispatcher.runSync("createDataResource",
> mapIn);
>>>>>>                String dataResourceId =
>>>>>> (String)result.get("dataResourceId");
>>>>>>
>>>>>>                mapIn = new HashMap();
>>>>>>                mapIn.put("localeString", localeString);
>>>>>>                mapIn.put("textData", textData);
>>>>>>                mapIn.put("description", description);
>>>>>>                mapIn.put("userLogin", userLogin);
>>>>>>                mapIn.put("dataResourceId", dataResourceId);
>>>>>>                result = dispatcher.runSync("createContent", mapIn);
>>>>>>                String contentId = (String)result.get("contentId");
>>>>>>
>>>>>>
>>>>>>                // Create assoc to SurveyQuestionOption
>>>>>>                // Angelo, note that this is not the ContentAssoc entity
>>>>>> that you would use.
>>>>>>                // I think you would just use the createContentAssoc
>>>>> service
>>>>>> here instead
>>>>>>                // And I would use FastMaps because that is the OFBiz
> way.
>>>>>>                mapIn = new HashMap();
>>>>>>                mapIn.put("localeString", localeString);
>>>>>>                mapIn.put("contentId", contentId);
>>>>>>                mapIn.put("surveyAnswerOptionId", surveyAnswerOptionId);
>>>>>>                mapIn.put("userLogin", userLogin);
>>>>>>                Map result2 =
>>>>>> dispatcher.runSync("createSurveyAnswerOptionContentAssoc", mapIn);
>>>>>>
>>>>>> In my mind, that is still a lot of code, when there are only a few
> pieces
>>>>>> of
>>>>>> data, but you might want to stick to something like this for now.
>>>>>>
>>>>>> Sorry I can't be of more help, but I have forgotten much of what I did
>>>>>> before. With Hans taking an interest in CMS, maybe things will get
>>>>>> improved.
>>>>>>
>>>>>> -Al
>>>>>>
>>>>>> On Thu, Jan 22, 2009 at 12:00 PM, Angelo Matarazzo <
>>>>>> matarazzoang...@gmail.com> wrote:
>>>>>>
>>>>>>> Hi,
>>>>>>> I am following the debate between Hans and David about Content
>>>>> Component.
>>>>>>> I am looking at a way to upload a resource and integrate it in
>>>>> database.
>>>>>>> In Content Component there is a java service: persistContentAndAssoc
>>>>>>  which
>>>>>>> is called very often.
>>>>>>> Instead in Party Component it seems that this service is  replaced by
>>>>>>> uploadPartyContentFile which don't call "persistContentAndAssoc" but
>>>>>> other
>>>>>>> services.
>>>>>>> Why?
>>>>>>> To upload a file it is better to follow  Party Component?
>>>>>>> "persistContentAndAssoc" is been replaced in the system?
>>>>>>> Thank you.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> View this message in context:
>>>>>>> http://www.nabble.com/Content-Service-tp21610839p21610839.html
>>>>>>> Sent from the OFBiz - User mailing list archive at Nabble.com.
>>>>>>>
>>>>>>>
>>

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFJemWVrP3NbaWWqE4RAsigAJ4rGD5YqIdr3XLvQIFOUaHAjlmFNACfX75b
AEnl5fRRyStCdMp07kTPX7Y=
=IlTd
-----END PGP SIGNATURE-----

Reply via email to