JNDI datasource configuration

[aillet ()]

I must integrate a JBI SE component (not develop by PEtALS) which need a TransactionManager.

In the JBI specification, it is mentionned that JBI implementations have to provide a JNDI NamingContext and also a JTA implementation (see ComponentContext#getTransactionManager part).

Do you know if this part is well implemented in PEtALS 2.2 quickstart and if it has been used elsewhere ?

Other thing, is there a way to configure a JNDI datasource in PEtALS ? If yes, how to do and configure it externally (in the SU/SA jbi.xml perhaps ) ?

Regards,
Richard.

[Roland Naudin - EBM WebSourcing]

Hi Richard,

The Quick start doesn't provide transaction support, the others
distributions (Standalone, platform) does.

BTW, the transaction support is not mandatory in JBI specs! ;-)

If you are developping your own SE based on the CDK, you can use the
method getCurrentTransaction on your JBIListener to get the current
transaction. If you want to create a transaction, you have to use the
method getTransactionManager() from the componentContext.

About the JNDI datasource, there is one defined for your PEtALS domain.
By default, PEtALS provides its internal JNDI which is replicated
amongst the PEtALS nodes.
If you check the topology.xml file, you can set your own external JNDI
datasource.

Each component has a dedicated initial Context, which is separated each
others.
We are thinking to change this initial Context to one shared between all
the components.
May be a subject to a vote.

Regards
/Roland

Le vendredi 08 août 2008 à 09:02 -0700, aillet a écrit :

> I must integrate my own SE component which need a TransactionManager.
>
> In the JBI specification, it is mentionned that implementations have to
> provide a JNDI NamingContext and also a JTA implmentation (see
> ComponentContext#getTransactionManager part).
>
> Do you know if this part is well implemented in PEtALS 2.2 quickstart ?
>
> Other thing, is there a way to configure a JNDI datasource in PEtALS ? If
> yes, how to configure it externally (SU/SA jbi.xml) ?
>
> Regards,
> Richard.
> pièce jointe document plein texte (message-footer.txt)
> --
> You receive this message as a subscriber of the petals-users@... mailing list.
> To unsubscribe: mailto:petals-users-unsubscribe@...
> For general help: mailto:sympa@...?subject=help
> OW2 mailing lists service home page: http://www.ow2.org/wws

--

Roland NAUDIN
PEtALS team
EBM Websourcing

Try PEtALS at http://petals.ow2.org




--
You receive this message as a subscriber of the petals-users@... mailing list.
To unsubscribe: mailto:petals-users-unsubscribe@...
For general help: mailto:sympa@...?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws

[aillet]

Hi Roland,

can you tell me more about the internal JNDI datasource ?
I would like to reference it in my component but I have not the exact path (i.e.: java:comp/env/...).


Richard.

Roland Naudin - EBM WebSourcing wrote:

Hi Richard,

The Quick start doesn't provide transaction support, the others
distributions (Standalone, platform) does.

BTW, the transaction support is not mandatory in JBI specs! ;-)

If you are developping your own SE based on the CDK, you can use the
method getCurrentTransaction on your JBIListener to get the current
transaction. If you want to create a transaction, you have to use the
method getTransactionManager() from the componentContext.

About the JNDI datasource, there is one defined for your PEtALS domain.
By default, PEtALS provides its internal JNDI which is replicated
amongst the PEtALS nodes.
If you check the topology.xml file, you can set your own external JNDI
datasource.

Each component has a dedicated initial Context, which is separated each
others.
We are thinking to change this initial Context to one shared between all
the components.
May be a subject to a vote.

Regards
/Roland

Le vendredi 08 août 2008 à 09:02 -0700, aillet a écrit :
> I must integrate my own SE component which need a TransactionManager.
>
> In the JBI specification, it is mentionned that implementations have to
> provide a JNDI NamingContext and also a JTA implmentation (see
> ComponentContext#getTransactionManager part).
>
> Do you know if this part is well implemented in PEtALS 2.2 quickstart ?
>
> Other thing, is there a way to configure a JNDI datasource in PEtALS ? If
> yes, how to configure it externally (SU/SA jbi.xml) ?
>
> Regards,
> Richard.
> pièce jointe document plein texte (message-footer.txt)
> --
> You receive this message as a subscriber of the [e-mail] mailing list.
> To unsubscribe: mailto:[e-mail]
> For general help: mailto:[e-mail]?subject=help
> OW2 mailing lists service home page: http://www.ow2.org/wws
--
Roland NAUDIN
PEtALS team
EBM Websourcing

Try PEtALS at http://petals.ow2.org




--
You receive this message as a subscriber of the [e-mail] mailing list.
To unsubscribe: mailto:[e-mail]
For general help: mailto:[e-mail]?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws

[aillet]

Hi roland,

Is there anywhere a documentation of the PEtALS configuration (in particular to create topology.xml) ?

Richard.

Roland Naudin - EBM WebSourcing wrote:

Hi Richard,

The Quick start doesn't provide transaction support, the others
distributions (Standalone, platform) does.

BTW, the transaction support is not mandatory in JBI specs! ;-)

