Mailing-List: contact commits-help@cayenne.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cayenne.apache.org
Message-ID: <1555214161.1258584159690.JavaMail.jira@brutus>
Date: Wed, 18 Nov 2009 22:42:39 +0000 (UTC)
From: "Ari Maniatis (JIRA)" <jira@apache.org>
To: commits@cayenne.apache.org
Subject: [jira] Commented: (CAY-1312) Allow lifecycle callbacks on ROP
 client
In-Reply-To: <1931255163.1258539639568.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CAY-1312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12779703#action_12779703 ] 

Ari Maniatis commented on CAY-1312:
-----------------------------------

Just throwing this out as an idea: would users sometimes want to specify particular clients? For instance, you might have a data processing node which is different to a client GUI node or a (in the future) Cayenne aware Ajax node.

If so, the schema would allow for this to be arbitrary text (not an enumeration), but the modeler would by default give you three options (as you specified) and maybe (later) a free entry text option.

> Allow lifecycle callbacks on ROP client
> ---------------------------------------
>
>                 Key: CAY-1312
>                 URL: https://issues.apache.org/jira/browse/CAY-1312
>             Project: Cayenne
>          Issue Type: New Feature
>          Components: Cayenne Core Library
>            Reporter: Andrey Razumovsky
>            Assignee: Andrey Razumovsky
>             Fix For: 3.1
>
>
> Allow lifecycle callbacks on ROP client. They should work roughly the same way. This jira does not include modeler support, but does possible configuration cahnges

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