December 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-3450) CLI - avoid required attributes to be hard to see when using tab completion

by Rostislav Svoboda (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3450?page=com.atlassian.jira.plugi... ] Rostislav Svoboda updated WFCORE-3450: -------------------------------------- Description: This is follow up for WFCORE-2283 which marked required attributes by "*" when using tab completion. Still if there are many attributes, it's hard to see all required attributes, for example in: {code} [standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/cluster-connection=my-cluster:add( ! check-period connector-name* max-retry-interval notification-interval retry-interval-multiplier allow-direct-connections-only cluster-connection-address* discovery-group* message-load-balancing-type producer-window-size static-connectors* call-failover-timeout confirmation-window-size initial-connect-attempts min-large-message-size reconnect-attempts use-duplicate-detection call-timeout connection-ttl max-hops notification-attempts retry-interval {code} it's not clear at the first look how many required attributes there are. Suggestion is to group required attributes together and then provide list of other attributes, for example on the next line. Another options might be considered as well. For example to show required attributes when double pressing <tab>. Discussed on https://developer.jboss.org/wiki/CLI-BetterCompletionForArguments?et=watc... was: This is follow up for WFCORE-2283 which marked required attributes by "*" when using tab completion. Still if there are many attributes, it's hard to see all required attributes, for example in: {code} [standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/cluster-connection=my-cluster:add( ! check-period connector-name* max-retry-interval notification-interval retry-interval-multiplier allow-direct-connections-only cluster-connection-address* discovery-group* message-load-balancing-type producer-window-size static-connectors* call-failover-timeout confirmation-window-size initial-connect-attempts min-large-message-size reconnect-attempts use-duplicate-detection call-timeout connection-ttl max-hops notification-attempts retry-interval {code} it's not clear at the first look how many required attributes there are. Suggestion is to group required attributes together and then provide list of other attributes, for example on the next line. Another options might be considered as well. For example to show required attributes when double pressing <tab>. > CLI - avoid required attributes to be hard to see when using tab completion > ---------------------------------------------------------------------------- > > Key: WFCORE-3450 > URL: https://issues.jboss.org/browse/WFCORE-3450 > Project: WildFly Core > Issue Type: Feature Request > Components: CLI > Reporter: Miroslav Novak > > This is follow up for WFCORE-2283 which marked required attributes by "*" when using tab completion. Still if there are many attributes, it's hard to see all required attributes, for example in: > {code} > [standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/cluster-connection=my-cluster:add( > ! check-period connector-name* max-retry-interval notification-interval retry-interval-multiplier > allow-direct-connections-only cluster-connection-address* discovery-group* message-load-balancing-type producer-window-size static-connectors* > call-failover-timeout confirmation-window-size initial-connect-attempts min-large-message-size reconnect-attempts use-duplicate-detection > call-timeout connection-ttl max-hops notification-attempts retry-interval > {code} > it's not clear at the first look how many required attributes there are. > Suggestion is to group required attributes together and then provide list of other attributes, for example on the next line. Another options might be considered as well. For example to show required attributes when double pressing <tab>. > Discussed on https://developer.jboss.org/wiki/CLI-BetterCompletionForArguments?et=watc... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3450) CLI - avoid required attributes to be hard to see when using tab completion

