Re: How much of the system repository is needed for a karaf boot?

2018-01-16 Thread Jean-Baptiste Onofré 

Hi Steinar,

All core jars are taken from system repository. Even startup.properties reads 
from system repo.


Basically the minimum that you should have is the ones in  startup.properties 
and, if you don't want remote resolution, the ones in boot features.


Regards
JB

On 01/16/2018 07:22 PM, Steinar Bang wrote:

The $KARAF_HOME/system directory is the top of an area laid out like a
maven repository, containing (in karaf 4.1.4) 64 jar files.

The repository is the first repository of the
org.ops4j.pax.url.mvn.defaultRepositories configuration setting.

How many of these jar files are needed for karaf to boot and start
pulling dependencies down from external maven repository?  None?  All?
Some? (if "some" are there a way to find out which ones are essential?)

Thanks!


  - Steinar (trying to figure out the proper way to do a debian package
of karaf https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881297 )



--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Transaction Control

2018-01-16 Thread Leschke, Scott 
I've been trying to integrate this into my app. I just pulled down the latest 
(0.0.3) jars from Maven Central.  As far as I can tell, the two bundles I need 
are
tx-control-service-local
tx-control-provider-jdbc-local

I can drop the first one into my deploy directory and it tells me it needs the 
second.  As soon as I try to deploy the second jar, the console stops 
recognizing commands or hangs (at least that's the appearance).  The  Following 
is what I see in the log.  Note that I'm using 4.2.0.M2.


2018-01-16T14:38:17,751 | INFO  | fileinstall-c:/bam | fileinstall  
| 9 - org.apache.felix.fileinstall - 3.6.4 | Installing bundle 
tx-control-provider-jdbc-local / 0.0.3
2018-01-16T14:38:17,813 | INFO  | FelixFrameworkWiring | CommandExtension   
  | 33 - org.apache.karaf.shell.core - 4.2.0.M2 | Unregistering 
commands for bundle org.apache.karaf.event/4.2.0.M2
2018-01-16T14:38:17,820 | INFO  | FelixFrameworkWiring | CommandExtension   
  | 33 - org.apache.karaf.shell.core - 4.2.0.M2 | Unregistering 
commands for bundle org.apache.karaf.features.command/4.2.0.M2
2018-01-16T14:38:17,828 | INFO  | FelixFrameworkWiring | Activator  
  | 6 - org.ops4j.pax.logging.pax-logging-api - 1.10.1 | Disabling 
SLF4J API support.
2018-01-16T14:38:17,828 | INFO  | activator-1-thread-2 | CommandExtension   
  | 33 - org.apache.karaf.shell.core - 4.2.0.M2 | Unregistering 
commands for bundle org.apache.karaf.kar.core/4.2.0.M2
2018-01-16T14:38:17,828 | INFO  | FelixFrameworkWiring | Activator  
  | 6 - org.ops4j.pax.logging.pax-logging-api - 1.10.1 | Disabling 
Jakarta Commons Logging API support.
2018-01-16T14:38:17,829 | INFO  | FelixFrameworkWiring | Activator  
  | 6 - org.ops4j.pax.logging.pax-logging-api - 1.10.1 | Disabling 
Log4J API support.
2018-01-16T14:38:17,829 | INFO  | FelixFrameworkWiring | Activator  
  | 6 - org.ops4j.pax.logging.pax-logging-api - 1.10.1 | Disabling 
Avalon Logger API support.
2018-01-16T14:38:17,829 | INFO  | FelixFrameworkWiring | Activator  
  | 6 - org.ops4j.pax.logging.pax-logging-api - 1.10.1 | Disabling JULI 
Logger API support.
2018-01-16T14:38:17,829 | INFO  | activator-1-thread-1 | HttpServiceFactoryImpl 
  | 105 - org.ops4j.pax.web.pax-web-runtime - 6.1.0 | Unbinding bundle: 
[org.apache.karaf.webconsole.features [111]]
2018-01-16T14:38:17,830 | INFO  | FelixFrameworkWiring | Activator  
  | 6 - org.ops4j.pax.logging.pax-logging-api - 1.10.1 | Disabling 
Log4J v2 API support.
2018-01-16T14:38:17,831 | INFO  | activator-1-thread-1 | FeaturesPlugin 
  | 111 - org.apache.karaf.webconsole.features - 4.2.0.M2 | Features 
plugin deactivated
2018-01-16T14:38:17,870 | INFO  | FelixFrameworkWiring | core   
  | 12 - org.apache.aries.jmx.core - 1.1.7 | Unregistering 
org.osgi.jmx.framework.BundleStateMBean to MBeanServer 
org.apache.karaf.management.internal.EventAdminMBeanServerWrapper@700031b9 with 
name 
osgi.core:type=bundleState,version=1.7,framework=org.apache.felix.framework,uuid=cac40ac4-12dd-4cb5-8ded-1f73370df0aa
2018-01-16T14:38:17,870 | INFO  | FelixFrameworkWiring | core   
  | 12 - org.apache.aries.jmx.core - 1.1.7 | Unregistering 
org.osgi.jmx.service.cm.ConfigurationAdminMBean to MBeanServer 
org.apache.karaf.management.internal.EventAdminMBeanServerWrapper@700031b9 with 
name 
osgi.compendium:service=cm,version=1.3,framework=org.apache.felix.framework,uuid=cac40ac4-12dd-4cb5-8ded-1f73370df0aa
2018-01-16T14:38:17,870 | INFO  | FelixFrameworkWiring | core   
  | 12 - org.apache.aries.jmx.core - 1.1.7 | Unregistering 
org.osgi.jmx.framework.FrameworkMBean to MBeanServer 
org.apache.karaf.management.internal.EventAdminMBeanServerWrapper@700031b9 with 
name 
osgi.core:type=framework,version=1.7,framework=org.apache.felix.framework,uuid=cac40ac4-12dd-4cb5-8ded-1f73370df0aa
2018-01-16T14:38:17,870 | INFO  | FelixFrameworkWiring | core   
  | 12 - org.apache.aries.jmx.core - 1.1.7 | Unregistering 
org.osgi.jmx.framework.ServiceStateMBean to MBeanServer 
org.apache.karaf.management.internal.EventAdminMBeanServerWrapper@700031b9 with 
name 
osgi.core:type=serviceState,version=1.7,framework=org.apache.felix.framework,uuid=cac40ac4-12dd-4cb5-8ded-1f73370df0aa
2018-01-16T14:38:17,871 | INFO  | FelixFrameworkWiring | core   
  | 12 - org.apache.aries.jmx.core - 1.1.7 | Unregistering 
org.osgi.jmx.framework.PackageStateMBean to MBeanServer 
org.apache.karaf.management.internal.EventAdminMBeanServerWrapper@700031b9 with 
name 
osgi.core:type=packageState,version=1.5,framework=org.apache.felix.framework,uuid=cac40ac4-12dd-4cb5-8ded-1f73370df0aa
2018-01-16T14:38:17,871 | INFO  | FelixFrameworkWiring | core   
  | 12 - org.apache.aries.jmx.core -

How much of the system repository is needed for a karaf boot?

2018-01-16 Thread Steinar Bang 
The $KARAF_HOME/system directory is the top of an area laid out like a
maven repository, containing (in karaf 4.1.4) 64 jar files.

The repository is the first repository of the
org.ops4j.pax.url.mvn.defaultRepositories configuration setting.

How many of these jar files are needed for karaf to boot and start
pulling dependencies down from external maven repository?  None?  All?
Some? (if "some" are there a way to find out which ones are essential?)

Thanks!


 - Steinar (trying to figure out the proper way to do a debian package
   of karaf https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881297 )

Re: "org.apache.felix.eventadmin.IgnoreTopic" ignored for log events

2018-01-16 Thread João Assunção 
Hello Roberto,

A few months ago I came across the same issue.
I think it is a bug in the EventAdmin implementation (
https://issues.apache.org/jira/browse/FELIX-5738).
Unfortunately, I didn't find an workwaround.

João Assunção

Email: joao.assun...@exploitsys.com
Mobile: +351 916968984
Phone: +351 211933149
Web: www.exploitsys.com



On Tue, Jan 16, 2018 at 3:44 PM, robe...@iooota.com 
wrote:

> Context: Apache Karaf 4.1.3
>
> Hi,
> I'm trying to force the EventAdmin to do not propagate any event dealing
> with the logging system, but whatever value I try with the
> "org.apache.felix.eventadmin.IgnoreTopic" parameter gets ignored.
>
> I've done some debugging and this is what I've noticed:
> - the check is performed at org.apache.felix.eventadmin.
> impl.handler.EventAdminImpl.postEvent(org.osgi.service.event.Event) line:
> 178, where "checkTopic(...)" is invoked
> - checkTopic() applies a set of matchers (derived from the ".cfg" file) to
> the topic of the event considered
> - the matcher is implemented by org.apache.felix.eventadmin.impl.handler.
> EventHandlerTracker$SubPackageMatcher.match(java.lang.String) line: 377
> this way
>
> @Override
> public boolean match(final String className)
> {
> final int pos = className.lastIndexOf('.');
> return pos > -1 && className.substring(0, pos +
> 1).startsWith(m_packageName);
> }
>
> "classname" is passed as "org/osgi/service/log/LogEntry/LOG_WARNING" (the
> event topic) and "m:packageName" is "org/osgi/service/log/." (derived from
> "org/osgi/service/log/*" in the .cfg file).
>
> Whatever value I set in the .cfg file pos will always be -1 and
> there's nothing I can do about it, since I can't choose the logging events
> topic string. Thus, the result will be always "false" and no event will be
> skipped.
>
> What am I missing?...
>
> Thanks in advance,
>
>
> Roberto
>
>

"org.apache.felix.eventadmin.IgnoreTopic" ignored for log events

2018-01-16 Thread robe...@iooota.com 
Context: Apache Karaf 4.1.3

Hi,
I'm trying to force the EventAdmin to do not propagate any event dealing with 
the logging system, but whatever value I try with the 
"org.apache.felix.eventadmin.IgnoreTopic" parameter gets ignored.

I've done some debugging and this is what I've noticed:
- the check is performed at 
org.apache.felix.eventadmin.impl.handler.EventAdminImpl.postEvent(org.osgi.service.event.Event)
 line: 178, where "checkTopic(...)" is invoked
- checkTopic() applies a set of matchers (derived from the ".cfg" file) to the 
topic of the event considered
- the matcher is implemented by 
org.apache.felix.eventadmin.impl.handler.EventHandlerTracker$SubPackageMatcher.match(java.lang.String)
 line: 377 this way

@Override
public boolean match(final String className)
{
final int pos = className.lastIndexOf('.');
return pos > -1 && className.substring(0, pos + 
1).startsWith(m_packageName);
}

"classname" is passed as "org/osgi/service/log/LogEntry/LOG_WARNING" (the event 
topic) and "m:packageName" is "org/osgi/service/log/." (derived from 
"org/osgi/service/log/*" in the .cfg file).

Whatever value I set in the .cfg file pos will always be -1 and there's 
nothing I can do about it, since I can't choose the logging events topic 
string. Thus, the result will be always "false" and no event will be skipped.

What am I missing?...

Thanks in advance,


Roberto