New fernflower fork project
by Jess Sightler
I have created a new project within Windup for maintaining a fork of
Fernflower with Java 7 compatibility and a Maven pom. Maybe we can start
releasing and keeping this up to date separately from windup core?
It is here:
https://github.com/windup/windup-fernflower
I think we can switch Windup to use this as part of 2.6.0, if noone
objects to that.
8 years, 7 months
Deployment / run exceptions analysis use case // Fwd: Re: Java_opts, memory, cannot reset buffer???
by Ondrej Zizka
On the F2F meeting, I suggested to include the deployment / run
exceptions analysis amongst long term goals for Windup.
This is a use case.
Ondra
-------- Forwarded Message --------
Subject: Re: Java_opts, memory, cannot reset buffer???
Date: Tue, 26 Apr 2016 18:04:15 +0200
From: Oscar Arribas <oscar(a)redhat.com>
To: Qadeer Khan <qkhan(a)redhat.com>
CC: jboss-migration(a)redhat.com
Hi Qadeer,
see https://access.redhat.com/solutions/30513
Best regards,
Oscar.
On Tue, Apr 26, 2016 at 5:49 PM, Qadeer Khan <qkhan(a)redhat.com
<mailto:qkhan@redhat.com>> wrote:
We are getting these error messages during run time on EAP 6.4
server. We recently migrated an application from EAP 5 to EAP 6.4
------------------------------
1. ERROR
[org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/wac-ia].[jsp]]
(http-127.0.0.1/127.0.0.1:8080-4) JBWEB000236: Servlet.service() for
servlet jsp threw exception: javax.servlet.jsp.JspException:
JBWEB004062: Unable to compile class for JSP:
2. JBWEB004061: An error occurred at line: 90 in the generated java
file:
C:\jboss6\standalone\tmp\work\jboss.web\default-host\wac-ia\org\apache\jsp\pages\content\credit_005frisk_005fdecision_005fcontent_jsp.java
The code of method _jspService(HttpServletRequest,
HttpServletResponse) is exceeding the 65535 bytes limit
3. ERROR
[org.apache.catalina.core.ContainerBase.[jboss.web].[default-host]]
(http-127.0.0.1/127.0.0.1:8080-4) JBWEB000313: Exception processing
error page /prepareExceptionOccured.do:
java.lang.IllegalStateException: JBWEB000029: Cannot reset buffer
after response has been committed
-------------------------------
I am not sure if it is related to JAVA_OPTS setting but that's what
we have for JAVA_OPTS
"JAVA_OPTS=-Xms256m -Xmx1024m -XX:MaxPermSize=256m.
We are using servlet version 3.0 and server RAM is 6G.
Appreciate any insight into the problem and any recommendation on
how to resolve it?
Regards
Qadeer Khan - RHCJA,RHCSA
RedHat Consulting - Public Sector
Senior Consultant
Mobile: 703-798-5621
Email: qkhan(a)redhat.com <mailto:qkhan@redhat.com>
http://www.redhat.com
8 years, 8 months
Lucene CCEx - ClassCastException: class org.apache.lucene.codecs.lucene40.Lucene40PostingsFormat
by Ondrej Zizka
Hi team,
after rebase, I started getting this Lucene exception.
Did we change the version of Lucene used?
Caused by: java.lang.ClassCastException: class
org.apache.lucene.codecs.lucene40.Lucene40PostingsFormat
at java.lang.Class.asSubclass(Class.java:3404)
at
org.apache.lucene.util.SPIClassIterator.next(SPIClassIterator.java:141)
at
org.apache.lucene.util.NamedSPILoader.reload(NamedSPILoader.java:65)
at
org.apache.lucene.util.NamedSPILoader.<init>(NamedSPILoader.java:47)
at
org.apache.lucene.util.NamedSPILoader.<init>(NamedSPILoader.java:37)
at
org.apache.lucene.codecs.PostingsFormat.<clinit>(PostingsFormat.java:44)
... 47 more
8 years, 8 months
Enum and Enum constants as a javaclass condition
by Marek Novotny
Windup team,
I am looking for a help/advice how to create Javaclass condition for
usages of Enums and more specifically Enum constants.
It seems that current features supported in
org.jboss.windup.ast.java.data.TypeReferenceLocation is not enough to
recognize Enums outside import declaration.
Am I something overlooking or it is not just implemented - created
https://issues.jboss.org/browse/WINDUP-1002 for the follow up.
--
Marek Novotny
--
Windup team member and Seam Project Lead
Red Hat Czech s.r.o.
Purkynova 99
612 45 Brno
8 years, 8 months
Re: [windup-dev] Fwd: [WindUp] Regular expression to detect filesystem paths
by Ondrej Zizka
Hi Roman,
1) Yes, the rule seems useful, thanks! You can create a PR, or shall I?
2) How about leaving out the <where>:
<filecontent filename="{*}.jsp" pattern="import=""" />
<where> is generally useful if you need to match a regex, or refer to
the value somewhere else in the rule.
Ondra
On 21.4.2016 09:40, Roman Martin Gil wrote:
> Thanks Ondrej, my latest rule version is working as I want.
>
> Now I create a new rule to identify page import definitions empty (<%@
> page import="" %>, .... this line in WAS is working
> successfully 🤔 but in EAP not (compile error).
>
> <rule id="jsp-empty-imports">
> <when>
> <filecontent filename="{*}.jsp" pattern="import={emptyString}" />
> </when>
> <perform>
> <hint message="Empty imports definition in a jsp" effort="1"
> severity="mandatory">
> <message>
> Empty import definitions in .jsp or .jspf
> files will fail in compilation time. It is needed to
> remove them.
> </message>
> </hint>
> </perform>
> <where param="emptyString">
> <matches pattern="("")" />
> </where>
> </rule>
>
>
> I think that rule is also important in other migrations so WindUp
> could introduce in its global rules. What do you think?
>
> Regards
>
> On Thu, Apr 21, 2016 at 4:58 AM, Ondrej Zizka <ozizka(a)redhat.com
> <mailto:ozizka@redhat.com>> wrote:
>
> For the cases like "Message: ", i'd suggest to use negative
> lookbehind:
>
> (?<!\w)[a-z]:[\\\\|/]
>
> Which basically says, make sure there's no word character prior to
> the potential drive letter.
>
> Ondra
>
>
>
> On 20.4.2016 16:02, Marek Novotny wrote:
>
> forgot to include Romain in CC
>
> On 20.4.2016 16:01, Brad Davis wrote:
>
> +1 -- it is not only important for Windows to Linux, but
> also for identifying file read / writes that need to be
> mounted for cloud deployments to things like OpenShift.
>
> Brad Davis
> Director of FSI Solutions, Red Hat Consulting
> Email: bdavis(a)redhat.com <mailto:bdavis@redhat.com> | c:
> 980.226.7865 <tel:980.226.7865> | http://www.redhat.com
>
> ----- Original Message -----
> From: "Marek Novotny" <mnovotny(a)redhat.com
> <mailto:mnovotny@redhat.com>>
> To: "Windup-dev List" <windup-dev(a)lists.jboss.org
> <mailto:windup-dev@lists.jboss.org>>
> Sent: Wednesday, April 20, 2016 9:49:31 AM
> Subject: [windup-dev] Fwd: [WindUp] Regular expression to
> detect filesystem paths
>
> adding windup-dev ml as this could be interested to Windup
> community.
>
>
> Romain,
>
> I would go with simplified pattern for every unique
> occurrence to more
> more general one.
>
> So try to use <or></or> and condition patterns in it.
> Something like the following:
>
> <rule id="filesystem-paths-properties">
> <when>
> <or>
> <filecontent
> filename="{*}.{extensions}"
> pattern="{filesystem}" />
> <filecontent
> filename="{*}.{extensions}"
> pattern="{netfilesystem}" />
> <filecontent
> filename="{*}.{extensions}"
> pattern="page import="{filesystem}" />
> </or>
> </when>
> <perform>
> <hint message="File system properties"
> effort="1"
> severity="mandatory">
> <message>
> TODO
> </message>
> </hint>
> </perform>
> <where param="extensions">
> <matches
> pattern="(java|properties|jsp|jpsf|tag|xml|txt)" />
> </where>
> <where param="filesystem">
> <matches pattern="(\S:[\\|/])" />
> </where>
> <where param="netfilesystem">
> <matches pattern="(\\\\ntfileserver\)" />
> </where>
> <where param="netfilesystem">
> <matches pattern="" />
> </where>
> </rule>
>
> -------- Forwarded Message --------
> Subject: [WindUp] Regular expression to detect
> filesystem paths
> Date: Wed, 20 Apr 2016 15:29:03 +0200
> From: Roman Martin Gil <rmarting(a)redhat.com
> <mailto:rmarting@redhat.com>>
> To: Marek Novotny <mnovotny(a)redhat.com
> <mailto:mnovotny@redhat.com>>
>
>
>
> Hi,
>
> I am very obfuscated to create a rule to identify some
> filesystem paths
> patterns. I am trying to detect when the code (.java,
> .properties) have
> the following entries:
>
> * "c:\\"
> * "e:\\"
> * "c:/"
> * "e:/"
> * "\\\\ntfileserver\"
> * "page import="""
>
>
> My first approach is similar to:
>
> <rule id="filesystem-paths-properties">
> <when>
> <filecontent filename="{*}.{extensions}"
> pattern="{filesystem}" />
> </when>
> <perform>
> <hint message="File system properties"
> effort="1"
> severity="mandatory">
> <message>
> TODO
> </message>
> </hint>
> </perform>
> <where param="extensions">
> <matches
> pattern="(java|properties|jsp|jpsf|tag|xml|txt)" />
> </where>
> <where param="filesystem">
> <matches pattern="((c|e):|[\\])" />
> </where>
> </rule>
>
> However I am detecting cases as "Message: " as a pattern.
> How could I
> create a rule to identify these cases?
>
> Thank you very much in advance
>
> PD: What is the better mail list to send it?
>
>
>
>
>
>
>
> --
>
> Saludos/Best regards
> ______________________________________________________________________
> *Jose Roman Martin Gil *
> /MW Senior Architect/ | +34 605 926 271 | roman.martin(a)redhat.com
> <mailto:roman.martin@redhat.com>
>
> //*Red Hat* Iberia
> C/ José Bardasano Baos, 9, Edif. Gorbea 3, planta 3ºD, 28016 Madrid, Spain
> ______________________________________________________________________
>
8 years, 8 months
Re: [windup-dev] Fwd: [WindUp] Regular expression to detect filesystem paths
by Marek Novotny
Cool, I read your yesterday email and suggested " instead of " and
now I see you made it yourself, great!
On 21.4.2016 09:40, Roman Martin Gil wrote:
> Thanks Ondrej, my latest rule version is working as I want.
>
> Now I create a new rule to identify page import definitions empty (<%@
> page import="" %>, .... this line in WAS is working successfully 🤔 but
> in EAP not (compile error).
>
> <rule id="jsp-empty-imports">
> <when>
> <filecontent filename="{*}.jsp" pattern="import={emptyString}" />
> </when>
> <perform>
> <hint message="Empty imports definition in a jsp" effort="1"
> severity="mandatory">
> <message>
> Empty import definitions in .jsp or .jspf files
> will fail in compilation time. It is needed to
> remove them.
> </message>
> </hint>
> </perform>
> <where param="emptyString">
> <matches pattern="("")" />
> </where>
> </rule>
>
>
> I think that rule is also important in other migrations so WindUp could
> introduce in its global rules. What do you think?
>
> Regards
>
> On Thu, Apr 21, 2016 at 4:58 AM, Ondrej Zizka <ozizka(a)redhat.com
> <mailto:ozizka@redhat.com>> wrote:
>
> For the cases like "Message: ", i'd suggest to use negative lookbehind:
>
> (?<!\w)[a-z]:[\\\\|/]
>
> Which basically says, make sure there's no word character prior to
> the potential drive letter.
>
> Ondra
>
>
>
> On 20.4.2016 16:02, Marek Novotny wrote:
>
> forgot to include Romain in CC
>
> On 20.4.2016 16:01, Brad Davis wrote:
>
> +1 -- it is not only important for Windows to Linux, but
> also for identifying file read / writes that need to be
> mounted for cloud deployments to things like OpenShift.
>
> Brad Davis
> Director of FSI Solutions, Red Hat Consulting
> Email: bdavis(a)redhat.com <mailto:bdavis@redhat.com> | c:
> 980.226.7865 <tel:980.226.7865> | http://www.redhat.com
>
> ----- Original Message -----
> From: "Marek Novotny" <mnovotny(a)redhat.com
> <mailto:mnovotny@redhat.com>>
> To: "Windup-dev List" <windup-dev(a)lists.jboss.org
> <mailto:windup-dev@lists.jboss.org>>
> Sent: Wednesday, April 20, 2016 9:49:31 AM
> Subject: [windup-dev] Fwd: [WindUp] Regular expression to
> detect filesystem paths
>
> adding windup-dev ml as this could be interested to Windup
> community.
>
>
> Romain,
>
> I would go with simplified pattern for every unique
> occurrence to more
> more general one.
>
> So try to use <or></or> and condition patterns in it.
> Something like the following:
>
> <rule id="filesystem-paths-properties">
> <when>
> <or>
> <filecontent filename="{*}.{extensions}"
> pattern="{filesystem}" />
> <filecontent filename="{*}.{extensions}"
> pattern="{netfilesystem}" />
> <filecontent filename="{*}.{extensions}"
> pattern="page import="{filesystem}" />
> </or>
> </when>
> <perform>
> <hint message="File system properties"
> effort="1"
> severity="mandatory">
> <message>
> TODO
> </message>
> </hint>
> </perform>
> <where param="extensions">
> <matches
> pattern="(java|properties|jsp|jpsf|tag|xml|txt)" />
> </where>
> <where param="filesystem">
> <matches pattern="(\S:[\\|/])" />
> </where>
> <where param="netfilesystem">
> <matches pattern="(\\\\ntfileserver\)" />
> </where>
> <where param="netfilesystem">
> <matches pattern="" />
> </where>
> </rule>
>
> -------- Forwarded Message --------
> Subject: [WindUp] Regular expression to detect
> filesystem paths
> Date: Wed, 20 Apr 2016 15:29:03 +0200
> From: Roman Martin Gil <rmarting(a)redhat.com
> <mailto:rmarting@redhat.com>>
> To: Marek Novotny <mnovotny(a)redhat.com
> <mailto:mnovotny@redhat.com>>
>
>
>
> Hi,
>
> I am very obfuscated to create a rule to identify some
> filesystem paths
> patterns. I am trying to detect when the code (.java,
> .properties) have
> the following entries:
>
> * "c:\\"
> * "e:\\"
> * "c:/"
> * "e:/"
> * "\\\\ntfileserver\"
> * "page import="""
>
>
> My first approach is similar to:
>
> <rule id="filesystem-paths-properties">
> <when>
> <filecontent filename="{*}.{extensions}"
> pattern="{filesystem}" />
> </when>
> <perform>
> <hint message="File system properties"
> effort="1"
> severity="mandatory">
> <message>
> TODO
> </message>
> </hint>
> </perform>
> <where param="extensions">
> <matches
> pattern="(java|properties|jsp|jpsf|tag|xml|txt)" />
> </where>
> <where param="filesystem">
> <matches pattern="((c|e):|[\\])" />
> </where>
> </rule>
>
> However I am detecting cases as "Message: " as a pattern.
> How could I
> create a rule to identify these cases?
>
> Thank you very much in advance
>
> PD: What is the better mail list to send it?
>
>
>
>
>
>
>
> --
>
> Saludos/Best regards
> ______________________________________________________________________
> *Jose Roman Martin Gil *
> /MW Senior Architect/ | +34 605 926 271 | roman.martin(a)redhat.com
> <mailto:roman.martin@redhat.com>
>
> /**/*Red Hat* Iberia
> C/ José Bardasano Baos, 9, Edif. Gorbea 3, planta 3ºD, 28016 Madrid, Spain
> ______________________________________________________________________
>
--
Marek Novotny
--
Windup team member and Seam Project Lead
Red Hat Czech s.r.o.
Purkynova 99
612 45 Brno
8 years, 8 months
Fwd: [WindUp] Regular expression to detect filesystem paths
by Marek Novotny
adding windup-dev ml as this could be interested to Windup community.
Romain,
I would go with simplified pattern for every unique occurrence to more
more general one.
So try to use <or></or> and condition patterns in it.
Something like the following:
<rule id="filesystem-paths-properties">
<when>
<or>
<filecontent filename="{*}.{extensions}"
pattern="{filesystem}" />
<filecontent filename="{*}.{extensions}"
pattern="{netfilesystem}" />
<filecontent filename="{*}.{extensions}"
pattern="page import="{filesystem}" />
</or>
</when>
<perform>
<hint message="File system properties" effort="1"
severity="mandatory">
<message>
TODO
</message>
</hint>
</perform>
<where param="extensions">
<matches pattern="(java|properties|jsp|jpsf|tag|xml|txt)" />
</where>
<where param="filesystem">
<matches pattern="(\S:[\\|/])" />
</where>
<where param="netfilesystem">
<matches pattern="(\\\\ntfileserver\)" />
</where>
<where param="netfilesystem">
<matches pattern="" />
</where>
</rule>
-------- Forwarded Message --------
Subject: [WindUp] Regular expression to detect filesystem paths
Date: Wed, 20 Apr 2016 15:29:03 +0200
From: Roman Martin Gil <rmarting(a)redhat.com>
To: Marek Novotny <mnovotny(a)redhat.com>
Hi,
I am very obfuscated to create a rule to identify some filesystem paths
patterns. I am trying to detect when the code (.java, .properties) have
the following entries:
* "c:\\"
* "e:\\"
* "c:/"
* "e:/"
* "\\\\ntfileserver\"
* "page import="""
My first approach is similar to:
<rule id="filesystem-paths-properties">
<when>
<filecontent filename="{*}.{extensions}"
pattern="{filesystem}" />
</when>
<perform>
<hint message="File system properties" effort="1"
severity="mandatory">
<message>
TODO
</message>
</hint>
</perform>
<where param="extensions">
<matches pattern="(java|properties|jsp|jpsf|tag|xml|txt)" />
</where>
<where param="filesystem">
<matches pattern="((c|e):|[\\])" />
</where>
</rule>
However I am detecting cases as "Message: " as a pattern. How could I
create a rule to identify these cases?
Thank you very much in advance
PD: What is the better mail list to send it?
--
Saludos/Best regards
______________________________________________________________________
*Jose Roman Martin Gil *
/MW Senior Architect/ | +34 605 926 271 | roman.martin(a)redhat.com
<mailto:roman.martin@redhat.com>
/**/*Red Hat* Iberia
C/ José Bardasano Baos, 9, Edif. Gorbea 3, planta 3ºD, 28016 Madrid, Spain
______________________________________________________________________
8 years, 8 months
Deps in windup-rules-java-api
by Ondrej Zizka
Hi,
I've noticed that in the pom.xml of $subj, there is:
<dependency>
<groupId>org.jboss.windup.ast</groupId>
<artifactId>windup-java-ast</artifactId>
<classifier>forge-addon</classifier>
<scope>compile</scope>
</dependency>
<dependency>
<groupId>org.jboss.windup.rules.apps</groupId>
<artifactId>windup-rules-base</artifactId>
<classifier>forge-addon</classifier>
<scope>compile</scope>
</dependency>
Shouldn't that be of scope provided, and listed in ../addon/pom.xml ?
Ondra
8 years, 8 months
