An SPI is a contract that a user would implement, but also a contract
the need to implement such a contract.
For example, take SessionImplementor from ORM. It is the SPI contract
for Session. Most other SPI contracts pass SessionImplementor as an
argment, or make it available in some fashion
Hi,
> What's your definition of an SPI
I think an SPI is something which the user implements (as you say
typically advanced users which need to plug-in custom functionality
into the framework) opposed to an API, which is something which a user
just uses/invokes.
> That's the proposal I have pus
Hi,
thanks for your feedback.
I think we might go for a combined approach. For everything not
related to method validation (that is, the api/spi split related
changes), I've now added deprecation markers and at the same time the
new types [1]. So clients could adapt to these changes based on 4.3
Hi Pawel,
On 2 April 2012 15:27, Pawel Kozlowski wrote:
> Hi Sanne, All,
>
> On Mon, Mar 26, 2012 at 3:38 PM, Sanne Grinovero wrote:
>
>> Are you interested in implementing JTA for a specific NoSQL store, or
>> on the general problem?
>
> Both actually. Just to give you more context I'm looking
hi Emmanuel, All!
I've provided some more context regarding the data store I'm looking
into in response to Sanne's post. I know it sounds crazy but I'm
exploring git as a key-value store (that gives me versioning as a
"bonus").
On Mon, Mar 26, 2012 at 6:37 PM, Emmanuel Bernard
wrote:
> I am not
Hi Sanne, All,
On Mon, Mar 26, 2012 at 3:38 PM, Sanne Grinovero wrote:
> Are you interested in implementing JTA for a specific NoSQL store, or
> on the general problem?
Both actually. Just to give you more context I'm looking into OGM as a
JPA interface for 2 NoSQL data stores:
(1) Neo4j - fro
On 2 avr. 2012, at 11:44, Hardy Ferentschik wrote:
>>
>> What's your definition of an SPI, in the team we have slightly different
>> ones.
>>
>> In Hibernate search an SPI is targeted at frameworks or hyper advanced user
>> who are willing to integrate or enhance Hibernate Search. Otherwise,
But we probably don't have the bandwidth for a "4.9".
On 2 avr. 2012, at 11:54, Sanne Grinovero wrote:
> I don't know if it's doable, but having an API "deprecated" (literally
> or just as a wiki warning) without having no alternative, and remove
> it in next version makes it very hard to proceed
On 2 April 2012 10:44, Hardy Ferentschik wrote:
>
> On Apr 2, 2012, at 11:16 AM, Emmanuel Bernard wrote:
>
>> What's your definition of an SPI, in the team we have slightly different
>> ones.
>>
>> In Hibernate search an SPI is targeted at frameworks or hyper advanced user
>> who are willing to
I don't know if it's doable, but having an API "deprecated" (literally
or just as a wiki warning) without having no alternative, and remove
it in next version makes it very hard to proceed iteratively in an
upgrade migration.
If you want to "start clean" in version 5, as a user (hypothetically
spe
On Apr 2, 2012, at 11:16 AM, Emmanuel Bernard wrote:
> What's your definition of an SPI, in the team we have slightly different ones.
>
> In Hibernate search an SPI is targeted at frameworks or hyper advanced user
> who are willing to integrate or enhance Hibernate Search. Otherwise, they are
On Apr 1, 2012, at 11:56 AM, Gunnar Morling wrote:
> I'm not really sure which is the better option here. Given that method
> validation is the biggest new feature of BV 1.1 and HV 5 will be the
> first release to implement that new version of the spec, I think it
> would be ok if that release br
What's your definition of an SPI, in the team we have slightly different ones.
In Hibernate search an SPI is targeted at frameworks or hyper advanced user who
are willing to integrate or enhance Hibernate Search. Otherwise, they are
considered APIs - which includes interfaces you might need to i
For such drastic moves, Hibernate Search has used the migration page on the
wiki to alert people. Not ideal but it works.
Emmanuel
On 1 avr. 2012, at 11:56, Gunnar Morling wrote:
> Hi all,
>
> Hardy and I have been discussing approaches for deprecating certain
> features in Hibernate Validator
I need to dive a bit into the JPA 2.1 PaaS proposal but here are a few comments
in line int he mean time.
On 30 mars 2012, at 17:57, Steve Ebersole wrote:
> The scope of multi-tenancy in JPA 2.1 is pretty much set it seems, its
> just details at this point. And that scope is decidedly differen
15 matches
Mail list logo
