Hi all,
I'm having an interesting conversation on the forums:
- https://forum.hibernate.org/viewtopic.php?f=9&t=1039407
Pawel is mentioning the need to configure a PROVIDER_URL property to
get his slaves to know were to connect to.
I'm pretty sure others have successfully configured this in the p
Hi,
In case we are talking about Context.PROVIDER_URL, then this is a
JNDI configuration property. He should be able to set it via hibernate.jndi.url.
--Hardy
On Tue, May 12, 2015 at 10:43:08AM +0100, Sanne Grinovero wrote:
> Hi all,
> I'm having an interesting conversation on the forums:
> -
This might help as well -
https://docs.jboss.org/author/display/WFLY8/JNDI+Reference
On Tue, May 12, 2015 at 01:12:38PM +0200, Hardy Ferentschik wrote:
> Hi,
>
> In case we are talking about Context.PROVIDER_URL, then this is a
> JNDI configuration property. He should be able to set it via
> h
We have some Hibernate Search tests which use multi-tenancy, and
require the schema to be exported explicitly. I'm trying to get these
to run now with Hibernate ORM 5.
I can't use the command line tool, as the test configuration options
should be passed by instance (there are several unit tests to
None of the bootstrapping contracts are kept around after the SF is
bootstrapped. Nothing different there from Configuration. There is
nothing meaningful on SessionFactory for performing any schema tools. For
what its worth I hope to change that with the metamodel work (6.0), but for
now this is
HHH-9792 - Clean up missed Configuration methods
On Tue, May 12, 2015 at 11:05 PM, Steve Ebersole
wrote:
> None of the bootstrapping contracts are kept around after the SF is
> bootstrapped. Nothing different there from Configuration. There is
> nothing meaningful on SessionFactory for perform
