[JBoss JIRA] (DROOLS-1288) KieModuleMetaData: Enhance to return a collection of "function" definitons
by Michael Anstis (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1288?page=com.atlassian.jira.plugi... ]
Michael Anstis updated DROOLS-1288:
-----------------------------------
Summary: KieModuleMetaData: Enhance to return a collection of "function" definitons (was: KieModuleMetaData: Enhance to return a collection of "functions" definitons)
> KieModuleMetaData: Enhance to return a collection of "function" definitons
> --------------------------------------------------------------------------
>
> Key: DROOLS-1288
> URL: https://issues.jboss.org/browse/DROOLS-1288
> Project: Drools
> Issue Type: Feature Request
> Affects Versions: 7.0.0.Beta1
> Reporter: Michael Anstis
> Assignee: Edson Tirelli
> Priority: Minor
>
> Functions used in DRL need to be in the same file as the DRL using them; otherwise they need to be imported. Guvnor 5.x built a single {{String}} containing the definition of *all* assets in a project to {{PackageBuilder}} (IIRC) so all functions were always in the same file as any consuming DRL.
> In 6.x we add individual files to {{KieBuilder}} and hence functions are (more than likely) in different files to the DRL using them. Classes used by a specific file need to be imported (if they are not in the same package). Functions will now also need to be imported.
> This request is to enhance {{KieModuleMetaData}} to return a collection of functions so that we can populate these in the {{DataModelOracle}} passed to the client and used to drive the "Import Data Object" screen on editors. We'd need to enhance the DMO and related "import" screens to handle functions. [~nheron] is to raise a GUVNOR JIRA for such enhancement.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (DROOLS-1288) KieModuleMetaData: Enhance to return a collection of "functions" definitons
by Michael Anstis (JIRA)
Michael Anstis created DROOLS-1288:
--------------------------------------
Summary: KieModuleMetaData: Enhance to return a collection of "functions" definitons
Key: DROOLS-1288
URL: https://issues.jboss.org/browse/DROOLS-1288
Project: Drools
Issue Type: Feature Request
Affects Versions: 7.0.0.Beta1
Reporter: Michael Anstis
Assignee: Edson Tirelli
Priority: Minor
Functions used in DRL need to be in the same file as the DRL using them; otherwise they need to be imported. Guvnor 5.x built a single {{String}} containing the definition of *all* assets in a project to {{PackageBuilder}} (IIRC) so all functions were always in the same file as any consuming DRL.
In 6.x we add individual files to {{KieBuilder}} and hence functions are (more than likely) in different files to the DRL using them. Classes used by a specific file need to be imported (if they are not in the same package). Functions will now also need to be imported.
This request is to enhance {{KieModuleMetaData}} to return a collection of functions so that we can populate these in the {{DataModelOracle}} passed to the client and used to drive the "Import Data Object" screen on editors. We'd need to enhance the DMO and related "import" screens to handle functions. [~nheron] is to raise a GUVNOR JIRA for such enhancement.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (WFLY-7112) Allow optional tag virtual-host (and others) inside jboss-app.xml
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-7112?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar updated WFLY-7112:
------------------------------
Component/s: EE
> Allow optional tag virtual-host (and others) inside jboss-app.xml
> -----------------------------------------------------------------
>
> Key: WFLY-7112
> URL: https://issues.jboss.org/browse/WFLY-7112
> Project: WildFly
> Issue Type: Feature Request
> Components: EE
> Affects Versions: 10.1.0.Final
> Reporter: Guido Jäkel
> Assignee: Jason Greene
>
> With undertow, the assignment of a web-application to a virtual host must be set in {{$WAR/META-INF/jboss-web.xml}}. A very adjacent parameter, the context-root, might be defined or overridden here, too.
> In practice, for a concrete deployment generally one have to adapt both parts of the URL, the (virtual) host and the context-root part and may use this file and e.g. apply it with the overlay feature.
> In case of an EAR, its components are declared inside {{$EAR/META-INF/application.xml}}. For an web application, the {{context-root}} is defined here. I found, that this have precedence to a {{$WAR/WEB-INF/jboss-web.xml}}. I don't expect this, but it might be defined by JEE specifications in that way. If not, this feature request should be converted to a bug report concerning a wrong preference order.
> To my knowledge, at the moment this file seems the only way to set the {{virtual-host}} to use. And this looks very inconsistent to me, because you have to use two different "far-out" files to controll this very associated informations.
> The informations in application.xml may be overridden and enriched by {{jboss-appl.xml}} in a similar manner as with {{web.xml}} and {{jboss-web.xml}}. I would expect (and suggest it as a feature) to define the virtual host here in an analogous way as the context root in {{application.xml}} may be overriden here.
> {code}
> <module>
> <web>
> <web-uri>a.war</web-uri>
> <context-root>/foo</context-root>
> <virtual-host>a.domain.tld</virtual-host>
> ...
> </web>
> </module>
> {code}
> This concept should be probably expanded to the complete feature set controlled by the {{jboss-web.xml}}, like undertow-related like {{server-instance}} or others like {{security-domain}}.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (WFLY-7112) Allow optional tag virtual-host (and others) inside jboss-app.xml
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-7112?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar updated WFLY-7112:
------------------------------
Affects Version/s: 10.1.0.Final
> Allow optional tag virtual-host (and others) inside jboss-app.xml
> -----------------------------------------------------------------
>
> Key: WFLY-7112
> URL: https://issues.jboss.org/browse/WFLY-7112
> Project: WildFly
> Issue Type: Feature Request
> Affects Versions: 10.1.0.Final
> Reporter: Guido Jäkel
> Assignee: Jason Greene
>
> With undertow, the assignment of a web-application to a virtual host must be set in {{$WAR/META-INF/jboss-web.xml}}. A very adjacent parameter, the context-root, might be defined or overridden here, too.
> In practice, for a concrete deployment generally one have to adapt both parts of the URL, the (virtual) host and the context-root part and may use this file and e.g. apply it with the overlay feature.
> In case of an EAR, its components are declared inside {{$EAR/META-INF/application.xml}}. For an web application, the {{context-root}} is defined here. I found, that this have precedence to a {{$WAR/WEB-INF/jboss-web.xml}}. I don't expect this, but it might be defined by JEE specifications in that way. If not, this feature request should be converted to a bug report concerning a wrong preference order.
> To my knowledge, at the moment this file seems the only way to set the {{virtual-host}} to use. And this looks very inconsistent to me, because you have to use two different "far-out" files to controll this very associated informations.
> The informations in application.xml may be overridden and enriched by {{jboss-appl.xml}} in a similar manner as with {{web.xml}} and {{jboss-web.xml}}. I would expect (and suggest it as a feature) to define the virtual host here in an analogous way as the context root in {{application.xml}} may be overriden here.
> {code}
> <module>
> <web>
> <web-uri>a.war</web-uri>
> <context-root>/foo</context-root>
> <virtual-host>a.domain.tld</virtual-host>
> ...
> </web>
> </module>
> {code}
> This concept should be probably expanded to the complete feature set controlled by the {{jboss-web.xml}}, like undertow-related like {{server-instance}} or others like {{security-domain}}.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (WFLY-7112) Allow optional tag virtual-host (and others) inside jboss-app.xml
by Guido Jäkel (JIRA)
Guido Jäkel created WFLY-7112:
---------------------------------
Summary: Allow optional tag virtual-host (and others) inside jboss-app.xml
Key: WFLY-7112
URL: https://issues.jboss.org/browse/WFLY-7112
Project: WildFly
Issue Type: Feature Request
Reporter: Guido Jäkel
Assignee: Jason Greene
With undertow, the assignment of a web-application to a virtual host must be set in {{$WAR/META-INF/jboss-web.xml}}. A very adjacent parameter, the context-root, might be defined or overridden here, too.
In practice, for a concrete deployment generally one have to adapt both parts of the URL, the (virtual) host and the context-root part and may use this file and e.g. apply it with the overlay feature.
In case of an EAR, its components are declared inside {{$EAR/META-INF/application.xml}}. For an web application, the {{context-root}} is defined here. I found, that this have precedence to a {{$WAR/WEB-INF/jboss-web.xml}}. I don't expect this, but it might be defined by JEE specifications in that way. If not, this feature request should be converted to a bug report concerning a wrong preference order.
To my knowledge, at the moment this file seems the only way to set the {{virtual-host}} to use. And this looks very inconsistent to me, because you have to use two different "far-out" files to controll this very associated informations.
The informations in application.xml may be overridden and enriched by {{jboss-appl.xml}} in a similar manner as with {{web.xml}} and {{jboss-web.xml}}. I would expect (and suggest it as a feature) to define the virtual host here in an analogous way as the context root in {{application.xml}} may be overriden here.
{code}
<module>
<web>
<web-uri>a.war</web-uri>
<context-root>/foo</context-root>
<virtual-host>a.domain.tld</virtual-host>
...
</web>
</module>
{code}
This concept should be probably expanded to the complete feature set controlled by the {{jboss-web.xml}}, like undertow-related like {{server-instance}} or others like {{security-domain}}.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (WFCORE-1742) Allow registering a custom handler for management interface
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1742?page=com.atlassian.jira.plugi... ]
Tristan Tarrant commented on WFCORE-1742:
-----------------------------------------
To clarify Infinispan's requirements:
- the ability to register an additional admin console in parallel with WildFly's when overlaying the Infinispan Datagrid subsystem on top. This is just serving static content (HTML, JS, CSS, etc) which talks to the /management context. A possible extension would allow WildFly's HAL to link to any additional admin consoles which may be overlayed.
- The ability to register a custom handler to implement a health-check context. (Generically, mapping a specific resource or operation to a shor URL as [~sebastian.laskawiec] mentioned)
> Allow registering a custom handler for management interface
> -----------------------------------------------------------
>
> Key: WFCORE-1742
> URL: https://issues.jboss.org/browse/WFCORE-1742
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Domain Management
> Reporter: Sebastian Łaskawiec
>
> When building [HealthCheck API for Infisnispan|https://github.com/infinispan/infinispan/pull/4499] we noticed there is no way to register a custom endpoint on Management REST interface. Without it, calling the API requires using HTTP POST method (since it includes runtime parameters) and the URL is very long (and not intuitive for our users):
> {noformat}
> curl --digest -L -D - "http://localhost:9990/management/subsystem/datagrid-infinispan/cache-cont..." --header "Content-Type: application/json" -u ispnadmin:ispnadmin
> HTTP/1.1 401 Unauthorized
> Connection: keep-alive
> WWW-Authenticate: Digest realm="ManagementRealm",domain="/management",nonce="AuZzFxz7uC4NMTQ3MDgyNTU1NTQ3OCfIJBHXVpPHPBdzGUy7Qts=",opaque="00000000000000000000000000000000",algorithm=MD5,qop="auth"
> Content-Length: 77
> Content-Type: text/html
> Date: Wed, 10 Aug 2016 10:39:15 GMT
> HTTP/1.1 200 OK
> Connection: keep-alive
> Authentication-Info: nextnonce="AuZzFxz7uC4NMTQ3MDgyNTU1NTQ3OCfIJBHXVpPHPBdzGUy7Qts=",qop="auth",rspauth="b518c3170e627bd732055c382ce5d970",cnonce="NGViOWM0NDY5OGJmNjY0MjcyOWE4NDkyZDU3YzNhYjY=",nc=00000001
> Content-Type: application/json; charset=utf-8
> Content-Length: 1927
> Date: Wed, 10 Aug 2016 10:39:15 GMT
> {
> "cache-health" : "GREEN",
> "cluster-health" : ["test"],
> "cluster-name" : "clustered",
> "free-memory" : 96778,
> "log-tail" : [
> "2016-08-10 11:54:14,706 INFO [org.infinispan.server.endpoint] (MSC service thread 1-5) DGENDPT10001: HotRodServer listening on 127.0.0.1:11222",
> "2016-08-10 11:54:14,706 INFO [org.infinispan.server.endpoint] (MSC service thread 1-1) DGENDPT10001: MemcachedServer listening on 127.0.0.1:11211",
> "2016-08-10 11:54:14,785 INFO [org.jboss.as.clustering.infinispan] (MSC service thread 1-6) DGISPN0001: Started ___protobuf_metadata cache from clustered container",
> "2016-08-10 11:54:14,800 INFO [org.jboss.as.clustering.infinispan] (MSC service thread 1-6) DGISPN0001: Started ___script_cache cache from clustered container",
> "2016-08-10 11:54:15,159 INFO [org.jboss.as.clustering.infinispan] (MSC service thread 1-5) DGISPN0001: Started ___hotRodTopologyCache cache from clustered container",
> "2016-08-10 11:54:15,210 INFO [org.infinispan.rest.NettyRestServer] (MSC service thread 1-6) ISPN012003: REST server starting, listening on 127.0.0.1:8080",
> "2016-08-10 11:54:15,210 INFO [org.infinispan.server.endpoint] (MSC service thread 1-6) DGENDPT10002: REST mapped to /rest",
> "2016-08-10 11:54:15,306 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management",
> "2016-08-10 11:54:15,307 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990",
> "2016-08-10 11:54:15,307 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: Infinispan Server 9.0.0-SNAPSHOT (WildFly Core 2.2.0.CR9) started in 8681ms - Started 196 of 237 services (121 services are lazy, passive or on-demand)"
> ],
> "number-of-cpus" : 8,
> "number-of-nodes" : 1,
> "total-memory" : 235520
> }%
> {noformat}
> It would be very convenient to allow exposing such endpoints with optional authorization and using custom URLs (e.g. something like http://localhost:9990/health).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (WFLY-7111) Distributable web applications cause Infinispan exceptions when Elytron is used
by Josef Cacek (JIRA)
Josef Cacek created WFLY-7111:
---------------------------------
Summary: Distributable web applications cause Infinispan exceptions when Elytron is used
Key: WFLY-7111
URL: https://issues.jboss.org/browse/WFLY-7111
Project: WildFly
Issue Type: Bug
Components: Security
Reporter: Josef Cacek
Assignee: Darran Lofthouse
Priority: Blocker
When a distributable secured web application mapped to Elytron domain is deployed to EAP and accessed. It throws intermittently {{org.infinispan.util.concurrent.TimeoutException}}
*Expected behavior:*
Distributable applications should be accessible without exceptions when Elytron is used.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (DROOLS-1286) GDT editor: unable to specify Literal value or Template key for domain objects as Condition BRL fragment
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1286?page=com.atlassian.jira.plugi... ]
Mario Fusco reassigned DROOLS-1286:
-----------------------------------
Assignee: Michael Anstis (was: Mario Fusco)
> GDT editor: unable to specify Literal value or Template key for domain objects as Condition BRL fragment
> ---------------------------------------------------------------------------------------------------------
>
> Key: DROOLS-1286
> URL: https://issues.jboss.org/browse/DROOLS-1286
> Project: Drools
> Issue Type: Bug
> Components: decision tables
> Affects Versions: 6.4.0.Final
> Reporter: Hiroko Miura
> Assignee: Michael Anstis
> Labels: support
> Attachments: Screen_Shot.png
>
>
> Guided Decision Table: When adding a Condition BRL fragment it is not possible to enter a template key or value for an attribute on a domain object.
> In the attached screen shot, when clicking pencil icon, nothing appear.
> This is confirmed by both FireFox anc Chrome.
> At that time, the following error is shown in browser's console.
> [Chrome]
> 12:44:40 SEVERE [LogConfiguration] Exception caught: (TypeError) : Cannot read property 'indexOf' of null
>
> [FireFox]
> 00:10:46 SEVERE [LogConfiguration] Exception caught: (TypeError) : b.indexOf is null
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months