Yes! Guess it should figure in the training course!
Vinay
----- Original Message -----
From: "marc fleury" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, June 25, 2001 3:30 PM
Subject: RE: [JBoss-dev] JAWS -Single Datasource
> |Nonetheless, it would be great if the new CMP stuff will be able to
> |support multiple datasources i.e. move the datasource from a JAWS file
> |level node to a bean level value.
>
> I should really add a slide in the training called "scratch your own itch,
> Open Source's dirty little secret"...
>
> You want it? bad?
>
> You know what to do....
>
> marcf
>
> |
> |Thanks
> |
> |Vinay
> |
> |marc fleury wrote:
> |>
> |> Not all configuration cases will uses transactions across different
> |> databases (i.e. really require XA synchronization).
> |>
> |> The case Vinay is talking about is fairly simple simple 2 beans,
> |2 different
> |> apps (they don't talk to each other so no transaction enrollment), 2
> |> different databases, which is a perfectly valid approach to web
container
> |> app design, in fact a smart way to handle the database access
> |from your web
> |> layers ( and teh real reason I suspect he is asking for this feature).
> |>
> |> Distributed transaction is another ball game altogether, but what he is
> |> asking for doesn't necessarily require that. Also he has been through
my
> |> training and he knows that distributed transactions are bad mkey?
> |>
> |> In short it is a very valid feature Vinay, as everyone told you (dain,
> |> danch), why don't you go ahead and hack the metadata code to
> |make sure you
> |> can support multiple datasources (I am surprised it is not there yet).
> |>
> |> Talk to sebastien if you need help on that code, he wrote it.
> |>
> |> regards
> |> marcf
> |>
> |> |-----Original Message-----
> |> |From: [EMAIL PROTECTED]
> |> |[mailto:[EMAIL PROTECTED]]On Behalf Of
danch
> |> |Sent: Sunday, June 24, 2001 11:58 PM
> |> |To: [EMAIL PROTECTED]
> |> |Subject: Re: [JBoss-dev] JAWS -Single Datasource
> |> |
> |> |
> |> |Dain Sundstrom wrote:
> |> |
> |> |> No reason to tie an entire jar to a single datasource. I'll
> |> |check my code
> |> |> to see if it can support multiple datasources, although I
> |don't think it
> |> |> will work with most DBs. This would require the DBs to
> |natively support
> |> |> JDBC 2.0 XA transactions, and if I remember most DBs don't
> |have 2-phase
> |> |> commit drivers yet.
> |> |>
> |> |> -dain
> |> |
> |> |I believe they are getting much closer (at least if implementations of
> |> |the XA extensions to JDBC are a true indicator). Of course, many of
the
> |> |XA implementations are broken in incompatible ways.
> |> |
> |> |Also, this wouldn't matter so long as the beans that are in different
> |> |databases are in different transactions. But then there'd be no reason
> |> |not to split them into different ejb-jar files.
> |> |
> |> |-danch
> |> |
> |> |
> |> |_______________________________________________
> |> |Jboss-development mailing list
> |> |[EMAIL PROTECTED]
> |> |http://lists.sourceforge.net/lists/listinfo/jboss-development
> |>
> |> _______________________________________________
> |> Jboss-development mailing list
> |> [EMAIL PROTECTED]
> |> http://lists.sourceforge.net/lists/listinfo/jboss-development
> |
> |_______________________________________________
> |Jboss-development mailing list
> |[EMAIL PROTECTED]
> |http://lists.sourceforge.net/lists/listinfo/jboss-development
>
>
>
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-development
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
