[JBoss JIRA] (DROOLS-4812) DMN FEEL warn if en-dash is present as a character in expression
by Toshiya Kobayashi (Jira)
[ https://issues.redhat.com/browse/DROOLS-4812?page=com.atlassian.jira.plug... ]
Toshiya Kobayashi updated DROOLS-4812:
--------------------------------------
Labels: (was: good-first-issue)
> DMN FEEL warn if en-dash is present as a character in expression
> ----------------------------------------------------------------
>
> Key: DROOLS-4812
> URL: https://issues.redhat.com/browse/DROOLS-4812
> Project: Drools
> Issue Type: Enhancement
> Components: dmn engine
> Reporter: Matteo Mortari
> Assignee: Matteo Mortari
> Priority: Major
>
> This is taken from the DMN spec :
> {code:java}
> (amount *rate/12) / (1 – (1 + rate/12)**-term)
> {code}
> however this would fail to parse correctly as the first subtraction sign is an "en-dash" (0x2013) and not a minus/hyphen sign (0x2D)
> {code:java}
> (amount *rate/12) / (1 – (1 + rate/12)**-term)
> ^
> (amount *rate/12) / (1 - (1 + rate/12)**-term)
> {code}
> while an "em-dash" is much more noticeable, this "en-dash" can be confused more easily, especially depending on the font used:
> {code:java}
> – en-dash
> - minus, or hyphen (standard)
> — em-dash (much more noticeable in the difference)
> {code}
> It is suggested for the parser/compile to emit a warning if the en-dash is used in an expression --or potentially if it's the last character in a viable alternative.
> A good way to check for the behavior is to use the wrong expression above to exhibit the behavior when the en-dash is misplaced for a minus sign for a subtraction operation.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (WFLY-12856) EJB management resource component-class-name showing component name
by Cheng Fang (Jira)
[ https://issues.redhat.com/browse/WFLY-12856?page=com.atlassian.jira.plugi... ]
Cheng Fang updated WFLY-12856:
------------------------------
Description:
Attribute {{component-class-name}} should show the ejb bean class name, instead of the bean name. In additionm, showing the component name doesn't provide extra information since the identifier in the command already contains the component name.
{code}
/deployment=singleton-hello.jar/subsystem=ejb3/singleton-bean=SingletonHello:read-resource(include-runtime, recursive=true)
{
"outcome" => "success",
"result" => {
"component-class-name" => "SingletonHello",
"declared-roles" => [],
"execution-time" => 0L,
"invocations" => 0L,
"methods" => {},
"peak-concurrent-invocations" => 0L,
"run-as-role" => undefined,
"security-domain" => "other",
"timers" => [],
"wait-time" => 0L,
"service" => undefined
}
}
{code}
was:
Attribute {{component-class-name}} should show the ejb bean class name, instead of the bean name.
{code}
/deployment=singleton-hello.jar/subsystem=ejb3/singleton-bean=SingletonHello:read-resource(include-runtime, recursive=true)
{
"outcome" => "success",
"result" => {
"component-class-name" => "SingletonHello",
"declared-roles" => [],
"execution-time" => 0L,
"invocations" => 0L,
"methods" => {},
"peak-concurrent-invocations" => 0L,
"run-as-role" => undefined,
"security-domain" => "other",
"timers" => [],
"wait-time" => 0L,
"service" => undefined
}
}
{code}
> EJB management resource component-class-name showing component name
> -------------------------------------------------------------------
>
> Key: WFLY-12856
> URL: https://issues.redhat.com/browse/WFLY-12856
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Reporter: Cheng Fang
> Assignee: Cheng Fang
> Priority: Major
>
> Attribute {{component-class-name}} should show the ejb bean class name, instead of the bean name. In additionm, showing the component name doesn't provide extra information since the identifier in the command already contains the component name.
> {code}
> /deployment=singleton-hello.jar/subsystem=ejb3/singleton-bean=SingletonHello:read-resource(include-runtime, recursive=true)
> {
> "outcome" => "success",
> "result" => {
> "component-class-name" => "SingletonHello",
> "declared-roles" => [],
> "execution-time" => 0L,
> "invocations" => 0L,
> "methods" => {},
> "peak-concurrent-invocations" => 0L,
> "run-as-role" => undefined,
> "security-domain" => "other",
> "timers" => [],
> "wait-time" => 0L,
> "service" => undefined
> }
> }
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (WFLY-12856) EJB management resource component-class-name showing component name
by Cheng Fang (Jira)
[ https://issues.redhat.com/browse/WFLY-12856?page=com.atlassian.jira.plugi... ]
Cheng Fang updated WFLY-12856:
------------------------------
Description:
Attribute {{component-class-name}} should show the ejb bean class name, instead of the bean name.
{code}
/deployment=singleton-hello.jar/subsystem=ejb3/singleton-bean=SingletonHello:read-resource(include-runtime, recursive=true)
{
"outcome" => "success",
"result" => {
"component-class-name" => "SingletonHello",
"declared-roles" => [],
"execution-time" => 0L,
"invocations" => 0L,
"methods" => {},
"peak-concurrent-invocations" => 0L,
"run-as-role" => undefined,
"security-domain" => "other",
"timers" => [],
"wait-time" => 0L,
"service" => undefined
}
}
{code}
was:
{code}
/deployment=singleton-hello.jar/subsystem=ejb3/singleton-bean=SingletonHello:read-resource(include-runtime, recursive=true)
{
"outcome" => "success",
"result" => {
"component-class-name" => "SingletonHello",
"declared-roles" => [],
"execution-time" => 0L,
"invocations" => 0L,
"methods" => {},
"peak-concurrent-invocations" => 0L,
"run-as-role" => undefined,
"security-domain" => "other",
"timers" => [],
"wait-time" => 0L,
"service" => undefined
}
}
{code}
> EJB management resource component-class-name showing component name
> -------------------------------------------------------------------
>
> Key: WFLY-12856
> URL: https://issues.redhat.com/browse/WFLY-12856
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Reporter: Cheng Fang
> Assignee: Cheng Fang
> Priority: Major
>
> Attribute {{component-class-name}} should show the ejb bean class name, instead of the bean name.
> {code}
> /deployment=singleton-hello.jar/subsystem=ejb3/singleton-bean=SingletonHello:read-resource(include-runtime, recursive=true)
> {
> "outcome" => "success",
> "result" => {
> "component-class-name" => "SingletonHello",
> "declared-roles" => [],
> "execution-time" => 0L,
> "invocations" => 0L,
> "methods" => {},
> "peak-concurrent-invocations" => 0L,
> "run-as-role" => undefined,
> "security-domain" => "other",
> "timers" => [],
> "wait-time" => 0L,
> "service" => undefined
> }
> }
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (WFLY-12856) EJB management resource component-class-name showing component name
by Cheng Fang (Jira)
Cheng Fang created WFLY-12856:
---------------------------------
Summary: EJB management resource component-class-name showing component name
Key: WFLY-12856
URL: https://issues.redhat.com/browse/WFLY-12856
Project: WildFly
Issue Type: Bug
Components: EJB
Reporter: Cheng Fang
Assignee: Cheng Fang
{code}
/deployment=singleton-hello.jar/subsystem=ejb3/singleton-bean=SingletonHello:read-resource(include-runtime, recursive=true)
{
"outcome" => "success",
"result" => {
"component-class-name" => "SingletonHello",
"declared-roles" => [],
"execution-time" => 0L,
"invocations" => 0L,
"methods" => {},
"peak-concurrent-invocations" => 0L,
"run-as-role" => undefined,
"security-domain" => "other",
"timers" => [],
"wait-time" => 0L,
"service" => undefined
}
}
{code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (WFLY-5525) ANT task and libraries to precompile jsp files
by Ricardo Martin Camarero (Jira)
[ https://issues.redhat.com/browse/WFLY-5525?page=com.atlassian.jira.plugin... ]
Ricardo Martin Camarero commented on WFLY-5525:
-----------------------------------------------
I've been working in a replacement for the JspC tomcat utility that uses directly the wildfly libraries (jastow and so on and so forth). It's a separate project that only provides the command line tool (no ANT task) for pre-compiling. See [the project here|https://github.com/rmartinc/jspc].
I have also done [a blog entry to explain how this works|https://blogs.nologin.es/rickyepoderi/index.php?/archives/179-Presenting-JspC-for-Wildfly.html].
Regards!
> ANT task and libraries to precompile jsp files
> ----------------------------------------------
>
> Key: WFLY-5525
> URL: https://issues.redhat.com/browse/WFLY-5525
> Project: WildFly
> Issue Type: Task
> Components: Web (Undertow)
> Reporter: Pradeep Pantula
> Priority: Optional
> Fix For: Awaiting Volunteers
>
>
> We are migration our applications from Jboss7.1 to WildFly8.1 . For all purposes we pre-compile jsp files and deploy applications for performance. Can anyone provide me ant tasks and related libraries to pre-compile jsp files and deploy applications (.ear files) in WildFly8.1
> I tried with ecj and jastow libraries which are provided under io.undertow.jsp module. But that did not worked for me.
> Can anyone let me know or give a way of how to achieve this.
> Thanks in Advance,
> Pradeep. P
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (WFCORE-3948) Potential race condition on deployment of EAR when Class-Path manifest entry is in use
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFCORE-3948?page=com.atlassian.jira.plug... ]
Brian Stansberry reopened WFCORE-3948:
--------------------------------------
I'll revert the CopyOnWriteArrayList and use a synchronized approach. The one DUP that needs to iterate while concurrent writes might be happening will synchronize on the list.
> Potential race condition on deployment of EAR when Class-Path manifest entry is in use
> --------------------------------------------------------------------------------------
>
> Key: WFCORE-3948
> URL: https://issues.redhat.com/browse/WFCORE-3948
> Project: WildFly Core
> Issue Type: Bug
> Components: Server
> Reporter: Stuart Douglas
> Assignee: Brian Stansberry
> Priority: Major
> Fix For: 11.0.0.Beta4
>
>
> Attachments#ADDITIONAL_MODULES is attached to the top level DU, but modified by sub deployments in ManifestClassPathProcessor#createAdditionalModule without any sort of synchronisation. This can result in ConcurrentModificationException when the list is read/written to by other sub deployments at the same time.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months