unsubscribe
unsubscribe
Re: 3.0.0RC1 - Karaf WebConsole in Equinox Issue
Thanks! Is there a tracking bug logged for this, so that we get to know when it's fixed? -Aritra On Mon, Apr 1, 2013 at 2:42 PM, Jean-Baptiste Onofré wrote: > Hi Aritra, > > yes it's a "known" issue, I'm working on it. > > It should be fixed in the following days (on 3.0.0-SNAPSHOT). > > Regards > JB > > > On 04/01/2013 10:20 AM, Aritra Chatterjee wrote: >> >> Hi, >> >> I am trying to run 3.0.0 RC1 karaf with Equinox container (Changed >> felix to equinox in config.properties). The launch does not cause any >> issues, however, on issuing the command feature:install webconsole, I >> get the following stack trace in the log file: >> >> 2013-03-28 20:18:22,676 | INFO | Local user karaf | >> FeaturesServiceImpl | 42 - org.apache.karaf.features.core >> - 3.0.0.RC1 | Installing feature webconsole 3.0.0.RC1 >> 2013-03-28 20:18:22,676 | INFO | Local user karaf | >> FeaturesServiceImpl | 42 - org.apache.karaf.features.core >> - 3.0.0.RC1 | Installing feature http 3.0.0.RC1 >> 2013-03-28 20:18:22,677 | INFO | Local user karaf | >> FeaturesServiceImpl | 42 - org.apache.karaf.features.core >> - 3.0.0.RC1 | Installing feature pax-http 3.0.0.M3 >> 2013-03-28 20:18:22,677 | INFO | Local user karaf | >> FeaturesServiceImpl | 42 - org.apache.karaf.features.core >> - 3.0.0.RC1 | Installing feature pax-jetty 8.1.9.v20130131 >> 2013-03-28 20:18:22,789 | INFO | Local user karaf | >> FeaturesServiceImpl | 42 - org.apache.karaf.features.core >> - 3.0.0.RC1 | Installing feature standard-condition-webconsole_0_0_0 >> 3.0.0.RC1 >> 2013-03-28 20:18:22,824 | INFO | Local user karaf | ShellUtil >> | 48 - org.apache.karaf.shell.console - 3.0.0.RC1 | >> Exception caught while executing command >> java.lang.NoSuchMethodError: >> org.osgi.framework.Version.toString0()Ljava/lang/String; >> at >> org.osgi.framework.VersionRange.toString(VersionRange.java:393)[osgi-3.8.0.v20120529-1548.jar:] >> at java.lang.String.valueOf(String.java:2838)[:1.6.0_27] >> at java.lang.StringBuffer.append(StringBuffer.java:236)[:1.6.0_27] >> at >> org.eclipse.osgi.internal.resolver.ImportPackageSpecificationImpl.toString(ImportPackageSpecificationImpl.java:212) >> at >> org.eclipse.osgi.internal.module.ResolverBundle.constraintsConflict(ResolverBundle.java:453) >> at >> org.eclipse.osgi.internal.module.ResolverImpl.checkFragmentConstraints(ResolverImpl.java:1419) >> at >> org.eclipse.osgi.internal.module.ResolverImpl.resolveBundle(ResolverImpl.java:1389) >> at >> org.eclipse.osgi.internal.module.ResolverImpl.resolveBundles0(ResolverImpl.java:783) >> at >> org.eclipse.osgi.internal.module.ResolverImpl.resolveBundles(ResolverImpl.java:653) >> at >> org.eclipse.osgi.internal.module.ResolverImpl.resolve(ResolverImpl.java:487) >> at >> org.eclipse.osgi.internal.resolver.StateImpl.resolve(StateImpl.java:481) >> at >> org.eclipse.osgi.internal.resolver.StateImpl.resolve(StateImpl.java:557) >> at >> org.eclipse.osgi.framework.internal.core.PackageAdminImpl.doResolveBundles(PackageAdminImpl.java:249) >> at >> org.eclipse.osgi.framework.internal.core.PackageAdminImpl.resolveBundles(PackageAdminImpl.java:192) >> at >> org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:322) >> at >> org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:300) >> at >> org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:292) >> at >> org.apache.karaf.features.internal.FeaturesServiceImpl.startBundle(FeaturesServiceImpl.java:465) >> at >> org.apache.karaf.features.internal.FeaturesServiceImpl.installFeatures(FeaturesServiceImpl.java:424) >> at >> org.apache.karaf.features.internal.FeaturesServiceImpl.installFeature(FeaturesServiceImpl.java:360) >> at >> org.apache.karaf.features.internal.FeaturesServiceImpl.installFeature(FeaturesServiceImpl.java:349) >> at Proxya9a053f2_4c25_46d2_b119_7f6c6cac394f.installFeature(Unknown >> Source) >> at >> org.apache.karaf.features.command.InstallFeatureCommand.doExecute(InstallFeatureCommand.java:62) >> at >> org.apache.karaf.features.command.FeaturesCommandSupport.doExecute(FeaturesCommandSupport.java:38) >> at >> org.apache.karaf.shell.console.AbstractAction.execute(AbstractAction.java:33) >> at >> org.apache.karaf.shell.console.OsgiCommandSupport.execute(OsgiCommandSupport.java:39) >> at >> org.apache.karaf.shell.commands.basic.AbstractComm
3.0.0RC1 - Karaf WebConsole in Equinox Issue
org.apache.karaf.shell.console.impl.jline.ConsoleImpl.run(ConsoleImpl.java:182) at java.lang.Thread.run(Thread.java:679)[:1.6.0_27] at org.apache.karaf.shell.console.impl.jline.ConsoleFactoryService$3.doRun(ConsoleFactoryService.java:102)[48:org.apache.karaf.shell.console:3.0.0.RC1] at org.apache.karaf.shell.console.impl.jline.ConsoleFactoryService$3$1.run(ConsoleFactoryService.java:93) at java.security.AccessController.doPrivileged(Native Method)[:1.6.0_27] at javax.security.auth.Subject.doAs(Subject.java:357)[:1.6.0_27] at org.apache.karaf.shell.console.impl.jline.ConsoleFactoryService$3.run(ConsoleFactoryService.java:91)[48:org.apache.karaf.shell.console:3.0.0.RC1] Any solutions for this? Regards, Aritra Chatterjee
Re: Karaf Maven Plugin fails with pax-http error
Created https://issues.apache.org/jira/browse/KARAF-2212 to track this.
On Thu, Feb 28, 2013 at 2:51 AM, Achim Nierbeck wrote:
> Hi,
>
> just recently we started to use the pax-web features.
> could you open a jira issue for it?
> I'm gonna take a look at it.
>
> regards, Achim
>
>
> 2013/2/21 Aritra Chatterjee
>>
>> Hi,
>>
>> I am using Karaf Maven Plugin 3.0 for creating a custom Karaf
>> distribution for my application. All was working fine till recently.
>> My maven build fails with the following error:
>>
>> [ERROR] Failed to execute goal
>>
>> org.apache.karaf.tooling:karaf-maven-plugin:3.0.0-SNAPSHOT:features-add-to-repository
>> (features-add-to-repository) on project apache-karaf: Error populating
>> repository: Unable to find the feature 'pax-http' -> [Help 1]
>>
>> Here's what my pom.xml looks like, the plugin and dependencies section:
>>
>> apache-karaf
>> pom
>> Custom Karaf Distribution
>>
>>
>> org.apache.karaf
>> apache-karaf
>> ${karaf.version}
>> tar.gz
>>
>>
>>
>>
>>
>>
>> org.apache.karaf.tooling
>> karaf-maven-plugin
>>
>>
>>
>> features-add-to-repository
>>
>> generate-resources
>>
>>
>> features-add-to-repository
>>
>>
>>
>>
>>
>> mvn:org.apache.karaf.features/spring/${karaf.version}/xml/features
>>
>>
>>
>> config
>>
>> standard
>>
>> region
>>
>> package
>>
>> kar
>>
>> ssh
>>
>> management
>>
>> webconsole
>>
>> spring
>>
>> spring-jms
>>
>> spring-tx
>>
>>
>> target/features-repo
>>
>>
>>
>>
>>
>>
>>
>> Is the pax-http feature used internally by Karaf? I tried removing the
>> webconsole feature, but it doesn't fix the build error. Any clues how
>> this could be solved?
>>
>> Regards,
>> Aritra Chatterjee
>
>
>
>
> --
>
> Apache Karaf <http://karaf.apache.org/> Committer & PMC
> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer &
> Project Lead
> OPS4J Pax for Vaadin <http://team.ops4j.org/wiki/display/PAXVAADIN/Home>
> Commiter & Project Lead
> blog <http://notizblog.nierbeck.de/>
--
Aritra Chatterjee
Software Engineer - II
FICO,
Ground Floor,
135, Titanium Building,
Old Airport Road, Kodihalli
Landmark: Opposite Leela Palace
Bangalore.
Pin: 560017
M +91-9901700144
T(Off.) +91-80 413 71672
Re: Karaf 3.0.0 Console Extender
Got it. The 3.0.0 documentation does not reflect this change. Hopefully that will be updated soon. On Jan 17, 2013 12:39 PM, "ksobkowiak" wrote: > Hi > > As stated in https://issues.apache.org/jira/browse/KARAF-1001 the > attribute > "name" has been removed from the in 3.x and the command name can > be only configured using the @Command annotation. Please remove the > attribute from your blueprint file. > > Best regards > Krzysztof > > > > -- > View this message in context: > http://karaf.922171.n3.nabble.com/Karaf-3-0-0-Console-Extender-tp4027276p4027360.html > Sent from the Karaf - User mailing list archive at Nabble.com. >
Karaf 3.0.0 Console Extender
XMLSchemaValidator.reportSchemaError(XMLSchemaValidator.java:3186)[:1.6.0_24] at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.processAttributes(XMLSchemaValidator.java:2663)[:1.6.0_24] at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.handleStartElement(XMLSchemaValidator.java:2070)[:1.6.0_24] at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.startElement(XMLSchemaValidator.java:709)[:1.6.0_24] at com.sun.org.apache.xerces.internal.jaxp.validation.DOMValidatorHelper.beginNode(DOMValidatorHelper.java:276)[:1.6.0_24] at com.sun.org.apache.xerces.internal.jaxp.validation.DOMValidatorHelper.validate(DOMValidatorHelper.java:243)[:1.6.0_24] at com.sun.org.apache.xerces.internal.jaxp.validation.DOMValidatorHelper.validate(DOMValidatorHelper.java:189)[:1.6.0_24] at com.sun.org.apache.xerces.internal.jaxp.validation.ValidatorImpl.validate(ValidatorImpl.java:108)[:1.6.0_24] at javax.xml.validation.Validator.validate(Unknown Source)[:2.2.0] at org.apache.aries.blueprint.parser.Parser.validate(Parser.java:285)[25:org.apache.aries.blueprint.core:1.0.1] ... 23 more Any clue how to resolve this? Regards, Aritra Chatterjee
Using AspectJ with Karaf
Hi, I need to use AspectJ in my OSGi project. I am using Karaf 3.0.0-SNAPSHOT as my project uses gemini-blueprint. I am following this ( http://dywicki.pl/2011/11/running-aspects-under-osgi-4-2-with-karaf/) link to enable aspect weaving. However, I am not able to automate the process using features/kar packaging. The method mentioned in the blog only works if I do the steps manually. I need to use AspectJ because I am trying to use the wormhole pattern to pass user context from front-end to the persistence layer, and switch the database based on the user context information received in the front-end. Is there a way this can be automated? Are there any alternatives to do this in Karaf? If yes, it will help to get some relevant examples/documentation. Regards, Aritra Chatterjee
