November 2007 - jboss-dev-forums - Jboss List Archives

[Design of POJO Server] - Re: Embbedded - broken - some fixes - still not working

by epbernard

"max.andersen(a)jboss.com" wrote : emmanuel - Isn't this way of starting (with PersistenceUnitInfo) different from what happens when hibernate scans for entities "on its own" in j2se scenario ? Not anymore, the scanning process has been mutualized now (latest beta). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4109069#4109069 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4109069

16 years, 5 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Improvig timer

by brittm

Like most folks, I guess, I've implemented an ActionHandler to dynamically modify due dates on tasks and timers. And like you mention Tom, there typically needs to be a dynamic date/time reference from the process instance as well as a static modifier...such as <timer name="xyz" baseDateTime="#{someJava.util.Date}" addDuration="1 business day"></timer> | Use case: I have an established deadline for a customer install, and this task/timer needs to come due 1 business day ahead of that deadline... <timer name="xyz" baseDateTime="#{deadlineDate}" addDuration="-1 business day"></timer> | or the same for a task... <task name="xyz" baseDateTime="#{deadlineDate}" addDuration="-1 business day" .../> -Britt View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4109052#4109052 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4109052

16 years, 5 months

1
0
0 / 0

[Design of POJO Server] - Re: Embbedded - broken - some fixes - still not working

by adrian＠jboss.org

"max.andersen(a)jboss.com" wrote : ...but why is this concern of where to get resources from leaked out via the urls passed down to hibernate via the urls it gets ? Can't we avoid that somehow? I don't understand your question? You need some identifier. JavaEE generally uses URLs (but they are not navigable there is no generic getChildURLs()). Currently hibernate gets the top level url and barfs because it only knows how to navigate file:, jar: There is no way to make it understand anything else. We're discussing how to go beyond these for reasons of optimization and ease of use/development. If you want to avoid the problem then we say you always have to package as a jar or exploded archive and we will always scan everything (multiple times :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4109042#4109042 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4109042

16 years, 5 months

1
0
0 / 0

[Design of POJO Server] - Re: Embbedded - broken - some fixes - still not working

by max.andersen＠jboss.com

...but why is this concern of where to get resources from leaked out via the urls passed down to hibernate via the urls it gets ? Can't we avoid that somehow? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4109035#4109035 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4109035

16 years, 5 months

1
0
0 / 0

[Design of POJO Server] - Re: Embbedded - broken - some fixes - still not working

by adrian＠jboss.org

"epbernard" wrote : | Even if we define a proprietary abstraction implemented by JBoss AS and passed as an argument to createContainerEntityManagerFactory (in the Map), it does not solves the whole problem. | JBoss AS has to conform to the PersistenceUnitInfo contract so that other providers can bootstrap :) I'm not saying don't support the spec. I'm saying we can optimize it. There are really two seperate issues: 1) The embedded stuff where we don't require a packaging step to run tests, we create a VFS context that collects the disparate resources from across the IDE project. A sort of in memory symbolic link. See the VFSTestCase in the embedded project. 2) Optimizing the scanning/parsing of the class files for annotations. Scanning we can trim the list the list to speed things up since we already did the scan and know which are @Entity. And we've already parse those classes that do match. The issue that started this thread was (1). (2) is a nice to have. At the moment we have EJB3, Hibernate, Tomcat, AOP and in the future the MC all needing to scan packages for annotated classes. Doing it N times for N different modules is just a waste. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4109027#4109027 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4109027

16 years, 5 months

1
0
0 / 0

[Design of JBossCache] - Re: Hot Deployment -Object Cache

by galder.zamarreno＠jboss.com

It is an open community in the sense that we discuss "stuff", as long as "stuff" is related to the forum where is posted, i.e. We freely help people with issues using JBoss Cache in the JBoss Cache Users Forum We help people with issues/queries developing features or fixing bugs in JBoss Cache in the JBoss Cache Design Forum Your post does is not fall in either of these categories, so we're not able to help your further at this point. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4109026#4109026 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4109026

16 years, 5 months

1
0
0 / 0

[Design of POJO Server] - Re: Embbedded - broken - some fixes - still not working

by max.andersen＠jboss.com

emmanuel - Isn't this way of starting (with PersistenceUnitInfo) different from what happens when hibernate scans for entities "on its own" in j2se scenario ? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4109024#4109024 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4109024

16 years, 5 months

1
0
0 / 0

[Design of POJO Server] - Re: Embbedded - broken - some fixes - still not working

by epbernard

Hey guys, There are some reasons why I assume either a JAR structure or a directory from these URLs. The contract between the app server and the persistence provider is defined by javax.persistence.spi.PersistenceUnitInfo When the container creates a PU, it calls /** | * Called by the container when an EntityManagerFactory | * is to be created. | * | * @param info Metadata for use by the persistence provider | * @param map A Map of integration-level properties for use | * by the persistence provider (may be null if no properties | * are specified). | * @return EntityManagerFactory for the persistence unit | * specified by the metadata | */ | public EntityManagerFactory createContainerEntityManagerFactory(PersistenceUnitInfo info, Map map); Specifically the interesting bits of the contract are /** | * Interface implemented by the container and used by the | * persistence provider when creating an EntityManagerFactory. | */ | public interface PersistenceUnitInfo { | [...] | | /** | * @return The list of JAR file URLs that the persistence | * provider must examine for managed classes of the persistence | * unit. Each jar file URL corresponds to a named <jar-file> | * element in the persistence.xml file. | */ | public List<URL> getJarFileUrls(); | | /** | * @return The URL for the jar file or directory that is the | * root of the persistence unit. (If the persistence unit is | * rooted in the WEB-INF/classes directory, this will be the | * URL of that directory.) | */ | public URL getPersistenceUnitRootUrl(); | | [...] | } The reading of the JavaDoc (and the intend of the spec) is that the persistence provider expect either a directory or a JAR file. I scan the root URL for 3 reasons: - get the annotated classes - get hbm.xml files - get ORM.xml files 2 is proprietary to Hibernate of course. Even if we define a proprietary abstraction implemented by JBoss AS and passed as an argument to createContainerEntityManagerFactory (in the Map), it does not solves the whole problem. JBoss AS has to conform to the PersistenceUnitInfo contract so that other providers can bootstrap :) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4109018#4109018 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4109018

16 years, 5 months

1
0
0 / 0

[Design of POJO Server] - Re: Client-side clustering classes in the aspects module

by bstansberry＠jboss.com

Crap; ClusterChooserInterceptor has a tie to the general purpose aspects module InvokeRemoteInterceptor via a couple constants that serve as metadata keys InvokeRemoteInterceptor.REMOTING and InvokeRemoteInterceptor.INVOKER_LOCATOR. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4109017#4109017 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4109017

16 years, 5 months

1
0
0 / 0

[Design of JBossCache] - Re: Hot Deployment -Object Cache

by ekobir

Sorry to bother you Galder. I just thought somebody can reply from here as it is an open community... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4109004#4109004 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4109004

16 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums November 2007