[Design of EJB 3.0] - Re: Bringing in ejb3-cache
by wolfc
"ALRubinger" wrote : ...
| * Add new internal callback mechanisms for things like "prePassivate", "passivationStarted", "passivationCompleted". Part of the contract of the cache impl will be to implement these callbacks (thus allowing us to do whatever blocking/locking or get notification in tests).
Wouldn't a dummy persistence manager be enough?
"ALRubinger" wrote : ...
| * WTF was I thinking with this horrid CacheFactory-per-impl design? Should better be a configurable factory capable of creating any N Caches. Ditto for the PersistenceManagerFactories. I'll have to change up the relevant jboss-beans.xml to fix this as well.
What I really would like to see is a deployer which takes cache metadata (@CacheConfig) and creates a cache based on that. Which we then inject into the container using @Inject with component scope.
That would require the container to be a MC component as well though. See embedded ejb deployers.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4185625#4185625
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4185625
16 years, 1 month
[Design of EJB 3.0] - Bringing in ejb3-cache
by ALRubinger
Recent work in SimpleStatefulCache has uncovered a few issues:
* https://jira.jboss.org/jira/browse/EJBTHREE-1551
* https://jira.jboss.org/jira/browse/EJBTHREE-1549 (Resolved)
My tests for 1549 are imperfect as they put Thread.sleep() into the client, resulting in:
* Long execution time
* Assumption that background work will have completed in the time allotted
This has to be fixed.
The best way to do this would be to extract out portions of SimpleStatefulCache such that they may be overridden with some locking introduced (@see org.jboss.ejb3.core.test.ejbthree1549.ForcePassivationCache.BlockingPassivationTask.block()).
And while we're at it, the cache impls should really conform to the Cache SPI as dictated by the ejb3-cache project. Currently they do not.
I'm working on the following:
* Move / Copy / Something to put SimpleStatefulCache into ejb3-cache. Currently I can't have this implementation conform to both the legacy StatefulCache and new Cache SPIs because they're incompatible.
* Do the extraction and fix the tests as outlined above
* Add new internal callback mechanisms for things like "prePassivate", "passivationStarted", "passivationCompleted". Part of the contract of the cache impl will be to implement these callbacks (thus allowing us to do whatever blocking/locking or get notification in tests).
* Move StatefulContainer to the new Cache SPI
* WTF was I thinking with this horrid CacheFactory-per-impl design? Should better be a configurable factory capable of creating any N Caches. Ditto for the PersistenceManagerFactories. I'll have to change up the relevant jboss-beans.xml to fix this as well.
Anything else we want to get in there?
I'm unsure of what to do with the TreeCache impl here, because the second I move StatefulContainer to rely upon the new Cache SPI, that'll break.
For now I'm starting with the elements that won't break everything. I'll have to coordinate/schedule API changes w/ Brian.
S,
ALR
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4185607#4185607
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4185607
16 years, 1 month
[Design of PVM (Process Virtual Machine)] - jbpm-pvm-1.0.beta1 Hibernate Mapping Exception.
by sreeraaman
Hi All,
I get the following exception when trying to start my jboss server with my enterprise archive which has the jbpm-pvm-1.0.beta1 jar file inside it.
My persistence.xml looks like this:
| <?xml version="1.0" encoding="UTF-8"?>
| <persistence>
| <persistence-unit name="pu">
| <jta-data-source>java:/pu-DS</jta-data-source>
| <jar-file>../jbpm-jpdl.jar</jar-file>
| <jar-file>../jbpm-pvm.jar</jar-file>
| <properties>
| <property name="hibernate.hbm2ddl.auto" value="false"/>
| <property name="hibernate.dialect" value="org.hibernate.dialect.MySQLInnoDBDialect"/>
| <property name="jboss.entity.manager.jndi.name" value="entityManager"/>
| <property name="hibernate.archive.autodetection" value="class,hbm" />
| <property name="hibernate.show_sql" value="true"/>
| <property name="hibernate.search.default.directory_provider" value="org.hibernate.search.store.FSDirectoryProvider"/>
| <property name="hibernate.search.default.indexBase" value="C:/lucene/indexes"/>
| <property name="hibernate.ejb.event.post-insert"
| value="org.hibernate.search.event.FullTextIndexEventListener"/>
| <property name="hibernate.ejb.event.post-update"
| value="org.hibernate.search.event.FullTextIndexEventListener"/>
| <property name="hibernate.ejb.event.post-delete"
| value="org.hibernate.search.event.FullTextIndexEventListener"/>
| </properties>
| </persistence-unit>
| </persistence>
|
The deployment exception says this:
| javax.persistence.PersistenceException: org.hibernate.MappingException: Could not determine type for: converter, at table: JBPM_VARIABLEDEF, for columns: [org.hibernate.mapping.Column(TYPE_CONVERTER_)]
|
Any help would be appreciated.
best regards
sriraman.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4185602#4185602
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4185602
16 years, 1 month
[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Status of LargeMessages work
by clebert.suconic@jboss.com
"Tim" wrote :
| "Clebert" wrote :
| | II - I have added a new interface called ServerLargeMessage which will be implemented by each storage-manager we have. We have JournalServerLargeMessageImpl and NullStorageManager. The StorageManager will be responsible for the instantiation of this class.
| |
|
| Confusing name. The journal is a large message?
|
|
I'm out of creativity here.. I could use a little help! :-)
I have an interface called ServerLargeMessage, and a class extendins ServerMessageImpl and implementing ServerLargeMessage for the Journal.
| +-------------------------------+ +----------------+
| | ServerMessageImpl | | ServerLargeMsg|
| +-------------------------------+ +----------------+
| ^ ^
| | |
| | |
| | |
| | |
| +-------------------------------+ |
| | JournalServerLargeMessageImpl |------------------
| +-------------------------------+
|
|
What would be a better name for JournalServerLargeMessageImpl?
I have also NullStorageServerLargeMessageImpl.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4185559#4185559
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4185559
16 years, 1 month