by Ingo Weiss (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3450?page=com.atlassian.jira.plugi... ] Ingo Weiss commented on WFCORE-3450: ------------------------------------ As mentioned, I think colours + '*' would be best suited. If the terminal doesn't support colours, then the '*' should suffice. Maybe we can add a note mentioning that '*' attributes are required ones? > CLI - avoid required attributes to be hard to see when using tab completion > ---------------------------------------------------------------------------- > > Key: WFCORE-3450 > URL: https://issues.jboss.org/browse/WFCORE-3450 > Project: WildFly Core > Issue Type: Feature Request > Components: CLI > Reporter: Miroslav Novak > > This is follow up for WFCORE-2283 which marked required attributes by "*" when using tab completion. Still if there are many attributes, it's hard to see all required attributes, for example in: > {code} > [standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/cluster-connection=my-cluster:add( > ! check-period connector-name* max-retry-interval notification-interval retry-interval-multiplier > allow-direct-connections-only cluster-connection-address* discovery-group* message-load-balancing-type producer-window-size static-connectors* > call-failover-timeout confirmation-window-size initial-connect-attempts min-large-message-size reconnect-attempts use-duplicate-detection > call-timeout connection-ttl max-hops notification-attempts retry-interval > {code} > it's not clear at the first look how many required attributes there are. > Suggestion is to group required attributes together and then provide list of other attributes, for example on the next line. Another options might be considered as well. For example to show required attributes when double pressing <tab>. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2122) Error when drl file is opened with in project with runtime classes

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2122?page=com.atlassian.jira.plugi... ] Mario Fusco commented on DROOLS-2122: ------------------------------------- Fixed by https://github.com/kiegroup/droolsjbpm-knowledge/commit/aedd33f85b4fa73bd... and https://github.com/kiegroup/droolsjbpm-tools/commit/b8dc98591075b7f050d96... > Error when drl file is opened with in project with runtime classes > ------------------------------------------------------------------- > > Key: DROOLS-2122 > URL: https://issues.jboss.org/browse/DROOLS-2122 > Project: Drools > Issue Type: Bug > Components: eclipse plugin > Affects Versions: 7.3.0.Final > Environment: DevstudioIS 11.1.0.Beta1 > Brms 6.4.6.GA > Reporter: Tomas David > Assignee: Mario Fusco > Priority: Blocker > Fix For: 7.5.0.Final > > Attachments: Screenshot from 2017-11-09 09-55-05.png, devstudiolog.log > > > If new drools project is created with build using Java and Drools classes, error is displayed after drl file is opened. > This blocks also other functions like add a breakpoint or show content assist menu. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2122) Error when drl file is opened with in project with runtime classes

by Matteo Mortari (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2122?page=com.atlassian.jira.plugi... ] Matteo Mortari commented on DROOLS-2122: ---------------------------------------- Also requires 2 commits, on droolsjbpm-knowledge and a new one on droolsjbpm-tools: https://github.com/kiegroup/droolsjbpm-knowledge/commit/aedd33f85b4fa73bd... https://github.com/kiegroup/droolsjbpm-tools/commit/b8dc98591075b7f050d96... > Error when drl file is opened with in project with runtime classes > ------------------------------------------------------------------- > > Key: DROOLS-2122 > URL: https://issues.jboss.org/browse/DROOLS-2122 > Project: Drools > Issue Type: Bug > Components: eclipse plugin > Affects Versions: 7.3.0.Final > Environment: DevstudioIS 11.1.0.Beta1 > Brms 6.4.6.GA > Reporter: Tomas David > Assignee: Mario Fusco > Priority: Blocker > Fix For: 7.5.0.Final > > Attachments: Screenshot from 2017-11-09 09-55-05.png, devstudiolog.log > > > If new drools project is created with build using Java and Drools classes, error is displayed after drl file is opened. > This blocks also other functions like add a breakpoint or show content assist menu. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3450) CLI - avoid required attributes to be hard to see when using tab completion

by Miroslav Novak (JIRA)

Miroslav Novak created WFCORE-3450: -------------------------------------- Summary: CLI - avoid required attributes to be hard to see when using tab completion Key: WFCORE-3450 URL: https://issues.jboss.org/browse/WFCORE-3450 Project: WildFly Core Issue Type: Feature Request Components: CLI Reporter: Miroslav Novak This is follow up for WFCORE-2283 which marked required attributes by "*" when using tab completion. Still if there are many attributes, it's hard to see all required attributes, for example in: {code} [standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/cluster-connection=my-cluster:add( ! check-period connector-name* max-retry-interval notification-interval retry-interval-multiplier allow-direct-connections-only cluster-connection-address* discovery-group* message-load-balancing-type producer-window-size static-connectors* call-failover-timeout confirmation-window-size initial-connect-attempts min-large-message-size reconnect-attempts use-duplicate-detection call-timeout connection-ttl max-hops notification-attempts retry-interval {code} it's not clear at the first look how many required attributes there are. Suggestion is to group required attributes together and then provide list of other attributes, for example on the next line. Another options might be considered as well. For example to show required attributes when double pressing <tab>. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2163) [DMN Editor] Context table doesn't show entry type label if table is scrolled

by Jozef Marko (JIRA)

Jozef Marko created DROOLS-2163: ----------------------------------- Summary: [DMN Editor] Context table doesn't show entry type label if table is scrolled Key: DROOLS-2163 URL: https://issues.jboss.org/browse/DROOLS-2163 Project: Drools Issue Type: Bug Components: DMN Editor Affects Versions: 7.5.0.Final Reporter: Jozef Marko Assignee: Michael Anstis Context table offers 5 types of entries while each entry has label of its own type (Literal Expression, Function Relation etc.) However this label is not shown if the user scroll the table. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-1226) undeploying disabled deployment stops service for same runtime-name in DeploymentUndeployHandler

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1226?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on WFCORE-1226: ------------------------------------------------- Abhijit humbe <abhumbe(a)redhat.com> changed the Status of [bug 1280262|https://bugzilla.redhat.com/show_bug.cgi?id=1280262] from CLOSED to NEW > undeploying disabled deployment stops service for same runtime-name in DeploymentUndeployHandler > ------------------------------------------------------------------------------------------------- > > Key: WFCORE-1226 > URL: https://issues.jboss.org/browse/WFCORE-1226 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 2.0.4.Final > Reporter: Chao Wang > Assignee: Chao Wang > Fix For: 2.0.6.Final > > Attachments: WFCORE-1226-wildflytest.patch, WFCORE-1226.patch > > > {noformat} > 1. Start EAP 6.4.4 in domain mode and deploy application using following CLI command: > ~~ > [domain@localhost:9999 /] deploy /Applications/WebApp-1.war --server-groups=main-server-group --name=WebApp-1.war --runtime-name=WebApp-1.war > ~~~ > 2. Deploy next version of application in "disabled" state with same "runtime-name" > ~~~ > [domain@localhost:9999 /] deploy /Applications/WebApp-2.war --disabled --name=WebApp-2.war --runtime-name=WebApp-1.war > ~~~ > 3. Now use replace-deployment command to access latest version of application: > ~~~ > [domain@localhost:9999 /] /server-group=main-server-group:replace-deployment(name=WebApp-2.war,to-replace=WebApp-1.war) > ~~~ > its working fine,laest version of application is accessable. > 4. Now try to undeploy old version of application > ~~~ > /server-group=main-server-group/deployment=WebApp-1.war:undeploy() > ~~~ > After undploying older version, we are not able to access(404) latest version of application(WebApp-2.war) as well.To access it we have to redeploy it. > Same steps are working fine in Standalone mode. > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-9594) url rewriting doesnt work in wildfly 8.2.1

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-9594?page=com.atlassian.jira.plugin.... ] Stuart Douglas resolved WFLY-9594. ---------------------------------- Resolution: Rejected > url rewriting doesnt work in wildfly 8.2.1 > ------------------------------------------ > > Key: WFLY-9594 > URL: https://issues.jboss.org/browse/WFLY-9594 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 8.2.1.Final > Reporter: SATISH POKALWAR > Assignee: Stuart Douglas > > I have an application running on wildfly 8.2.1 which is upgraded from jboss 6.4. for URL rewriting in jboss 6.4 , we have virtual server section in standlone-full.xml however to do the same on wildfly 8.2.1 its been suggested to write the rule in undertow-handlers.conf and put the same in WEB-INF directory ,however that is not working.Basically i want to rewrite http://ip_address/a and http://ip_address/b to http://ip_address/c , to do the same i have written below rule in undertow-handlers.conf it is not working, regex['^/a/$'] -> rewrite['/c/$1']. Can anyone tell if am doing anything wrong , similiar rule used to work in JBOSS 6.4 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2132) [DMN Editor] Boxed Expressions: FunctionDefinition editor

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2132?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2132: -------------------------------- QE Status: ON_QA (was: NEW) > [DMN Editor] Boxed Expressions: FunctionDefinition editor > --------------------------------------------------------- > > Key: DROOLS-2132 > URL: https://issues.jboss.org/browse/DROOLS-2132 > Project: Drools > Issue Type: Feature Request > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-9594) url rewriting doesnt work in wildfly 8.2.1

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-9594?page=com.atlassian.jira.plugin.... ] Stuart Douglas commented on WFLY-9594: -------------------------------------- Please ask for help on the forums, JIRA is for bug reports. That said you can do this in standalone.xml using an expression-filter in the filters section. You probably want something like: path-prefix(/a/) -> rewrite(/c/${remaining}) If you want to use regex: regex('^/a/(.*)') -> rewrite('/c/${1}') > url rewriting doesnt work in wildfly 8.2.1 > ------------------------------------------ > > Key: WFLY-9594 > URL: https://issues.jboss.org/browse/WFLY-9594 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 8.2.1.Final > Reporter: SATISH POKALWAR > Assignee: Stuart Douglas > > I have an application running on wildfly 8.2.1 which is upgraded from jboss 6.4. for URL rewriting in jboss 6.4 , we have virtual server section in standlone-full.xml however to do the same on wildfly 8.2.1 its been suggested to write the rule in undertow-handlers.conf and put the same in WEB-INF directory ,however that is not working.Basically i want to rewrite http://ip_address/a and http://ip_address/b to http://ip_address/c , to do the same i have written below rule in undertow-handlers.conf it is not working, regex['^/a/$'] -> rewrite['/c/$1']. Can anyone tell if am doing anything wrong , similiar rule used to work in JBOSS 6.4 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2017