[JBoss JIRA] (WFCORE-1487) Include indexed properties in the suggestion list if no completer exists
by Bartosz Spyrko-Śmietanko (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1487?page=com.atlassian.jira.plugi... ]
Bartosz Spyrko-Śmietanko reopened WFCORE-1487:
----------------------------------------------
Reopening after the fix was reverted in WFCORE-1682
> Include indexed properties in the suggestion list if no completer exists
> ------------------------------------------------------------------------
>
> Key: WFCORE-1487
> URL: https://issues.jboss.org/browse/WFCORE-1487
> Project: WildFly Core
> Issue Type: Enhancement
> Components: CLI
> Affects Versions: 2.1.0.Final
> Reporter: Bartosz Spyrko-Śmietanko
> Assignee: Bartosz Spyrko-Śmietanko
> Fix For: 2.2.0.CR1, 3.0.0.Alpha1
>
>
> Command parameters that can be specified by either an index and a name, but have no value completer are not included in the tab completion list.
> For example patch rollback tab completion does not show --patch-id
> {noformat}
> [disconnected /] patch rollback --
> --override-all --override-modules --override= --preserve= --reset-configuration= --rollback-to
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (WFCORE-1713) Migrate ModelControllerMBeanTestCase from wildfly test suite to core test suite
by ehsavoie Hugonnet (JIRA)
ehsavoie Hugonnet created WFCORE-1713:
-----------------------------------------
Summary: Migrate ModelControllerMBeanTestCase from wildfly test suite to core test suite
Key: WFCORE-1713
URL: https://issues.jboss.org/browse/WFCORE-1713
Project: WildFly Core
Issue Type: Enhancement
Components: Test Suite
Affects Versions: 3.0.0.Alpha4
Reporter: ehsavoie Hugonnet
Assignee: Tomaz Cerar
Priority: Minor
Brian Stansberry: please copy ModelControllerMBeanTestCase from full into core
it uses a sar deployment but that can be converted to a ServiceActivator deployment as core doesn't support .sar
then all the methods in the copy of the test in full except testAllMBeanInfos() can be removed
all this, besides getting the test in a better spot, will remove the need to simultaneously upgrade core and fix the test in full
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (WFCORE-1713) Migrate ModelControllerMBeanTestCase from wildfly test suite to core test suite
by ehsavoie Hugonnet (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1713?page=com.atlassian.jira.plugi... ]
ehsavoie Hugonnet reassigned WFCORE-1713:
-----------------------------------------
Assignee: ehsavoie Hugonnet (was: Tomaz Cerar)
> Migrate ModelControllerMBeanTestCase from wildfly test suite to core test suite
> -------------------------------------------------------------------------------
>
> Key: WFCORE-1713
> URL: https://issues.jboss.org/browse/WFCORE-1713
> Project: WildFly Core
> Issue Type: Enhancement
> Components: Test Suite
> Affects Versions: 3.0.0.Alpha4
> Reporter: ehsavoie Hugonnet
> Assignee: ehsavoie Hugonnet
> Priority: Minor
>
> Brian Stansberry: please copy ModelControllerMBeanTestCase from full into core
> it uses a sar deployment but that can be converted to a ServiceActivator deployment as core doesn't support .sar
> then all the methods in the copy of the test in full except testAllMBeanInfos() can be removed
> all this, besides getting the test in a better spot, will remove the need to simultaneously upgrade core and fix the test in full
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (WFLY-6882) A client is not able to invoke EJB's deployed as "HASingleton deployment"
by Wolf-Dieter Fink (JIRA)
[ https://issues.jboss.org/browse/WFLY-6882?page=com.atlassian.jira.plugin.... ]
Wolf-Dieter Fink commented on WFLY-6882:
----------------------------------------
[~pferraro] If I deploy an application as a HA Singleton the use-case is that the deployed SLSB/SFSB/Singleton or MDB is only handled by one server in a cluster.
So if I have a cluster of let say 4 nodes one will start the HASingleton. Any Client of this cluster should be able to invoke this application no matter whether this server is in the initial host list or provided by the ejb-client cluster-view update.
This is similar if I deploy a special application only on one node in this cluster.
For MDB it should be no problem as the queue is clustered and anyone in the cluster can send to it but only this MDB(app) is consuming it.
This is a common use-case and should be possible.
> A client is not able to invoke EJB's deployed as "HASingleton deployment"
> -------------------------------------------------------------------------
>
> Key: WFLY-6882
> URL: https://issues.jboss.org/browse/WFLY-6882
> Project: WildFly
> Issue Type: Bug
> Components: Clustering, EJB
> Affects Versions: 10.0.0.Final, 11.0.0.Alpha1
> Reporter: Wolf-Dieter Fink
> Assignee: Enrique González Martínez
>
> Given that an application contains a SLSB and is clustered, any EJB client will be updated to have a view off all cluster members and is able to use and failover to any node in the cluster no matter whether it is in the initial list of servers.
> Now if the application is marked as "singleton-deployment" via jboss-all.xml and deployed to all servers only one server in a cluster will pick it and make it active.
> Now the expectation is that a client is routed to that server no matter whether this special server is included in the clients initial connection list.
> The interesting thing is that the client.log show that both servers are connected it the application is NOT marked as singleton
> But only the initial server is connected if the app is marked as singleton!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (WFLY-6948) Upgrade HAL to 2.9.0.Alpha1
by Harald Pehl (JIRA)
Harald Pehl created WFLY-6948:
---------------------------------
Summary: Upgrade HAL to 2.9.0.Alpha1
Key: WFLY-6948
URL: https://issues.jboss.org/browse/WFLY-6948
Project: WildFly
Issue Type: Component Upgrade
Components: Web Console
Reporter: Harald Pehl
Assignee: Harald Pehl
Priority: Blocker
Fix For: 10.1.0.Final, 11.0.0.Alpha1
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months