cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joerg Heinicke <joerg.heini...@gmx.de>
Subject Re: cvs commit: cocoon-2.1/src/blocks/slide/java/org/apache/cocoon/components/source/impl SlideSourceFactory.java
Date Wed, 03 Dec 2003 15:20:32 GMT
On 03.12.2003 14:48, Unico Hommes wrote:

>>>>I am thinking JDO. What's the reason for this?
>>>
>>
>>I'm not that familiar with Java or the Avalon lifecycles, but 
>>here is my analysis from
>>http://wiki.cocoondev.org/Wiki.jsp?page=FirstFridayDecember2003:
>>
>>Make it possible to include also the OJB block by default 
>>without breaking Cocoon. This is a really important issue as 
>>it breaks our suggested build system workflow using 
>>local.blocks.properties! You can not include blocks when they 
>>are excluded in blocks.properties.
>>
>>AFAIU the reason for the problem is factory = new 
>>OjbStorePMF(); in the
>>initialize() method in JdoPMFImpl.java. Isn't it possible to 
>>do lazy initializing when accessing factory the first time? I 
>>guess this has to be done in getPersistenceManager().
> 
> Yes, you are right. I got it working now. I had to change the factory
> instance variable's type to Object but it works. I hope this will also
> work for other JVM's than the one I tested it on. Should I commit it?

Why is the change to Object needed? Is this class instantiated on start 
up even if it's not Initializable?

Everything that's better than now should be committed. What are the 
potential issues with other JVMs? Do you cast the Object to the PMFactory?

What do the other people think?

Joerg


Mime
View raw message