You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by "chris snow (JIRA)" <ji...@apache.org> on 2010/02/25 06:52:28 UTC

[jira] Commented: (OFBIZ-3505) Data model to have Content and Party applications not dependant on other applications

    [ https://issues.apache.org/jira/browse/OFBIZ-3505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12838195#action_12838195 ] 

chris snow commented on OFBIZ-3505:
-----------------------------------

Another approach would be to:

h2. Refactor content component:

1) rename the existing content component in applications to contentext
2) create a new component in framework called content
3) move all the core content entities to a new content component in framework.  we would need to decide on what entities would stay in content.  my initial list is below.

If any of the core content entities have dependencies on party components, we would need to refactor the party component too.

h2. Refactor party component

1) rename the existing party component in applications to partyext
2) create a new component in framework called party
3) move the core party entities (i.e. those depended on my content) to the new party component in framework.

The above approach would not break existing ofbiz functionality, and would allow ofbiz to work standalone.  The next step would be to migrate the core content and party (if applicable) screens to the new framework components.

h2. Suggested Framework content component entities

view AssocRevisionItemView
view ContentAssocRevisionItemView
view MaxRevisionItemView
view MaxContentApprovalView
view ContentAssocOptViewFrom
view ContentRevisionItemAndContentApprovalView

entity Content
view ContentAndRole
entity ContentApproval
entity ContentAssoc
view ContentAssocDataResourceViewFrom
view ContentAssocDataResourceViewTo
entity ContentAssocPredicate
view ContentAssocViewFrom
view ContentAssocViewTo
entity ContentAttribute
view ContentDataResourceView
entity ContentMetaData
entity ContentOperation
entity ContentPurpose
entity ContentPurposeOperation
entity ContentPurposeType
entity ContentRevision
entity ContentRevisionItem
entity ContentRole
entity ContentType
entity ContentTypeAttr
view SubContentDataResourceView

entity AudioDataResource
entity CharacterSet
entity DataCategory
entity DataResource
entity DataResourceAttribute
view DataResourceContentView
entity DataResourceMetaData
entity DataResourcePurpose
entity DataResourceRole
entity DataResourceType
entity DataResourceTypeAttr
entity DataTemplateType
entity ElectronicText
entity FileExtension
entity ImageDataResource
entity MetaDataPredicate
entity MimeType
entity MimeTypeHtmlTemplate
entity OtherDataResource
entity VideoDataResource

entity Document
entity DocumentAttribute
entity DocumentType
entity DocumentTypeAttr

entity WebPreferenceType
entity WebUserPreference

extend-entity WebPage
entity WebSiteContent
view WebSiteAndContent
entity WebSiteContentType
entity WebSitePathAlias
entity WebSitePublishPoint
entity WebSiteRole
view ContentAssocAndContentPurpose

h2. Suggested application contentext component entities

entity Survey
entity SurveyApplType
entity SurveyMultiResp
entity SurveyMultiRespColumn
entity SurveyPage
entity SurveyQuestion
view SurveyQuestionAndAppl
entity SurveyQuestionAppl
entity SurveyQuestionCategory
entity SurveyQuestionOption
entity SurveyQuestionType
entity SurveyResponse
view SurveyResponseAndAnswer
entity SurveyResponseAnswer
entity SurveyTrigger 

h2. Next steps

If the committers agree on this approach, we could have a standalone ofbiz very soon (minus some content and party management screens)

> Data model to have Content and Party applications not dependant on other applications
> -------------------------------------------------------------------------------------
>
>                 Key: OFBIZ-3505
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-3505
>             Project: OFBiz
>          Issue Type: Sub-task
>          Components: ALL APPLICATIONS
>            Reporter: Bruno Busco
>            Priority: Minor
>         Attachments: ofbiz_core.patch
>
>
> The patch attached is the work I did to try to have the Content and Party applications not dependent on the other applications.
> The patch only changes the data model and not the application code also so applying the patch results in a not working OFBiz.
> The purpose of the patch is to describe the solution I found to remove the mentioned dependencies and, if agreed, could be the base to change the code accordingly.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.