2011/3/30 :
> so i think i understand the open session in view pattern when generally
> used with controllers and creating a filter which creates the hibernate
> session and starts the transaction and then there are multiple service
> calls for that http request.
Actually I wouldn't like it to wo
so i think i understand the open session in view pattern when generally
used with controllers and creating a filter which creates the hibernate
session and starts the transaction and then there are multiple service
calls for that http request.
im trying to do the same thing for batch jobs but runn
What I mean is this...
Lets say we want to allow users to plug in a ConnectionProvider by this
method. How do they get configuration information into this service? Thats
why our file is slightly different, you have key/value pairs allowed. The
required key is implClass to name your impl. Bu
Each provider configuration file can contain multiple implementations
of the given interface. From the JavaDoc of j.u.ServiceLoader: "The
file contains a list of fully-qualified binary names of concrete
provider classes, one per line".
>From how I understood your original requirement/implementatio
To be honest not sure what this really buys you. Basically you have to follow
the META-INF/service/{intf-name} pattern for naming your locator file and that
locator file, as far as I know, can only have a single entry naming the impl
class. Which is kind of limiting. What concrete benefits do
Even better then :)
Adam
On Mar 30, 2011, at 8:23 PM, Steve Ebersole wrote:
> Hibernate 4 targets java 6
>
> On Wednesday, March 30, 2011, at 01:16 pm, Adam Warski wrote:
>> Heh sorry, pasted the wrong link :) This should be the right one:
>> http://java.sun.com/developer/technicalArticles/java
Hibernate 4 targets java 6
On Wednesday, March 30, 2011, at 01:16 pm, Adam Warski wrote:
> Heh sorry, pasted the wrong link :) This should be the right one:
> http://java.sun.com/developer/technicalArticles/javase/extensible/index.htm
> l
>
> Anyway, the mechanism/names were standardized as part
Heh sorry, pasted the wrong link :) This should be the right one:
http://java.sun.com/developer/technicalArticles/javase/extensible/index.html
Anyway, the mechanism/names were standardized as part of Java 6.
That's e.g. how CDI extensions are discovered:
http://docs.jboss.org/weld/reference/1.1.
Hi,
since Java 1.6 this functionality is provided by
java.util.ServiceLoader [1] so when you are based on JDK 6 anyway you
could simply use that class.
When targeting older JDKs one indeed must build it from hand (HV does
this for instance, too). Sun's JDK has contained this utility for
quite a w
This is exactly what I have done. There is no standard java mechanism for
doing this. Your link simply shows how one piece of java (Sound API) does it.
On Wednesday, March 30, 2011, at 11:22 am, Adam Warski wrote:
> Did you think about using the java services mechanism? Essentialy placing a
>
Did you think about using the java services mechanism? Essentialy placing a
file in META-INF/services:
http://download.oracle.com/javase/1.4.2/docs/guide/sound/programmer_guide/chapter13.html
?
I don't think it gives any functionality, but is a standard way for doing such
things.
Adam
On Mar 2
11 matches
Mail list logo
