cayenne-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tarik Cherkovi <cher...@gmail.com>
Subject Re: Commits not visible across contexts in ROP
Date Fri, 13 Feb 2009 15:35:51 GMT
Oh I see. I will read up on XMPP. Here is my web.xml snippet.

I'd like to try forcing the context for forget it's cache and see what
performance is like.  It may be acceptable and at least provide a plan b.

    <servlet>
        <servlet-name>cayenne-service</servlet-name>

 <servlet-class>org.apache.cayenne.remote.hessian.service.HessianServlet</servlet-class>
   <init-param>
      <param-name>cayenne.RemoteService.EventBridge.factory</param-name>
      <param-value>org.apache.cayenne.event.XMPPBridgeFactory</param-value>
   </init-param>
   <init-param>
      <param-name>cayenne.XMPPBridge.xmppHost</param-name>
      <param-value>localhost</param-value>
   </init-param>
   <init-param>
      <param-name>cayenne.XMPPBridge.xmppPort</param-name>
      <param-value>5222</param-value>
   </init-param>
   <init-param>
      <param-name>cayenne.XMPPBridge.xmppChatService</param-name>
      <param-value>conference</param-value>
   </init-param>
     </servlet>
    <servlet-mapping>
        <servlet-name>cayenne-service</servlet-name>
        <url-pattern>/cayenne-service</url-pattern>
    </servlet-mapping>

On Fri, Feb 13, 2009 at 10:12 AM, Andrus Adamchik <andrus@objectstyle.org>wrote:

>
> On Feb 13, 2009, at 5:04 PM, Tarik Cherkovi wrote:
>
>  used XMPP connection for that purpose (see example web.xml declarations
>>>
>> here:
>>
>>>
>>> http://cayenne.apache.org/doc/remote-object-persistence-cws-deployment.html
>>>  ).
>>>
>> This requires
>>
>>> running a separate XMPP server, but otherwise works nicely.
>>>
>>
>> I added the configuration to my web.xml but I don't notice a difference.
>> What does the server actually send to the client?  Is there a way to check
>> that it's doing it?
>>
>> Thanks for your support and help on this.  I really appreciate it and hope
>> I
>> can come up with a solution as I am a bit in a crunch trying to go live
>> but
>> hitting this.
>>
>
> You will need a separate XMPP server running outside the web container.
> Strange that you don't see any client errors. Can you send a piece of
> web.xml where you set it up?
>
> Also on a local network JavaGroups communication channel is probably one of
> the best options, as it requires zero setup.. don't have examples handy. I
> may need some time to figure how to set it up.
>
> Andrus
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message