Comments on: Organization of BC4J – Domain (EO) and Business (VO) package http://technology.amis.nl/2004/10/18/organization-of-bc4j-domain-eo-and-business-vo-package/?utm_source=rss&utm_medium=rss&utm_campaign=organization-of-bc4j-domain-eo-and-business-vo-package Fri, 12 Apr 2013 10:04:09 +0000 hourly 1 http://wordpress.org/?v=3.5.1 By: Lucas http://technology.amis.nl/2004/10/18/organization-of-bc4j-domain-eo-and-business-vo-package/#comment-966 Lucas Wed, 20 Oct 2004 06:56:17 +0000 /?p=215#comment-966 Martijn,

I had planned on sending you an email to tell you about JHeadstart’s inability to make use of two different BC4J packages. I realized it Monday night as I drove home. I think it is a very simple addition to the JHeadstart generator extensions:
- define an additional Service Level property, similar to persistenceBase, something like Entity Objects persistence Base
- change in the JAG XSLTs the way the eoDOC variable is derived

We might be able to trick the JAG by copying the EO-xml files to the same directory as the VO-xml files, but to me that is a dirty solution and I am not sure how BC4J will react. So I suggest we concentrate on this small change in the generator.

Lucas

]]> By: Martijn Peters http://technology.amis.nl/2004/10/18/organization-of-bc4j-domain-eo-and-business-vo-package/#comment-965 Martijn Peters Tue, 19 Oct 2004 21:56:51 +0000 /?p=215#comment-965 Lucas,

After some struggling with the wizards I finally succeeded to use an enterprise entity objects package in another project.

This are the steps for JDeveloper 10g in more detail:
- open a new Business Component project …
- … define entity objects without view objects and appmodule
- add a new Business Components Archive – Deployment Profile and deploy it
- open a second Business Compontents project …
- … do not define any entity objects, view objects or appmodule!
- add the middle-tier archive of the first project as a project library in the second project
- right-click on .jpx file in the System Manager and select Import Business Components …
- … navigate to the Business Components .xml file in the middle-tier archive
- once again right-click on the .jpx file and select New Default Data Components …
- … select the package name of the second project and select entity objects of the first project
- … now create view objects and appmodule to be used in the second project

Now remains the question: how to continue with JHeadstart?
When right-clicking the appmodule the New JHeadstart Application Structure File is grayed out.
JHeadstart cannot store JHeadstart properties in the read-only entity objects .xml files (and it should not be ;-)
Can we fake JHeadstart by copying the .xml files from the first project to the second project?????

kind regards,
Martijn

]]>