Naming convention is a good idea indeed. As at the minimum we'll need
to accommodate the existing multi-domain users. So probably make it
cayenne-domainname.xml.
Andrus
On Nov 26, 2009, at 12:15 PM, Evgeny Ryabitskiy (JIRA) wrote:
>
> [ https://issues.apache.org/jira/browse/CAY-1318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12782828
> #action_12782828 ]
>
> Evgeny Ryabitskiy commented on CAY-1318:
> ----------------------------------------
>
> Good idea. I also have no need in multiple DataDomains sharing same
> file.
>
> My problem in multiple domains from multiple files... Right now I am
> trying to solve it... still don't have nice solution :(
> Really need a "Domain Merger" right now.. or maybe yesterday...
>
> I can suggest one thing about configuration names.
> We can add some name pattern to such cayenne files like *-
> cayenne.xml (Ex.: myProject-cayenne.xml)
> or *.cay.xml (Ex.: myProject.cay.xml ) Or something else.. It
> will be nice and more standardized.
>
> Adding some standards is a good practice ;)
>
>> Cayenne configuration to support a single DataDomain
>> ----------------------------------------------------
>>
>> Key: CAY-1318
>> URL: https://issues.apache.org/jira/browse/CAY-1318
>> Project: Cayenne
>> Issue Type: Task
>> Components: Cayenne Core Library, CayenneModeler GUI
>> Affects Versions: 3.1M1
>> Reporter: Andrus Adamchik
>> Assignee: Andrus Adamchik
>> Fix For: 3.1M1
>>
>>
>> Multi-datadomain runtime configurations offer no advantage over
>> multiple configurations with a single domain each. So going to
>> change the project structure to only support a single DataDomain. A
>> Modeler will have project upgrader that will split multi-domain
>> projects into multiple single domain projects (e.g. cayenne1.xml,
>> cayenne2.xml, etc).
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
>
This archive was generated by hypermail 2.0.0 : Thu Nov 26 2009 - 05:39:12 EST