2:05 p.m.
This would require reports, but we should have the info for these things below that we
wouldn't have had info for in Windup 1:
We can push the functionality for EJB reporting & Resource reporting --- Database and
Queues. Assist folks with generating them in Jboss (either linking to docs for setting up
database or JMS queues or the IBM MQ Resource adapter). Those tasks would show the value
clearly.
* Resources we should generate the XML chunk that should go in JBoss's Standalone.xml
if possible, maybe JBoss CLI as well & link to relevant JBoss documentation (JMS or
Datasource Setup)
* IBM MQ Queues would indicate we need to setup the IBM MQ Resource Adapter and link to
the product docs on doing so with JBoss.
* If an EJB is tied to a Queue, we have that info now in Windup.
* If a message listener is bound in Spring to a Queue, we can get that info in Windup.
* If a Hibernate file leverages a Oracle Dialect & references a named JNDI datasource,
we know it needs to be setup in JBoss.
* If the code manually looks up a datasource, we could write an extractor to pull that out
into the graph as well.
Brad Davis
Senior Manager, Red Hat Consulting
Email: bdavis(a)redhat.com | c: 980.226.7865 | http://www.redhat.com
----- Original Message -----
From: "Ondrej Zizka" <ozizka(a)redhat.com>
To: windup-dev(a)lists.jboss.org
Sent: Monday, March 30, 2015 2:10:09 PM
Subject: Re: [windup-dev] Windup 2.2.0.Final Released
1) More complex rules querying more complex Java constructs / transitive relations etc.
2) Easier and more powerful rules.
Since we first only converted the Windup 1 rules, Windup 2 doesn't give much over
that.
I believe it will as the new rules start coming.
Ondra
On 30.3.2015 16:20, Robb Greathouse wrote:
We still need to justify the additional 30 minutes to clients. At this point it is appears
to give the same report that Windup .7 gave. What can we add to the report to demonstrate
value added for those additional minute?
Robb Greathouse
Middleware Business Unit
JBoss, a Division of Red Hat
cellphone 505-507-4906
Great! Thank you for confirming this! We definitely wanted to get these improvements into
this release, so thank you for your patience as we sorted out some of the issues!
~Lincoln
On Fri, Mar 27, 2015 at 2:48 PM, Robb Greathouse < robb.greathouse(a)redhat.com >
wrote:
Cudos.
Running against the 300~mb test file and restricting it to look at packages com.clarify it
runs in about 40 minutes vs the old time of 20 hours plus. Definite performance
improvement.
Robb Greathouse
Middleware Business Unit
JBoss, a Division of Red Hat
cellphone 505-507-4906
I am proud to announce the release of Windup 2.2.0.Final, which includes the following
features/enhanvements/and bugfixes.
Great job team!
~Lincoln
Bug
* [ WINDUP-510 ] - Build fails with BOM missing
* [ WINDUP-511 ] - Quickstarts tests fail with a NPE
* [ WINDUP-516 ] - [Performance] Multiple valueStores even if the rule does not use
parameters
* [ WINDUP-517 ] - Application Index page lacks technology list and effort information
* [ WINDUP-518 ] - XML Handlers do not support nested rules
* [ WINDUP-524 ] - Fix the cyclic dependency between windup and windup-rulesets
* [ WINDUP-542 ] - Fix severe regression in AST performance
* [ WINDUP-544 ] - StackOverflowException when generating Application report
Enhancement
* [ WINDUP-409 ] - Allow rules metadata to be specified with annotations - @Rules(
phase = ..., ...)
* [ WINDUP-470 ] - Classes in java.lang package may differ in how they are parsed
* [ WINDUP-506 ] - Identify Archives Ruleset: Improve memory footprint
* [ WINDUP-508 ] - WindupRuleProvider should contain a location/origin field (to
indicate where it was defined)
* [ WINDUP-515 ] - Add Severity to Hint
* [ WINDUP-520 ] - Rule Externalization - Introduce a Rule, RuleProvider and
RulesetMetadata API
* [ WINDUP-529 ] - Performance issue: Query requires iterating over all vertices
[(ClassificationModel:classification = ...)]
Feature Request
* [ WINDUP-402 ] - Change ruleset category metadata to tag-like system (make it a set
of strings)
* [ WINDUP-521 ] - Rule Externalization - Create XML Handlers for Rule metadata
* [ WINDUP-522 ] - Rule Externalization - Create user-interface for selecting
source/target platforms
* [ WINDUP-523 ] - Rule Externalization - Allow filtering of RuleProviders by tags
(categories)
Task
* [ WINDUP-512 ] - Rename Implicit to Dependent
* [ WINDUP-513 ] - Phase pseudo-RuleProviders to have ~Phase suffix
* [ WINDUP-530 ] - Rename the module "utils" to "windup-utils"
Sub-task
* [ WINDUP-464 ] - Expand all addons with simple layout to use full api/impl/tests
structure
* [ WINDUP-465 ] - Review all rules, organize into an external repository, and add
useful hint information with links to knowledge articles
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
_______________________________________________
windup-dev mailing list
windup-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/windup-dev
_______________________________________________
windup-dev mailing list windup-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/windup-dev
_______________________________________________
windup-dev mailing list
windup-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/windup-dev