org.springframework.context.ApplicationContext cannot be found by org.jboss.tools.windup.runtime_3.1.0.qualifier
by Ian Tewksbury
Linconln,
I am trying to get Eclipse to be able to load windup legacy with Forge and have run into the error I think I was running into months ago when I last tried this. The legacy-windup-engine depends on ApplicationContext as a maven dependency but Eclipse/Forage does not seem to be able find the dependency. I have honestly forget how Forge is supposed to work at this point. I thought Forge should automatically be finding all the required dependencies of the jars in the add-on. But maybe I am crazy. Does the addon need to include all the jars that the legacy-windup jars depend on?
Blue Skies,
~Ian
java.lang.NoClassDefFoundError: org/springframework/context/ApplicationContext
at java.lang.Class.getDeclaredMethods0(Native Method)
at java.lang.Class.privateGetDeclaredMethods(Class.java:2531)
at java.lang.Class.getDeclaredMethods(Class.java:1855)
at org.jboss.forge.furnace.proxy.javassist.util.proxy.SecurityActions.getDeclaredMethods(SecurityActions.java:30)
at org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.getMethods(ProxyFactory.java:1121)
at org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.getMethods(ProxyFactory.java:1098)
at org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.makeSortedMethodList(ProxyFactory.java:803)
at org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.computeSignature(ProxyFactory.java:810)
at org.jboss.forge.furnace.proxy.javassist.util.proxy.ProxyFactory.createClass(ProxyFactory.java:398)
at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$3.call(ClassLoaderAdapterCallback.java:987)
at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42)
at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.enhance(ClassLoaderAdapterCallback.java:900)
at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.enhanceResult(ClassLoaderAdapterCallback.java:277)
at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.access$200(ClassLoaderAdapterCallback.java:37)
at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$2.call(ClassLoaderAdapterCallback.java:124)
at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42)
at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.invoke(ClassLoaderAdapterCallback.java:96)
at org.jboss.windup.WindupFactory_$$_javassist_ffb85582-a284-4183-a727-6db372ddc32c.createWindupEngine(WindupFactory_$$_javassist_ffb85582-a284-4183-a727-6db372ddc32c.java)
at org.jboss.tools.windup.core.WindupService.getWindupEngine(WindupService.java:391)
at org.jboss.tools.windup.core.WindupService.getWindupReportEngine(WindupService.java:412)
at org.jboss.tools.windup.core.WindupService.generateReport(WindupService.java:250)
at org.jboss.tools.windup.core.WindupService.generateReport(WindupService.java:186)
at org.jboss.tools.windup.ui.internal.commands.GenerateWindupReportHandler$1.run(GenerateWindupReportHandler.java:78)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Caused by: java.lang.ClassNotFoundException: org.springframework.context.ApplicationContext cannot be found by org.jboss.tools.windup.runtime_3.1.0.qualifier
at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:432)
at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:345)
at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:337)
at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:160)
at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
... 24 more
11 years
Merry Christmas
by Daniel Cunha
Hello Folks,
I just want to wish a Merry Christmas to all.
--
Daniel Cunha (soro)
11 years
Windup Meeting Minutes - 2014-12-17
by Lincoln Baxter, III
Minutes:
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2014/windup....
Minutes (text):
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2014/windup....
Log:
http://transcripts.jboss.org/meeting/irc.freenode.org/windup/2014/windup....
Meeting summary
---------------
* Agenda (lincolnthree, 15:01:57)
* Status Reports (lincolnthree, 15:04:39)
* Finished WINDUP-377 with the help of the team. Rules can now be
{parameterized}. (lincolnthree, 15:05:48)
* Fixed WINDUP-432 - There was a bug in our environment util that
caused windup to break in eclipse. (lincolnthree, 15:06:29)
* I plan on doing some demo-type playing with the xml rules for the
purpose of brainstorming / continuing to look at rule
parameterization and improving the way it works and how rules work
together. (lincolnthree, 15:07:18)
* I also plan to start looking at our test runner failures to see if I
can see what's going on there (lincolnthree, 15:07:36)
* XML's are already merged, briefly checked that the report is the
same and it was, but cannot guarantee (mbriskar, 15:08:03)
* I played a little with Handlers here and there (mbriskar, 15:08:40)
* I tried to make WINDUP-424 with detailed tests so we have handlers
covered (mbriskar, 15:09:15)
* working now on WINDUP-407 (mbriskar, 15:09:40)
* WINDUP-420 - Switched to caching compiled xpath's for some
performance improvement. (maybe 20% on the xml portion of the scan
at most) (jsightler, 15:11:17)
* Fixed a bug that caused --overwrite not to be possible from the
command line (./windup style invocation) (jsightler, 15:12:02)
* Fixed WINDUP-428 that was causing some rules to miss in some cases
(missing links from some source files to JavaClass) (jsightler,
15:13:03)
* , Also fixed WINDUP-427, WINDUP-426, and WINDUP-425 (internal little
API improvements) (jsightler, 15:13:25)
* I am currently working in providing a generalized way to have an
iteration use threads. This would be enabled via calling
Iteration.over().threaded() (optionally specifying the number of
threads) (jsightler, 15:14:11)
* there are some roadblocks around the way titan/blueprints handle
transactions across thread boundaries that are slowing this down at
the moment, but I'm hoping I can have something in the next day or
two (jsightler, 15:14:55)
* Priorities (lincolnthree, 15:26:46)
* #1. Performance and stability (lincolnthree, 15:27:00)
* #2 Making rules more usable (adding more conditions) (lincolnthree,
15:27:26)
* #3 Making the rules work together better and make more sense to the
user (lincolnthree, 15:27:46)
* Weekly Release (lincolnthree, 15:54:13)
* We have a weekly release coming up. Just thought i would mention it
in the meeting. (lincolnthree, 15:54:28)
* This will be the first release that encompasses the new rules params
feature and should be the best performing release yet.
(lincolnthree, 15:55:13)
* Test coverage (lincolnthree, 15:57:27)
* Ideas for how to improve windup (brainstorming) (lincolnthree,
16:17:42)
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
11 years
GraphServiceTest Error
by Ian Tewksbury
All,
I am trying to build windup from master for the first time in a while but running into this error when trying to run a mvn clean install. Am I missing something or are the tests just broken right now?
-------------------------------------------------------------------------------
Test set: org.jboss.windup.graph.typedgraph.graphservice.GraphServiceTest
-------------------------------------------------------------------------------
Tests run: 3, Failures: 0, Errors: 3, Skipped: 0, Time elapsed: 17.857 sec <<< FAILURE! - in org.jboss.windup.graph.typedgraph.graphservice.GraphServiceTest
testGraphSearchWithoutCommit(org.jboss.windup.graph.typedgraph.graphservice.GraphServiceTest) Time elapsed: 0.042 sec <<< ERROR!
java.lang.IllegalStateException: Test runner could not locate test class [org.jboss.windup.graph.typedgraph.graphservice.GraphServiceTest] in any deployed Addon.
Blue Skies,
~Ian
11 years
Re: [windup-dev] What's the standard approach for Migrating WebLogic Work Managers
by Robb Greathouse
Can you send the code example? We will create a rule for that in Windup.
Robb Greathouse
Chief Evangelist
Middleware Business Unit
JBoss, a Division of Red Hat
cellphone 505-507-4906
----- Original Message -----
> Brad/Robb,
>
> I know of two approaches :
> * create a custom JCA adapter that implements the CommonJ code
> * use JMS queues
>
> Which one does consulting recommend when migrating?
>
> Regards,
> Jeremy Davis
> Senior Solution Architect
> jeremy.davis(a)redhat.com
>
>
>
>
>
>
11 years
Re: [windup-dev] LogOperation?
by Lincoln Baxter, III
org.jboss.windup.config.operation.Log
It just needs to be extended to take a java.util.logging.Logger as an argument as an alternative to using its own.
E.g. we currently have:
public static Log message(Level level, String message)
{
return new Log(level, message);
}
We need:
public static Log message(Logger log, Level level, String message)
{
return new Log(log, level, message);
}
~Lincoln
----- Original Message -----
From: "Ondrej Zizka" <ozizka(a)redhat.com>
To: "Lincoln Baxter" <lbaxter(a)redhat.com>
Sent: Tuesday, December 9, 2014 7:59:34 PM
Subject: LogOperation?
Hi Lincoln,
IIUC, you said we have some LogOperation, right?
I can't find it.
Normal logging can only be included in the operation itself, which is
not always desirable, hence the need for LogOperation. Or not?
Thanks,
Ondra
11 years, 1 month
