You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cayenne.apache.org by Aristedes Maniatis <ar...@maniatis.org> on 2007/10/24 11:52:05 UTC
Re: [JIRA] Created: (CAY-900) Create CayenneModeler Swing UI for managing callbacks and lifecycle listeners
On 24/10/2007, at 7:19 PM, Tore Halset wrote:
> Nice. Would it be possible for the merge-stuff that I am working on
> to determine the key for the comment value that should be merged to
> the database?
Sorry, not 100% sure about the scope of what you are working on. I've
looked at it briefly a week ago, but that's all. I'm working on the
idea of a tag like this:
<info name="keyname" value="sjdhfksdjhfksjhdf"
isRuntimeVisible="true" />
which could be nested inside <obj-attribute> <obj-relationship> or
<obj-entity>, etc. The keyname might be 'javadoc' or anything else
really, so there could be some reserved keys for various specific
jobs. Is that what you meant?
I'm also thinking that maybe the value needs to be a CDATA to
accommodate multiline comments which end up (say) as javadocs.
Ari Maniatis
-------------------------->
Aristedes Maniatis
phone +61 2 9660 9700
PGP fingerprint 08 57 20 4B 80 69 59 E2 A9 BF 2D 48 C2 20 0C C8
Re: [JIRA] Created: (CAY-900) Create CayenneModeler Swing UI for
managing callbacks and lifecycle listeners
Posted by Tore Halset <ha...@pvv.ntnu.no>.
On Oct 24, 2007, at 11:52 , Aristedes Maniatis wrote:
>
> On 24/10/2007, at 7:19 PM, Tore Halset wrote:
>
>> Nice. Would it be possible for the merge-stuff that I am working
>> on to determine the key for the comment value that should be
>> merged to the database?
>
> Sorry, not 100% sure about the scope of what you are working on.
> I've looked at it briefly a week ago, but that's all. I'm working
> on the idea of a tag like this:
>
> <info name="keyname" value="sjdhfksdjhfksjhdf"
> isRuntimeVisible="true" />
>
> which could be nested inside <obj-attribute> <obj-relationship> or
> <obj-entity>, etc.
For db-* as well as obj-*?
> The keyname might be 'javadoc' or anything else really, so there
> could be some reserved keys for various specific jobs. Is that what
> you meant?
Yes. Some agreed keys like "db-comment", "javadoc" or whatever would
work.
> I'm also thinking that maybe the value needs to be a CDATA to
> accommodate multiline comments which end up (say) as javadocs.
Sounds like a good idea.
- Tore.