If you are developping your own SE based on the CDK, you can use the
method getCurrentTransaction on your JBIListener to get the current
transaction. If you want to create a transaction, you have to use the
method getTransactionManager() from the componentContext.

About the JNDI datasource, there is one defined for your PEtALS domain.
By default, PEtALS provides its internal JNDI which is replicated
amongst the PEtALS nodes.
If you check the topology.xml file, you can set your own external JNDI
datasource.

Each component has a dedicated initial Context, which is separated each
others.
We are thinking to change this initial Context to one shared between all
the components.
May be a subject to a vote.

Regards
/Roland

Le vendredi 08 août 2008 à 09:02 -0700, aillet a écrit :
> I must integrate my own SE component which need a TransactionManager.
>
> In the JBI specification, it is mentionned that implementations have to
> provide a JNDI NamingContext and also a JTA implmentation (see
> ComponentContext#getTransactionManager part).
>
> Do you know if this part is well implemented in PEtALS 2.2 quickstart ?
>
> Other thing, is there a way to configure a JNDI datasource in PEtALS ? If
> yes, how to configure it externally (SU/SA jbi.xml) ?
>
> Regards,
> Richard.
> pièce jointe document plein texte (message-footer.txt)
> --
> You receive this message as a subscriber of the [e-mail] mailing list.
> To unsubscribe: mailto:[e-mail]
> For general help: mailto:[e-mail]?subject=help
> OW2 mailing lists service home page: http://www.ow2.org/wws
--
Roland NAUDIN
PEtALS team
EBM Websourcing

Try PEtALS at http://petals.ow2.org




--
You receive this message as a subscriber of the [e-mail] mailing list.
To unsubscribe: mailto:[e-mail]
For general help: mailto:[e-mail]?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws

[Roland Naudin - EBM WebSourcing]

Hello richard.

If you are using the the standalone distribution, there is a online
documentation which explains the fields you can set on this file.

For the platform distribution, the online documentation is not up to
date. But you can check the XSD in $PETALS_HOME/schema. This XSD is
entirely commented.

Le lundi 11 août 2008 à 06:16 -0700, aillet a écrit :

> Hi roland,
>
> Is there anywhere a documentation of the PEtALS configuration (in particular
> to create topology.xml) ?
>
> Richard.
>
>
> Roland Naudin - EBM WebSourcing wrote:
> >
> > Hi Richard,
> >
> > The Quick start doesn't provide transaction support, the others
> > distributions (Standalone, platform) does.
> >
> > BTW, the transaction support is not mandatory in JBI specs! ;-)
> >
> > If you are developping your own SE based on the CDK, you can use the
> > method getCurrentTransaction on your JBIListener to get the current
> > transaction. If you want to create a transaction, you have to use the
> > method getTransactionManager() from the componentContext.
> >
> > About the JNDI datasource, there is one defined for your PEtALS domain.
> > By default, PEtALS provides its internal JNDI which is replicated
> > amongst the PEtALS nodes.
> > If you check the topology.xml file, you can set your own external JNDI
> > datasource.
> >
> > Each component has a dedicated initial Context, which is separated each
> > others.
> > We are thinking to change this initial Context to one shared between all
> > the components.
> > May be a subject to a vote.
> >
> > Regards
> > /Roland
> >
> > Le vendredi 08 août 2008 à 09:02 -0700, aillet a écrit :
> >> I must integrate my own SE component which need a TransactionManager.
> >>
> >> In the JBI specification, it is mentionned that implementations have to
> >> provide a JNDI NamingContext and also a JTA implmentation (see
> >> ComponentContext#getTransactionManager part).
> >>
> >> Do you know if this part is well implemented in PEtALS 2.2 quickstart ?
> >>
> >> Other thing, is there a way to configure a JNDI datasource in PEtALS ? If
> >> yes, how to configure it externally (SU/SA jbi.xml) ?
> >>
> >> Regards,
> >> Richard.
> >> pièce jointe document plein texte (message-footer.txt)
> >> --
> >> You receive this message as a subscriber of the petals-users@...
> >> mailing list.
> >> To unsubscribe: mailto:petals-users-unsubscribe@...
> >> For general help: mailto:sympa@...?subject=help
> >> OW2 mailing lists service home page: http://www.ow2.org/wws
> > --
> > Roland NAUDIN
> > PEtALS team
> > EBM Websourcing
> >
> > Try PEtALS at http://petals.ow2.org
> >
> >
> >
> >
> > --
> > You receive this message as a subscriber of the petals-users@...
> > mailing list.
> > To unsubscribe: mailto:petals-users-unsubscribe@...
> > For general help: mailto:sympa@...?subject=help
> > OW2 mailing lists service home page: http://www.ow2.org/wws
> >
> >
>
> pièce jointe document plein texte (message-footer.txt)
> --
> You receive this message as a subscriber of the petals-users@... mailing list.
> To unsubscribe: mailto:petals-users-unsubscribe@...
> For general help: mailto:sympa@...?subject=help
> OW2 mailing lists service home page: http://www.ow2.org/wws

--

Roland NAUDIN
PEtALS team
EBM Websourcing

Try PEtALS at http://petals.ow2.org




--
You receive this message as a subscriber of the petals-users@... mailing list.
To unsubscribe: mailto:petals-users-unsubscribe@...
For general help: mailto:sympa@...?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws

[Roland Naudin - EBM WebSourcing]

In your component, you can access to your component' initial context
with the ComponentContext method getNamingContext().

/Roland

Le lundi 11 août 2008 à 06:13 -0700, aillet a écrit :

> Hi Roland,
>
> can you tell me more about the internal JNDI datasource ?
> I would like to reference it in my component but I have not the exact path
> (i.e.: java:comp/env/...).
>
>
> Richard.
>
>
> Roland Naudin - EBM WebSourcing wrote:
> >
> > Hi Richard,
> >
> > The Quick start doesn't provide transaction support, the others
> > distributions (Standalone, platform) does.
> >
> > BTW, the transaction support is not mandatory in JBI specs! ;-)
> >
> > If you are developping your own SE based on the CDK, you can use the
> > method getCurrentTransaction on your JBIListener to get the current
> > transaction. If you want to create a transaction, you have to use the
> > method getTransactionManager() from the componentContext.
> >
> > About the JNDI datasource, there is one defined for your PEtALS domain.
> > By default, PEtALS provides its internal JNDI which is replicated
> > amongst the PEtALS nodes.
> > If you check the topology.xml file, you can set your own external JNDI
> > datasource.
> >
> > Each component has a dedicated initial Context, which is separated each
> > others.
> > We are thinking to change this initial Context to one shared between all
> > the components.
> > May be a subject to a vote.
> >
> > Regards
> > /Roland
> >
> > Le vendredi 08 août 2008 à 09:02 -0700, aillet a écrit :
> >> I must integrate my own SE component which need a TransactionManager.
> >>
> >> In the JBI specification, it is mentionned that implementations have to
> >> provide a JNDI NamingContext and also a JTA implmentation (see
> >> ComponentContext#getTransactionManager part).
> >>
> >> Do you know if this part is well implemented in PEtALS 2.2 quickstart ?
> >>
> >> Other thing, is there a way to configure a JNDI datasource in PEtALS ? If
> >> yes, how to configure it externally (SU/SA jbi.xml) ?
> >>
> >> Regards,
> >> Richard.
> >> pièce jointe document plein texte (message-footer.txt)
> >> --
> >> You receive this message as a subscriber of the petals-users@...
> >> mailing list.
> >> To unsubscribe: mailto:petals-users-unsubscribe@...
> >> For general help: mailto:sympa@...?subject=help
> >> OW2 mailing lists service home page: http://www.ow2.org/wws
> > --
> > Roland NAUDIN
> > PEtALS team
> > EBM Websourcing
> >
> > Try PEtALS at http://petals.ow2.org
> >
> >
> >
> >
> > --
> > You receive this message as a subscriber of the petals-users@...
> > mailing list.
> > To unsubscribe: mailto:petals-users-unsubscribe@...
> > For general help: mailto:sympa@...?subject=help
> > OW2 mailing lists service home page: http://www.ow2.org/wws
> >
> >
>
> pièce jointe document plein texte (message-footer.txt)
> --
> You receive this message as a subscriber of the petals-users@... mailing list.
> To unsubscribe: mailto:petals-users-unsubscribe@...
> For general help: mailto:sympa@...?subject=help
> OW2 mailing lists service home page: http://www.ow2.org/wws

--

Roland NAUDIN
PEtALS team
EBM Websourcing

Try PEtALS at http://petals.ow2.org




--
You receive this message as a subscriber of the petals-users@... mailing list.
To unsubscribe: mailto:petals-users-unsubscribe@...
For general help: mailto:sympa@...?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws

[Roland Naudin - EBM WebSourcing]

Just a precision.

I misunderstood the meaning of datasource, what you expect is to get a
reference to a datasource from the JNDI, and i was just saying that
there is a JNDI context provided by PEtALS.

In fact, there is no native SQL datasource available in PEtALS.

My apologies
/Roland


Le mardi 12 août 2008 à 09:41 +0200, Roland Naudin - EBM WebSourcing a
écrit :

> In your component, you can access to your component' initial context
> with the ComponentContext method getNamingContext().
>
> /Roland
>
> Le lundi 11 août 2008 à 06:13 -0700, aillet a écrit :
> > Hi Roland,
> >
> > can you tell me more about the internal JNDI datasource ?
> > I would like to reference it in my component but I have not the exact path
> > (i.e.: java:comp/env/...).
> >
> >
> > Richard.
> >
> >
> > Roland Naudin - EBM WebSourcing wrote:
> > >
> > > Hi Richard,
> > >
> > > The Quick start doesn't provide transaction support, the others
> > > distributions (Standalone, platform) does.
> > >
> > > BTW, the transaction support is not mandatory in JBI specs! ;-)
> > >
> > > If you are developping your own SE based on the CDK, you can use the
> > > method getCurrentTransaction on your JBIListener to get the current
> > > transaction. If you want to create a transaction, you have to use the
> > > method getTransactionManager() from the componentContext.
> > >
> > > About the JNDI datasource, there is one defined for your PEtALS domain.
> > > By default, PEtALS provides its internal JNDI which is replicated
> > > amongst the PEtALS nodes.
> > > If you check the topology.xml file, you can set your own external JNDI
> > > datasource.
> > >
> > > Each component has a dedicated initial Context, which is separated each
> > > others.
> > > We are thinking to change this initial Context to one shared between all
> > > the components.
> > > May be a subject to a vote.
> > >
> > > Regards
> > > /Roland
> > >
> > > Le vendredi 08 août 2008 à 09:02 -0700, aillet a écrit :
> > >> I must integrate my own SE component which need a TransactionManager.
> > >>
> > >> In the JBI specification, it is mentionned that implementations have to
> > >> provide a JNDI NamingContext and also a JTA implmentation (see
> > >> ComponentContext#getTransactionManager part).
> > >>
> > >> Do you know if this part is well implemented in PEtALS 2.2 quickstart ?
> > >>
> > >> Other thing, is there a way to configure a JNDI datasource in PEtALS ? If
> > >> yes, how to configure it externally (SU/SA jbi.xml) ?
> > >>
> > >> Regards,
> > >> Richard.
> > >> pièce jointe document plein texte (message-footer.txt)
> > >> --
> > >> You receive this message as a subscriber of the petals-users@...
> > >> mailing list.
> > >> To unsubscribe: mailto:petals-users-unsubscribe@...
> > >> For general help: mailto:sympa@...?subject=help
> > >> OW2 mailing lists service home page: http://www.ow2.org/wws
> > > --
> > > Roland NAUDIN
> > > PEtALS team
> > > EBM Websourcing
> > >
> > > Try PEtALS at http://petals.ow2.org
> > >
> > >
> > >
> > >
> > > --
> > > You receive this message as a subscriber of the petals-users@...
> > > mailing list.
> > > To unsubscribe: mailto:petals-users-unsubscribe@...
> > > For general help: mailto:sympa@...?subject=help
> > > OW2 mailing lists service home page: http://www.ow2.org/wws
> > >
> > >
> >
> > pièce jointe document plein texte (message-footer.txt)
> > --
> > You receive this message as a subscriber of the petals-users@... mailing list.
> > To unsubscribe: mailto:petals-users-unsubscribe@...
> > For general help: mailto:sympa@...?subject=help
> > OW2 mailing lists service home page: http://www.ow2.org/wws

--

Roland NAUDIN
PEtALS team
EBM Websourcing

Try PEtALS at http://petals.ow2.org




--
You receive this message as a subscriber of the petals-users@... mailing list.
To unsubscribe: mailto:petals-users-unsubscribe@...
For general help: mailto:sympa@...?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws