On 13 Nov 00, at 9:43, marc fleury wrote:
> |I'm glad to see this is just for BMP. There are better solutions for
> |CMP, and I'd hate to be prevented from using them.
>
> Yes for BMP since the container doesn't own the state (he doesn't know where
> to look and such) all the container can ensure is that the state is
> persisted through the "ejbStore()" calls. Now the state in memory is
> synched across VM in one Tx encapsulation. A BMP finder can now work it's
> jdbc or odbc.
>
> This is a nobrainer.
>
> For CMP, it is of course another matter altogether, but right now the
> implementation of the finder is still through JDBC in databases so that we
> would need the same requirement. If we have in memory maps we can query
> across nodes (yeah right) then that is one thing, otherwise we are screwed.
What I want to do eventually is JDBC + check of the cache.
-Dan
>
> What I am saying is that the only thing I see us having any control over is
> the Tx information for example if the tx is new with finder then we can
> avoid this madness.
>
> marc
>
> |
> |-Dan
> |
> |On 13 Nov 00, at 17:54, Rickard �berg wrote:
> |
> |> Hey
> |>
> |> Dan OConnor wrote:
> |> > Could you point me to this in the spec to save some looking? :-)
> |>
> |> EJB 2.0, 11.3.2:
> |> "Before invoking the ejbFind<METHOD>(...) method, the container must
> |> first synchronize the
> |> state of any entity bean instances that are participating in the same
> |> transaction context as is used to exe-cute
> |> the ejbFind<METHOD>(...) by invoking the ejbStore() method on those
> |> entity bean
> |> instances."
> |>
> |> We can do this fairly easily by modifying our
> |> EntitySynchronizationInterceptor. But in a cluster where tx's aren't
> |> always cluster local... *shiver*..
> |>
> |> /Rickard
> |>
> |> --
> |> Rickard �berg
> |>
> |> Email: [EMAIL PROTECTED]
> |> http://www.telkel.com
> |> http://www.jboss.org
> |> http://www.dreambean.com
> |>
> |>
> |> --
> |> --------------------------------------------------------------
> |> To subscribe: [EMAIL PROTECTED]
> |> To unsubscribe: [EMAIL PROTECTED]
> |> Problems?: [EMAIL PROTECTED]
> |>
> |
> |
> |
> |
> |--
> |--------------------------------------------------------------
> |To subscribe: [EMAIL PROTECTED]
> |To unsubscribe: [EMAIL PROTECTED]
> |Problems?: [EMAIL PROTECTED]
> |
> |
>
>
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Problems?: [EMAIL PROTECTED]
>
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
