Return-Path: Delivered-To: apmail-cayenne-user-archive@www.apache.org Received: (qmail 23933 invoked from network); 16 Feb 2009 23:59:53 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 16 Feb 2009 23:59:53 -0000 Received: (qmail 47800 invoked by uid 500); 16 Feb 2009 23:59:53 -0000 Delivered-To: apmail-cayenne-user-archive@cayenne.apache.org Received: (qmail 47783 invoked by uid 500); 16 Feb 2009 23:59:52 -0000 Mailing-List: contact user-help@cayenne.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cayenne.apache.org Delivered-To: mailing list user@cayenne.apache.org Received: (qmail 47772 invoked by uid 99); 16 Feb 2009 23:59:52 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 16 Feb 2009 15:59:52 -0800 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [63.208.196.179] (HELO mho-02-bos.mailhop.org) (63.208.196.179) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 16 Feb 2009 23:59:41 +0000 Received: from cpe-69-204-109-121.buffalo.res.rr.com ([69.204.109.121] helo=insysware.insysware.com) by mho-02-bos.mailhop.org with esmtpsa (TLSv1:RC4-MD5:128) (Exim 4.68) (envelope-from ) id 1LZDMs-000BrK-Od for user@cayenne.apache.org; Mon, 16 Feb 2009 23:59:18 +0000 X-Mail-Handler: MailHop Outbound by DynDNS X-Originating-IP: 69.204.109.121 X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/mailhop/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX1/nIzBVf4DfNSDRt8wfuVagtO9eJSKbE/8= Content-class: urn:content-classes:message Subject: RE: Updating DataMap through ROP client Date: Mon, 16 Feb 2009 19:05:38 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable In-Reply-To: <3219fff70902161214i23139a17m560d2e1b66ee273@mail.gmail.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: X-MimeOLE: Produced By Microsoft Exchange V6.5 Thread-Topic: Updating DataMap through ROP client Thread-Index: AcmQdC38Vjib0W+JQJ69PwrT2W3thwAHb6nw References: <3219fff70902151009y1b8a1cb3j216b1d28070f5d28@mail.gmail.com> <3219fff70902161214i23139a17m560d2e1b66ee273@mail.gmail.com> From: "Zissis Trabaris" To: X-Virus-Checked: Checked by ClamAV on apache.org I can clear the EntityResolver on the client side but since I don't know how to get to the Configuration instance on the server side I can't re-load the maps. Without re-loading the maps on the server side, I will always get an entity not found exception when I try to use a newly added ObjEntity. Zissis Trabaris * Chief Technology Officer * INSYSWARE * 3235 West River Road, Grand Island, New York, 14072, USA=20 Mobile (716) 930-5654 * Office (518) 636-4118 * Fax (716) 625-1305 * z.trabaris@insysware.com * www.insysware.com=20 CONFIDENTIALITY: This email (including any attachments) may contain confidential, proprietary and privileged information, and unauthorized disclosure or use is prohibited. If you received this email in error, please notify the sender and delete this email from your system. Thank you.=20 -----Original Message----- From: Andrey Razumovsky [mailto:razumovsky.andrey@gmail.com]=20 Sent: Monday, February 16, 2009 3:15 PM To: user@cayenne.apache.org Subject: Re: Updating DataMap through ROP client I don't know details of Hessian, but I don't think HessianServlet caches any data. Have you tried simply clearing client context's cache? 2009/2/16 Zissis Trabaris > I have solved the DataMap problem with the following: I have created an > HTTP back-channel that send the map xmls to the client. The client then > creates a new Configuration instance, modifies the data maps, serializes > the results to XML, sends them to the server and the server saves them > to disk. The remaining problems to solve are the following: > > 1) I need to somehow refresh the configuration instances that are in > memory for the HessianServlet. > 2) Once refreshed, I need to somehow clear the object caches of the > HessianServlet. > > All of this without dropping any connections that the HessianServlet is > servicing. > > Zissis Trabaris * Chief Technology Officer * INSYSWARE * 3235 West River > Road, Grand Island, New York, 14072, USA > Mobile (716) 930-5654 * Office (518) 636-4118 * Fax (716) 625-1305 * > z.trabaris@insysware.com * www.insysware.com > > CONFIDENTIALITY: This email (including any attachments) may contain > confidential, proprietary and privileged information, and unauthorized > disclosure or use is prohibited. If you received this email in error, > please notify the sender and delete this email from your system. Thank > you. > > > -----Original Message----- > From: Andrey Razumovsky [mailto:razumovsky.andrey@gmail.com] > Sent: Sunday, February 15, 2009 1:10 PM > To: user@cayenne.apache.org > Subject: Re: Updating DataMap through ROP client > > Hi Zissis, > > DbEntities are not being sent to client (and DataMap is sent trimmed). > So I > don't think you can perform DataMap changes from client. What I would > try to > do is to write a custom query which performs your operations and the > fire it > from the client. I'm not sure this will work though. > > Regards, > Andrey > > 2009/2/15 Zissis Trabaris > > > We have an ROP client that acts as a modeler for our runtime > > application. Is there any way to modify a DataMap via an ROP client > > layer, synchronize the DB schema like I would do using > > ExecutingMergerContext at the server layer and then clear the server > and > > client object caches without dropping the ROP connection? > > > > > > > > Zissis Trabaris * Chief Technology Officer * INSYSWARE * 3235 West > River > > Road, Grand Island, New York, 14072, USA > > Mobile (716) 930-5654 * Office (518) 636-4118 * Fax (716) 625-1305 * > > z.trabaris@insysware.com > < > 20%2520z.trabaris@insysware.com <20%252520z.trabaris@insysware.com>>> > > * > > www.insysware.com > > > > ________________________________ > > > > CONFIDENTIALITY: This email (including any attachments) may contain > > confidential, proprietary and privileged information, and unauthorized > > disclosure or use is prohibited. If you received this email in error, > > please notify the sender and delete this email from your system. Thank > > you. > > > > > > > > >