Re: [VOTE][RESULT] Felix 1.4.0 framework and related subproject release
FYI, Felix 1.4.0 is available in Maven mirrors. Thanx Karl. On Wed, Nov 12, 2008 at 5:21 PM, Karl Pauls [EMAIL PROTECTED] wrote: I will look into it tonight. regards, Karl Am 12.11.2008 um 15:27 schrieb Stuart McCulloch [EMAIL PROTECTED]: 2008/11/11 Karl Pauls [EMAIL PROTECTED] Time to call the vote on the Felix 1.4.0 framework and related subprojects release. * +1 votes from Richard S. Hall, Stuart McCulloch, Carsten Ziegeler, Marcel Offermans, Didier Donsez, Alin Dreghiciu, Niclas Hedhman, Clement Escoffier, Toni Menzel, Edward Yakop, Felix Meschberger, Rob Walker, and Karl Pauls. * No other votes The vote is successful. I will make the release artifacts available as soon as possible. Hi Karl - any idea when the release artifacts will hit the Maven mirrors? -- Cheers, Stuart -- Alin Dreghiciu http://www.ops4j.org - New Energy for OSS Communities - Open Participation Software. http://www.qi4j.org- New Energy for Java - Domain Driven Development. http://malaysia.jayway.net - New Energy for Projects - Great People working on Great Projects at Great Places
[jira] Updated: (FELIX-804) Incorporate the Service Registry ListenerHook (RFC 126) work done in the CXF DOSGi project
[ https://issues.apache.org/jira/browse/FELIX-804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Bosschaert updated FELIX-804: --- Attachment: ListenerHook.patch The ListenerHook.patch file contains an implementation of the OSGi RFC 126 ListenerHook mechanism (see http://www.osgi.org/download/osgi-4.2-early-draft.pdf). The patch is created with a Felix Trunk checkout from Nov 12, 2008. The patch contains code from the originally part of the DOSGi code in CXF (http://svn.apache.org/repos/asf/cxf/sandbox/dosgi) written by Sergey Beryozkin, reapplied to the Felix trunk. Couple of notes regarding the patch: * It contains a new interface org.osgi.framework.hooks.service.ListenerHook. This and its embedded ListenerInfo are new interfaces that are part of the OSGi 4.2 Core specification (part of RFC 126) * There is also a new org.osgi.framework.ServiceException class, which is also part of OSGi 4.2 * Because of the changes to org.osgi.core, the dependency to that component in framework/pom.xml has been updated to 1.3.0-SNAPSHOT (from 1.2.0). I was wondering, should it not move to 1.4.1-SNAPSHOT or something? Unit tests are included for all code changes except for the changes to the org.apache.felix.framework.Felix class. Because all member variables of this class are Private its currently impossible to write unit tests for parts of it. I would happily volunteer to make this class unit-testable if this is considered to be a good idea. The patch contains new files (which sometimes causes problems with older patch application tools). It was created with Tortoise 1.5.0. Incorporate the Service Registry ListenerHook (RFC 126) work done in the CXF DOSGi project -- Key: FELIX-804 URL: https://issues.apache.org/jira/browse/FELIX-804 Project: Felix Issue Type: New Feature Components: Framework Reporter: David Bosschaert Attachments: ListenerHook.patch This bug relates to https://issues.apache.org/jira/browse/CXF-1897 The CXF DOSGi project contains an implementation of the ListenerHook of RFC 126. This could should move into Felix. See also: http://www.mail-archive.com/dev@felix.apache.org/msg06475.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Contributing parts of the ServiceRegistry Hooks (RFC 126) implementation into Felix
Hi all, 2008/11/7 David Bosschaert [EMAIL PROTECTED]: 2008/11/4 Richard S. Hall [EMAIL PROTECTED]: I think it sounds reasonable. I am all for creating a JIRA issue with appropriate patch. Great. I've created https://issues.apache.org/jira/browse/FELIX-804 where the patch will ultimately be attached. I've attached the patch containing the ListenerHook implementation to this bug. I also put some notes regarding the patch in the comment of the bug. It would be great if someone could review and apply it. Many thanks, David
Re: [VOTE][RESULT] Felix 1.4.0 framework and related subproject release
O.k. good. I will do the news today since I wasn't able to connect to the wiki yesterday. regards, Karl On Thu, Nov 13, 2008 at 10:07 AM, Alin Dreghiciu [EMAIL PROTECTED] wrote: FYI, Felix 1.4.0 is available in Maven mirrors. Thanx Karl. On Wed, Nov 12, 2008 at 5:21 PM, Karl Pauls [EMAIL PROTECTED] wrote: I will look into it tonight. regards, Karl Am 12.11.2008 um 15:27 schrieb Stuart McCulloch [EMAIL PROTECTED]: 2008/11/11 Karl Pauls [EMAIL PROTECTED] Time to call the vote on the Felix 1.4.0 framework and related subprojects release. * +1 votes from Richard S. Hall, Stuart McCulloch, Carsten Ziegeler, Marcel Offermans, Didier Donsez, Alin Dreghiciu, Niclas Hedhman, Clement Escoffier, Toni Menzel, Edward Yakop, Felix Meschberger, Rob Walker, and Karl Pauls. * No other votes The vote is successful. I will make the release artifacts available as soon as possible. Hi Karl - any idea when the release artifacts will hit the Maven mirrors? -- Cheers, Stuart -- Alin Dreghiciu http://www.ops4j.org - New Energy for OSS Communities - Open Participation Software. http://www.qi4j.org- New Energy for Java - Domain Driven Development. http://malaysia.jayway.net - New Energy for Projects - Great People working on Great Projects at Great Places -- Karl Pauls [EMAIL PROTECTED]
[jira] Resolved: (FELIX-811) MonitorAdmin - Unregistration of Monitorable causes IllegalArgumentException in MonitoringJob
[ https://issues.apache.org/jira/browse/FELIX-811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Didier DONSEZ resolved FELIX-811. - Resolution: Fixed Assignee: Didier DONSEZ the patch was applied and tested with the demo script felix/sandbox/donsez/script/monitor.txt and commited at revision: 713734 MonitorAdmin - Unregistration of Monitorable causes IllegalArgumentException in MonitoringJob - Key: FELIX-811 URL: https://issues.apache.org/jira/browse/FELIX-811 Project: Felix Issue Type: Bug Components: Sandbox Reporter: Martin Thelian Assignee: Didier DONSEZ Attachments: FELIX-811.patch If a Monitorable service is unregistered from the framework but there is still a scheduled MonitorJob monitoring StatusVariables of the unregistered Monitorable, an IllegalArgumentException is thrown in the MonitoringJobImpl and the whole MonitoringJob thread dies. The stracktrace: | Exception in thread Thread-24 java.lang.IllegalArgumentException: no such monitorable service for this pid | at org.apache.felix.sandbox.monitor.MonitorAdminImpl$MonitorAdminProxy.getStatusVariable(MonitorAdminImpl.java:322) | at org.apache.felix.sandbox.monitor.MonitorAdminImpl$MonitoringJobImpl$MyRunnable.run(MonitorAdminImpl.java:142) | at java.lang.Thread.run(Thread.java:595) The OSGi spec defines the following: Whether a monitoring job keeps track dynamically of the StatusVariables it monitors is not specified. This means that if we monitor a StatusVariable of a Monitorable service which disappears and later reappears then it is imple- mentation specific whether we still receive updates of the StatusVariable changes or not. From my point of view the MonitoringJob should just ignore disappeared variables and should continue to monitor all other variables. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (FELIX-810) MonitorAdmin - NullPointerException while calling MonitoringJob.stop()
[
https://issues.apache.org/jira/browse/FELIX-810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Didier DONSEZ resolved FELIX-810.
-
Resolution: Fixed
Assignee: Didier DONSEZ
the patch was applied and tested with the demo script
felix/sandbox/donsez/script/monitor.txt
and commited at revision: 713734
MonitorAdmin - NullPointerException while calling MonitoringJob.stop()
---
Key: FELIX-810
URL: https://issues.apache.org/jira/browse/FELIX-810
Project: Felix
Issue Type: Bug
Components: Sandbox
Reporter: Martin Thelian
Assignee: Didier DONSEZ
Attachments: FELIX-810.patch
I've started a scheduled job with:
| this.monitorService.startScheduledJob(
|PID, // listener.id
|variableNames.toArray(new String[variableNames.size()]),
|60, // seconds
|0 // Forever
| );
If I then need to stop the job via
| this.currentMonitorJob.stop();
e.g. because the variableName list has changed I'm getting the following
NullpointerException:
-
| java.lang.NullPointerException
| at
org.apache.felix.sandbox.monitor.MonitorAdminImpl$MonitoringJobImpl.unsubscribeStatusVariables(MonitorAdminImpl.java:185)
| at
org.apache.felix.sandbox.monitor.MonitorAdminImpl$MonitoringJobImpl.stop(MonitorAdminImpl.java:162)
-
The problem seems to be that there are no subscriptions in a scheduled job
and therefore the variable list shown in the code fragment below is null.
| private void unsubscribeStatusVariables() {
| [...]
|List list=(List)subscriptions.get(statusVariableName);
|if(list!=null) {
|list.remove(this);
|} // else never occurs
|if(list.isEmpty())
|subscriptions.remove(statusVariableName);
|}
| }
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (FELIX-804) Incorporate the Service Registry ListenerHook (RFC 126) work done in the CXF DOSGi project
[ https://issues.apache.org/jira/browse/FELIX-804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard S. Hall reassigned FELIX-804: - Assignee: Richard S. Hall Incorporate the Service Registry ListenerHook (RFC 126) work done in the CXF DOSGi project -- Key: FELIX-804 URL: https://issues.apache.org/jira/browse/FELIX-804 Project: Felix Issue Type: New Feature Components: Framework Reporter: David Bosschaert Assignee: Richard S. Hall Attachments: ListenerHook.patch This bug relates to https://issues.apache.org/jira/browse/CXF-1897 The CXF DOSGi project contains an implementation of the ListenerHook of RFC 126. This could should move into Felix. See also: http://www.mail-archive.com/dev@felix.apache.org/msg06475.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Contributing parts of the ServiceRegistry Hooks (RFC 126) implementation into Felix
I will try to take a look at it soon. - richard David Bosschaert wrote: Hi all, 2008/11/7 David Bosschaert [EMAIL PROTECTED]: 2008/11/4 Richard S. Hall [EMAIL PROTECTED]: I think it sounds reasonable. I am all for creating a JIRA issue with appropriate patch. Great. I've created https://issues.apache.org/jira/browse/FELIX-804 where the patch will ultimately be attached. I've attached the patch containing the ListenerHook implementation to this bug. I also put some notes regarding the patch in the comment of the bug. It would be great if someone could review and apply it. Many thanks, David
[jira] Updated: (FELIX-10) Implement Device Access
[ https://issues.apache.org/jira/browse/FELIX-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Offermans updated FELIX-10: -- Attachment: device-access.zip Donation of the implementation by Dennis Geurts. This was already discussed on the mailing list. Paperwork is being done now. Implement Device Access --- Key: FELIX-10 URL: https://issues.apache.org/jira/browse/FELIX-10 Project: Felix Issue Type: New Feature Components: Device Access, Specification compliance Reporter: Richard S. Hall Attachments: device-access.zip See section 103 in the OSGi R4 Service Compendium for a full description of the task. Since implementations of this service exist, perhaps a donation would be possible. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
