EAP6-EAP7 migration
by Matej Briskar
Hello team,
there are new issues in the jira issues tracker for migrating EAP6->EAP7 thanks to Eduardo. Currently we have 3 new issues (https://issues.jboss.org/browse/WINDUPRULE-66).
We have two ways we may resolve them:
a) create XSLT - this will take a lot of time, but user may love us for it
b) put there only hint - simple to do.
Not sure which way to go and if we have some time to spend doing XSLT. (estimation is 1 week for 1 XSLT transformation).
10 years
Re: [windup-dev] quickstarts
by Marek Novotny
Right, I prefer to keep them updated and released as they are probably
the simplest form how to look at basic examples of Java or XML Rules.
And Windup documentation references them for this purpose I guess, so we
would lost a simpler target to point to.
On 24.9.2015 18:09, Rodney Russ wrote:
> Well, they look like they at least have use based on the documentation
> (e.g. simple examples to look at), but I thought it was at least worth
> the question.
>
>
> On 24 Sep 2015, at 9:46, Jess Sightler wrote:
>
>> I have often wondered if we have anyone using them. I don't know,
>> though. I know that we never seem to hear questions about them.
>>
>> On 09/24/2015 08:10 AM, Rodney Russ wrote:
>>> Thanks, Marek. I asked as they were referenced in the docs and I
>>> wanted to be sure they were up to date if this was going to be the case.
>>>
>>> As a side note, does anyone think they aren't needed or aren't useful
>>> (i.e. should we stop maintaining and referencing them)?
>>>
>>>
>>> On 24 Sep 2015, at 2:52, Marek Novotny wrote:
>>>
>>>> On 24.9.2015 09:56, Marek Novotny wrote:
>>>>>
>>>>> On 24.9.2015 01:48, Rodney Russ wrote:
>>>>>> Have these been tested/looked at for 2.4.0.CR1?
>>>>>>
>>>>>> https://github.com/windup/windup-quickstarts
>>>>>>
>>>>>
>>>>> I don't think as they are still pointing to windup 2.3.0.Final
>>>>> (https://github.com/windup/windup-quickstarts/blob/master/pom.xml#L7)
>>>>>
>>>>
>>>> I created https://issues.jboss.org/browse/WINDUP-776 as I looked at XML
>>>> rules and they need to be updated too.
>>>>
>>>> --
>>>> Marek Novotny
>>>> --
>>>> Windup team member and Seam Project Lead
>>>>
>>>> Red Hat Czech s.r.o.
>>>> Purkynova 99
>>>> 612 45 Brno
--
Marek Novotny
--
Windup team member and Seam Project Lead
Red Hat Czech s.r.o.
Purkynova 99
612 45 Brno
10 years
Escaping in templates - <#escape x as x?html>
by Ing. Ondřej Žižka
I think we should add <#escape x as x?html> to all templates - unless
there's a reason not to. Is there?
This directive makes all ${...}'s HTML-escaped.
Regards,
Ondra
10 years
JSP / JSP / Taglib Parsing & Rules
by Brad Davis
One of my projects leverages Richfaces 3 and we need to move to 4. It would be very helpful to expand upon the (basic) JSP rules that we had in Windup 0.7 with actual JSP parsing in Windup 2.4. Because we leverage Eclipse for AST with Java, I wonder if we can do the same thing for JSF / JSP? Maybe we can reach out to one of the project leads in the Eclipse community to get their recommendation on which project would provide similar functionality for those technologies. I think Nick Sandonato from the Eclipse WTP team may be a good starting point.
There is a migration guide at: https://developer.jboss.org/wiki/RichFaces33-4xMigrationGuideUnleashed
I guess we could use old-fashioned XPath and probably get a lot of the way, but I think in Windup 1 this fell down around <% %> / embedded code. Thoughts?
Brad Davis
Senior Manager, Red Hat Consulting
Email: bdavis(a)redhat.com | c: 980.226.7865 | http://www.redhat.com
10 years
Freemarker shortcut for lists
by Ondrej Zizka
Hi team,
instead this
<#if
getTechnologyTagsForFile(reportModel.sourceFileModel).iterator()?has_content>
<dt>Technologies</dt>
<dd>
<#list
getTechnologyTagsForFile(reportModel.sourceFileModel).iterator() as techTag>
<span class="label
label-info">${techTag.name}</span>
</#list>
</dd>
</#if>
which, besides ugly syntax, affects performance, Freemarker has this
alternative:
<#list
getTechnologyTagsForFile(reportModel.sourceFileModel).iterator() >
<dt>Technologies</dt>
<dd>
<#items as techTag>
<span class="label
label-info">${techTag.name}</span>
</#items>
</dd>
</#list>
HTH,
Ondra
10 years, 1 month
JBoss Web Framework Kit -- Good Migration Option
by Brad Davis
I have largely ignored the JBoss Web Framework Kit, but it should be something we are actively looking at for migrations. We could be pushing it when we see versions of Seam, Struts, Spring that aren't otherwise in JBoss EAP 6.x but that is their target. In other words, if the customer doesn't want to rewrite things but just wants support on the newest server, it might be an option. We are exploring this with one of our customers currently, and I think it is a good options in some scenarios.
https://access.redhat.com/articles/112543
Basically path of least resistance upgrades.
Brad Davis
Senior Manager, Red Hat Consulting
Email: bdavis(a)redhat.com | c: 980.226.7865 | http://www.redhat.com
10 years, 1 month
Features for Discussion
by Brad Davis
I'd like to have the following features, but wanted to get everyone's feedback.
1) The ability to read in effort from the XML files.
User Story: User runs Windup report and doesn't agree with the effort estimate. They would like to change the effort for a Java rule and rerun Windup, but aren't technical enough to recompile Windup.
Proposed Solution: Having a utility that we could use to easily look up a property from the Windup XML configuration would be a great solution for this. That way, it makes it easy for people to modify the effort.
2) The ability to override and disable rules from the XML.
User Story: A Java rule is not providing anticipated output and needs to be excluded from the report.
Proposed Solution: Have a simple registry of disabled rules in the XML, where the qualified Java class is provided that needs to be disabled / skipped.
Brad Davis
Senior Manager, Red Hat Consulting
Email: bdavis(a)redhat.com | c: 980.226.7865 | http://www.redhat.com
10 years, 1 month
