Also plan to clear duplicate beans definitions mentioned in my earlier
email.

On Sun, Aug 14, 2011 at 17:03, Maxim Solodovnik <[email protected]>wrote:

> Just commited the fix for quartz jobs.
> Going to make tests working.
>
>
> On Sun, Aug 14, 2011 at 16:59, [email protected] <
> [email protected]> wrote:
>
>> Did you commit everything or still working?
>>
>>
>> 2011/8/14 Maxim Solodovnik <[email protected]>
>>
>>> I'm starting to resolve "quartz" issues
>>>
>>> ERROR 08-14 13:03:29.008 QuartzMeetingReminderJob.java 107116 23
>>> org.openmeetings.app.quartz.scheduler.QuartzMeetingReminderJob [R
>>> ed5_Scheduler_Worker-9] - execute
>>> java.lang.NullPointerException: null
>>>         at
>>> org.openmeetings.app.quartz.scheduler.QuartzMeetingReminderJob.execute(QuartzMeetingReminderJob.java:21)
>>> [openmeetings.
>>> jar:na]
>>>         at
>>> org.red5.server.scheduling.QuartzSchedulingServiceJob.execute(QuartzSchedulingServiceJob.java:59)
>>> [red5.jar:na]
>>>         at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
>>> [quartz-1.6.5.jar:1.6.5]
>>>         at
>>> org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:525)
>>> [quartz-1.6.5.jar:1.6.5]
>>> ERROR 08-14 13:05:09.008 QuartzMeetingReminderJob.java 207116 
>>> 23org.openmeetings.app.quartz.scheduler.QuartzMeetingReminderJob [R
>>> ed5_Scheduler_Worker-11] - execute
>>> java.lang.NullPointerException: null
>>>         at
>>> org.openmeetings.app.quartz.scheduler.QuartzMeetingReminderJob.execute(QuartzMeetingReminderJob.java:21)
>>> [openmeetings.
>>> jar:na]
>>>         at
>>> org.red5.server.scheduling.QuartzSchedulingServiceJob.execute(QuartzSchedulingServiceJob.java:59)
>>> [red5.jar:na]
>>>         at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
>>> [quartz-1.6.5.jar:1.6.5]
>>>         at
>>> org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:525)
>>> [quartz-1.6.5.jar:1.6.5]
>>> ERROR 08-14 13:06:49.008 QuartzSessionClear.java 307116 
>>> 31org.openmeetings.app.quartz.scheduler.QuartzSessionClear [Red5_Schedule
>>> r_Worker-2] - execute
>>> java.lang.NullPointerException: null
>>>         at
>>> org.openmeetings.app.quartz.scheduler.QuartzSessionClear.execute(QuartzSessionClear.java:27)
>>> [openmeetings.jar:na]
>>>         at
>>> org.red5.server.scheduling.QuartzSchedulingServiceJob.execute(QuartzSchedulingServiceJob.java:59)
>>> [red5.jar:na]
>>>         at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
>>> [quartz-1.6.5.jar:1.6.5]
>>>         at
>>> org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:525)
>>> [quartz-1.6.5.jar:1.6.5]
>>>
>>> On Sun, Aug 14, 2011 at 13:08, Maxim Solodovnik <[email protected]>wrote:
>>>
>>>> Everything except for quartz seems to work as expected right now
>>>> (extensive testing is required)
>>>>
>>>> I found we have several beans of same type with different names:
>>>> flvrerorderservice.xml
>>>>
>>>>     <bean id="openmeetings.FlvRecordingMetaDataDaoImpl"
>>>>
>>>> class="org.openmeetings.app.data.flvrecord.FlvRecordingMetaDataDaoImpl">
>>>>     </bean>
>>>>
>>>> red5-applicationContext.xml
>>>> <bean id="flvRecordingMetaDataDao"
>>>> class="org.openmeetings.app.data.flvrecord.FlvRecordingMetaDataDaoImpl"/>
>>>>
>>>> I guess we need to leave only one bean defined.
>>>> I would propose to use definition from red5-applicationContext.xml
>>>>
>>>> Is it OK?
>>>>
>>>> On Sun, Aug 14, 2011 at 10:05, Maxim Solodovnik 
>>>> <[email protected]>wrote:
>>>>
>>>>> Hello Sebastian,
>>>>>
>>>>> I have fixed "openjpa.Meta" error.
>>>>> Currently I delete
>>>>> org.openmeetings.app.persistence.utils.PersistenceSessionUtil class and 
>>>>> now
>>>>> in process of resolving compilation errors.
>>>>>
>>>>>
>>>>> On Sat, Aug 13, 2011 at 23:22, [email protected] <
>>>>> [email protected]> wrote:
>>>>>
>>>>>> Ah okay,
>>>>>>
>>>>>> this Runtime error:
>>>>>> *openjpa.MetaData - Meta class ...*
>>>>>> I thought it would be thrown as the enhancer does not produce the
>>>>>> necessary meta-data Model Files.
>>>>>>
>>>>>> I will continue tomorrow morning with the rest.
>>>>>>
>>>>>> We will also need to see how we can fix the injection for Axis2, there
>>>>>> is an integration guide for Axis2 but I never finished that one, maybe I 
>>>>>> do
>>>>>> have the chance to fix that tomorrow.
>>>>>>
>>>>>> Thanks,
>>>>>> Sebastian
>>>>>>
>>>>>>
>>>>>> 2011/8/13 Maxim Solodovnik <[email protected]>
>>>>>>
>>>>>>> Servlets should be injected as follows
>>>>>>> <bean
>>>>>>> class="org.springframework.web.context.support.ServletContextAttributeExporter">
>>>>>>>  <property name="attributes">
>>>>>>> <map>
>>>>>>> <entry key="cfgManagement">
>>>>>>>  <ref bean="cfgManagement"/>
>>>>>>> </entry>
>>>>>>> </map>
>>>>>>>  </property>
>>>>>>> </bean>
>>>>>>>
>>>>>>> extended with bean need to be injected
>>>>>>>
>>>>>>> init method is implemented as follows:
>>>>>>> @Override
>>>>>>> public void init(ServletConfig config) throws ServletException {
>>>>>>>  super.init(config);
>>>>>>> cfgManagement =
>>>>>>> (Configurationmanagement)config.getServletContext().getAttribute("cfgManagement");
>>>>>>>  log.error("in init: cfgManagement is null ? " + (null ==
>>>>>>> cfgManagement) + " ; " + cfgManagement);
>>>>>>> }
>>>>>>>
>>>>>>> please
>>>>>>> see src\app\org\openmeetings\servlet\outputhandler\DefaultIndex.java
>>>>>>>
>>>>>>> enchancer works OK
>>>>>>> enhance:
>>>>>>>  [openjpac] 142  openmeetings  INFO   [main] openjpa.Tool - No
>>>>>>> targets were given.  Running on all classes in your persistent classes 
>>>>>>> list,
>>>>>>> or all metadata files in classpath directories if you have not listed 
>>>>>>> your
>>>>>>> persistent classes.  Use -help to display too l usage information.
>>>>>>>      [echo] Enhancing complete.
>>>>>>>
>>>>>>> I see Runtime errors like this:
>>>>>>> 59005  openmeetings  WARN   [NioProcessor-1] openjpa.MetaData - Meta
>>>>>>> class "org.openmeetings.app.persistence.beans.basic.Configura
>>>>>>> tion_" for entity class
>>>>>>> org.openmeetings.app.persistence.beans.basic.Configuration can not be
>>>>>>> registered with following exception
>>>>>>> "java.security.PrivilegedActionException:
>>>>>>> java.lang.ClassNotFoundException:
>>>>>>> org.openmeetings.app.persistence.beans.basic.Configura
>>>>>>> tion_"
>>>>>>>
>>>>>>> I plan to fix it.
>>>>>>>
>>>>>>>
>>>>>>> On Sat, Aug 13, 2011 at 20:53, [email protected] <
>>>>>>> [email protected]> wrote:
>>>>>>>
>>>>>>>> the enhancer task is not working ... I do not really know why, the
>>>>>>>> path to the persistance.xml seems to be correct but the enhancer does 
>>>>>>>> not
>>>>>>>> find any files to *enahnce*.
>>>>>>>> From what I udnerstood there should be a file with "_" at the end by
>>>>>>>> created.
>>>>>>>> There is none.
>>>>>>>>
>>>>>>>> Maybe the Beans need some decorator/annotaction or implement some
>>>>>>>> interface to be found?
>>>>>>>>
>>>>>>>> Did you encounter sth similar?
>>>>>>>>
>>>>>>>> Thanks
>>>>>>>>
>>>>>>>> Sebastian
>>>>>>>>
>>>>>>>> 2011/8/13 [email protected] <[email protected]>
>>>>>>>>
>>>>>>>>> The Installer/Importer now works again ... by revision 4041
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> 2011/8/13 [email protected] <[email protected]>
>>>>>>>>>
>>>>>>>>>> there are already service beans in:
>>>>>>>>>> /red5-services/ userservice.service.xml
>>>>>>>>>>
>>>>>>>>>> I guess yo've seen that, how will we care about those injections
>>>>>>>>>> "@Autowired" VS "XML-declared" injections?
>>>>>>>>>>
>>>>>>>>>> I manually inject the Bean now into the Servlet by using the
>>>>>>>>>> WebAppContext ... we might switch that later on but for now I have 
>>>>>>>>>> no clue
>>>>>>>>>> why the other methods / scanning the source dir et cetera does not 
>>>>>>>>>> work for
>>>>>>>>>> the Servlets ... I had some thinking about that point in the past 
>>>>>>>>>> already
>>>>>>>>>> ... maybe we fix that later on ... except you got another idea of 
>>>>>>>>>> course ^^
>>>>>>>>>>
>>>>>>>>>> Sebastian
>>>>>>>>>>
>>>>>>>>>> 2011/8/13 [email protected] <[email protected]>
>>>>>>>>>>
>>>>>>>>>> Maxim,
>>>>>>>>>>>
>>>>>>>>>>> I start looking at the Install routine.
>>>>>>>>>>>
>>>>>>>>>>> I've fixed/commited the Build file so that you can compile the
>>>>>>>>>>> JAR without doing EVERYTHING.
>>>>>>>>>>> build_openmeetings_jar.xml
>>>>>>>>>>> That should at least make it easier to build + test.
>>>>>>>>>>>
>>>>>>>>>>> Somehow the injection in the Servlet(s) does not work yet.
>>>>>>>>>>> I guess one could also use @Autowire in
>>>>>>>>>>> org.openmeetings.servlet.outputhandler to inject the 
>>>>>>>>>>> ImportInitvalues. I'll
>>>>>>>>>>> try on that one. If you have comments on that I will appreciate :)
>>>>>>>>>>>
>>>>>>>>>>> Thanks,
>>>>>>>>>>> Sebastian
>>>>>>>>>>>
>>>>>>>>>>> 2011/8/12 [email protected] <[email protected]>
>>>>>>>>>>>
>>>>>>>>>>> Ah okay,
>>>>>>>>>>>>
>>>>>>>>>>>> so lets resync tomorrow.
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks,
>>>>>>>>>>>> tty then
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> 2011/8/12 Maxim Solodovnik <[email protected]>
>>>>>>>>>>>>
>>>>>>>>>>>>> javaee-api-5.1.1.jar was created as follows:
>>>>>>>>>>>>> 1) original jar was unpacked to folder javaee-api-5.1.1
>>>>>>>>>>>>> 2) javax/persistence was deleted
>>>>>>>>>>>>> 3) jar was recreated using: "jar
>>>>>>>>>>>>> -cf javaee-api-5.1.1.jar javaee-api-5.1.1"
>>>>>>>>>>>>> that's it
>>>>>>>>>>>>>
>>>>>>>>>>>>> I mainly work at night.
>>>>>>>>>>>>> It's 3:00 AM here right now, so I'm ready to go bed too :)
>>>>>>>>>>>>> I plan to work on Saturday/Sunday.
>>>>>>>>>>>>>
>>>>>>>>>>>>> I propose to send quick note via email on current task.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Sat, Aug 13, 2011 at 02:57, [email protected] <
>>>>>>>>>>>>> [email protected]> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Okay,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> maybe you could upload the docs or the source files of the
>>>>>>>>>>>>>> java-ee package somewhere so that we can redo the modifications.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> About splitting the work:
>>>>>>>>>>>>>> We have currently 22.oo o'clock here, don't know your schedule
>>>>>>>>>>>>>> or if you are a (K)nightrider but I certainly will fall asleep 
>>>>>>>>>>>>>> soon today
>>>>>>>>>>>>>> :))
>>>>>>>>>>>>>> Do you work on Saturday/Sunday? Otherwise we could split it
>>>>>>>>>>>>>> based on the time we work on. I will continue tomorrow maybe 
>>>>>>>>>>>>>> 10.oo CET.
>>>>>>>>>>>>>> Just do not forget to commit ALL your changes and do a Sync 
>>>>>>>>>>>>>> before you
>>>>>>>>>>>>>> continue.
>>>>>>>>>>>>>> What do you think?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Sebastian
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> 2011/8/12 Maxim Solodovnik <[email protected]>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Forget to mention
>>>>>>>>>>>>>>> spring* jars were not just removed but extracted into
>>>>>>>>>>>>>>> lib/spring folder
>>>>>>>>>>>>>>> and copied to the right place by ant.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Sat, Aug 13, 2011 at 02:47, Maxim Solodovnik <
>>>>>>>>>>>>>>> [email protected]> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Hello Sebastian,
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> I haven't touch these jars dom4j, jaxen (maybe acidentally
>>>>>>>>>>>>>>>> remove them in ant), sorry for that
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> red5/lib:
>>>>>>>>>>>>>>>> Path Filename Extension Status
>>>>>>>>>>>>>>>> aopalliance-.jar aopalliance-.jar .jar deleted
>>>>>>>>>>>>>>>> aopalliance-1.0.jar aopalliance-1.0.jar .jar added
>>>>>>>>>>>>>>>> aspectjrt.jar aspectjrt.jar .jar added
>>>>>>>>>>>>>>>> javaee-api-5.1.1.jar javaee-api-5.1.1.jar .jar modified
>>>>>>>>>>>>>>>> spring-aop-2.5.6.jar spring-aop-2.5.6.jar .jar deleted
>>>>>>>>>>>>>>>> spring-asm-3.0.0.jar spring-asm-3.0.0.jar .jar deleted
>>>>>>>>>>>>>>>> spring-beans-3.0.0.jar spring-beans-3.0.0.jar .jar deleted
>>>>>>>>>>>>>>>> spring-context-3.0.0.jar spring-context-3.0.0.jar .jar
>>>>>>>>>>>>>>>> deleted
>>>>>>>>>>>>>>>> spring-context-support-3.0.0.jar
>>>>>>>>>>>>>>>> spring-context-support-3.0.0.jar .jar deleted
>>>>>>>>>>>>>>>> spring-core-3.0.0.jar spring-core-3.0.0.jar .jar deleted
>>>>>>>>>>>>>>>> spring-expression-3.0.0.jar spring-expression-3.0.0.jar
>>>>>>>>>>>>>>>> .jar deleted
>>>>>>>>>>>>>>>> spring-web-3.0.0.jar spring-web-3.0.0.jar .jar deleted
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> red5-applicationContext.xml has this name bacause files
>>>>>>>>>>>>>>>> named "red5-*" are automatically loaded
>>>>>>>>>>>>>>>> please see server\red5\webapps\openmeetings\WEB-INF\web.xml
>>>>>>>>>>>>>>>>     <context-param>
>>>>>>>>>>>>>>>>         <param-name>contextConfigLocation</param-name>
>>>>>>>>>>>>>>>>         <param-value>/WEB-INF/red5-*.xml</param-value>
>>>>>>>>>>>>>>>>     </context-param>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Sat, Aug 13, 2011 at 02:36, [email protected] <
>>>>>>>>>>>>>>>> [email protected]> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Hi Maxim,
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> I've seen your changes, looks good.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> But I needed to at least add 2 JARs again:
>>>>>>>>>>>>>>>>> dom4j
>>>>>>>>>>>>>>>>> jaxen
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Could you shed some light on those questions:
>>>>>>>>>>>>>>>>> Which JARs did you exactly remove and add to the red5/lb
>>>>>>>>>>>>>>>>> directory?
>>>>>>>>>>>>>>>>> Why is the spring context names
>>>>>>>>>>>>>>>>> *red5-applicationContext.xml* shouldn't it be
>>>>>>>>>>>>>>>>> openmeetings-applicationContext.xml ?
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>>>>> Sebastian
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>> Sebastian Wagner
>>>>>>>>>>>>>>>>> http://www.webbase-design.de
>>>>>>>>>>>>>>>>> http://openmeetings.googlecode.com
>>>>>>>>>>>>>>>>> http://www.wagner-sebastian.com
>>>>>>>>>>>>>>>>> [email protected]
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>> WBR
>>>>>>>>>>>>>>>> Maxim aka solomax
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>> WBR
>>>>>>>>>>>>>>> Maxim aka solomax
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> --
>>>>>>>>>>>>>> Sebastian Wagner
>>>>>>>>>>>>>> http://www.webbase-design.de
>>>>>>>>>>>>>> http://openmeetings.googlecode.com
>>>>>>>>>>>>>> http://www.wagner-sebastian.com
>>>>>>>>>>>>>> [email protected]
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>> WBR
>>>>>>>>>>>>> Maxim aka solomax
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> Sebastian Wagner
>>>>>>>>>>>> http://www.webbase-design.de
>>>>>>>>>>>> http://openmeetings.googlecode.com
>>>>>>>>>>>> http://www.wagner-sebastian.com
>>>>>>>>>>>> [email protected]
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Sebastian Wagner
>>>>>>>>>>> http://www.webbase-design.de
>>>>>>>>>>> http://openmeetings.googlecode.com
>>>>>>>>>>> http://www.wagner-sebastian.com
>>>>>>>>>>> [email protected]
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Sebastian Wagner
>>>>>>>>>> http://www.webbase-design.de
>>>>>>>>>> http://openmeetings.googlecode.com
>>>>>>>>>> http://www.wagner-sebastian.com
>>>>>>>>>> [email protected]
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Sebastian Wagner
>>>>>>>>> http://www.webbase-design.de
>>>>>>>>> http://openmeetings.googlecode.com
>>>>>>>>> http://www.wagner-sebastian.com
>>>>>>>>> [email protected]
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Sebastian Wagner
>>>>>>>> http://www.webbase-design.de
>>>>>>>> http://openmeetings.googlecode.com
>>>>>>>> http://www.wagner-sebastian.com
>>>>>>>> [email protected]
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> WBR
>>>>>>> Maxim aka solomax
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Sebastian Wagner
>>>>>> http://www.webbase-design.de
>>>>>> http://openmeetings.googlecode.com
>>>>>> http://www.wagner-sebastian.com
>>>>>> [email protected]
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> WBR
>>>>> Maxim aka solomax
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> WBR
>>>> Maxim aka solomax
>>>>
>>>
>>>
>>>
>>> --
>>> WBR
>>> Maxim aka solomax
>>>
>>
>>
>>
>> --
>> Sebastian Wagner
>> http://www.webbase-design.de
>> http://openmeetings.googlecode.com
>> http://www.wagner-sebastian.com
>> [email protected]
>>
>
>
>
> --
> WBR
> Maxim aka solomax
>



-- 
WBR
Maxim aka solomax

-- 
You received this message because you are subscribed to the Google Groups 
"OpenMeetings developers" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/openmeetings-dev?hl=en.

Reply via email to