[VOTE] Release XBean 3.12
I've staged a release of bean at: https://repository.apache.org/content/repositories/orgapachegeronimo-088/ Tag: http://svn.apache.org/repos/asf/geronimo/xbean/tags/xbean-3.12/ , revision 1393394 Release notes: ** Bug * [XBEAN-119] - ContextUtil$ReadOnlyBinding#isRelative() always returns false * [XBEAN-121] - Constructor injection doesn't work with constructor argument of type array * [XBEAN-146] - xsd for list elements should be unbounded, not max=1 * [XBEAN-190] - XBeanNamespaceHandler does not close resource input streams ** Improvement * [XBEAN-187] - SVN:IGNORE is missing for beanutils * [XBEAN-200] - be able to use annotationfinder for non runtime retention annotation * [XBEAN-203] - Performance improvement by adding local cache for MultiParentClassLoader#loadClass * [XBEAN-207] - FileArchive doesn't have a way to specify the base package * [XBEAN-208] - DelegatingBundle performance issues * [XBEAN-227] - Add support for Spring 3.1 bean profiles * [XBEAN-228] - Support aries blueprint 1.0 * [XBEAN-229] - Make jexl an optional import on xbean-blueprint Please review and vote: [ ] +1 release xbean 3.12 [ ] -1 do not release -- Guillaume Nodet Blog: http://gnodet.blogspot.com/ FuseSource, Integration everywhere http://fusesource.com
[jira] [Created] (GERONIMODEVTOOLS-803) Java 7 not recognized as supported version for 3.0 server runtime
Jarek Gawor created GERONIMODEVTOOLS-803: Summary: Java 7 not recognized as supported version for 3.0 server runtime Key: GERONIMODEVTOOLS-803 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-803 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Reporter: Jarek Gawor Assignee: Jarek Gawor When creating Geronimo 3.0 server runtime and specifying Java 7 as JRE version a warning is issued that runtime requires JDK 1.5 or greater. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMODEVTOOLS-803) Java 7 not recognized as supported version for 3.0 server runtime
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13468807#comment-13468807 ] Jarek Gawor commented on GERONIMODEVTOOLS-803: -- The warning message is also wrong because JRE 1.6 is required to run Geronimo 3.0. > Java 7 not recognized as supported version for 3.0 server runtime > - > > Key: GERONIMODEVTOOLS-803 > URL: > https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-803 > Project: Geronimo-Devtools > Issue Type: Bug > Components: eclipse-plugin >Reporter: Jarek Gawor >Assignee: Jarek Gawor > > When creating Geronimo 3.0 server runtime and specifying Java 7 as JRE > version a warning is issued that runtime requires JDK 1.5 or greater. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMODEVTOOLS-803) Java 7 not recognized as supported version for 3.0 server runtime
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13468810#comment-13468810 ] Jarek Gawor commented on GERONIMODEVTOOLS-803: -- Fixes committed in revision 1393751. > Java 7 not recognized as supported version for 3.0 server runtime > - > > Key: GERONIMODEVTOOLS-803 > URL: > https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-803 > Project: Geronimo-Devtools > Issue Type: Bug > Components: eclipse-plugin >Reporter: Jarek Gawor >Assignee: Jarek Gawor > > When creating Geronimo 3.0 server runtime and specifying Java 7 as JRE > version a warning is issued that runtime requires JDK 1.5 or greater. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
buildbot
Gavin has done some cleanup for https://issues.apache.org/jira/browse/INFRA-5323 geronimo-server-21 needs some attention, it seems. Could someone take a look? We should also review the current set of builds and remove those that we no longer need. --kevan
Can jpa queries be cached?
I see that both geronimo and openejb have jta or non-tx jpa query wrappers that
close the entity manager after the query executes. This pretty effectively
prevents the query from being re-executed.
Despite recalling having written the geronimo version, I can't remember why
this is necessary.
We've found someone who is doing something like this:
@Stateless
@ConcurrencyManagement(ConcurrencyManagementType.CONTAINER)
@TransactionManagement(TransactionManagementType.CONTAINER)
@TransactionAttribute(TransactionAttributeType.REQUIRED)
public class Foo implements FooLocal
{
@PersistenceContext(unitName="FooJpa", type =
PersistenceContextType.TRANSACTION) private EntityManager em;
private Query findBars;
@PostConstruct void postConstruct()
{
findBars = em.createNamedQuery("findBars");
}
public Collection getAllBars() {
return findBars.getResultList();
}
}
The second time getAllBars() is called, the em is closed.
There are some other errors in their code which might possibly be causing this,
but I think what is happening is that the postconstruct is executing outside a
jta transaction, so that the findBars query is a wrapped query that closes
itself after the query executes, even though it is executing in a jta
environment.
Should our wrapper only close the em if it is executed (rather than created)
outside a jta tx?
advice really appreciated :-)
thanks
david jencks
