September 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFWIP-198) Operator long-term strategy

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFWIP-198?page=com.atlassian.jira.plugin.... ] Jeff Mesnil commented on WFWIP-198: ----------------------------------- [~mchoma] yes, tx recovery has been merged in wildfly-operator upstream but I don't see how that is related to your option (1). The code provides new configuration related to the feature and nothing else. > Operator long-term strategy > --------------------------- > > Key: WFWIP-198 > URL: https://issues.jboss.org/browse/WFWIP-198 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Choma > Assignee: Jeff Mesnil > Priority: Blocker > > Facts: > # Operator creates and manges internaly several kubernetes objects; StatefulSet, Pod, Service, Routes. By rough estimation these kubernetes objects expose approximately 50 options[2]. Operator now expose approximately 10 options [1]. > # EAP7-1192 is currently designed in way operator is integral part of solution. You can not turn off operator to EAP7-1192 properly work. > # User cant touch internal Kubernetes objects. Operator manages them and can overwrite changes anytime. > So given these facts question is what is long-term strategy with Operator? > # Operator will provide all options of internal objects. Everything I am able to configure directly with Kubernetes objects I will be able to configure with Operator > # Operator will expose just most useful options. If user wants to make something special he has to "turn off" operator and to be on his own. (Loosing transaction support provided by EAP7-1192) > # Operator will expose just most useful options. If user wants to make something special he can and Operator won't overwritten his changes. (I dont know if it is feasible?) > [1] https://github.com/wildfly/wildfly-operator/blob/master/doc/apis.adoc#wil... > [2] > https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.15/#pods... > https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.15/#stat... > https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.15/#serv... > https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.15/#ingr... -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4670) Upgrade JBoss MSC to 1.4.12.Final

by Katarina Hermanova (Jira)

Katarina Hermanova created WFCORE-4670: ------------------------------------------ Summary: Upgrade JBoss MSC to 1.4.12.Final Key: WFCORE-4670 URL: https://issues.jboss.org/browse/WFCORE-4670 Project: WildFly Core Issue Type: Component Upgrade Components: Server Reporter: Katarina Hermanova Assignee: Richard Opalka Fix For: 10.0.0.Beta9 -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4670) Upgrade JBoss MSC to 1.4.12.Final

by Katarina Hermanova (Jira)

[ https://issues.jboss.org/browse/WFCORE-4670?page=com.atlassian.jira.plugi... ] Katarina Hermanova updated WFCORE-4670: --------------------------------------- Priority: Major (was: Blocker) > Upgrade JBoss MSC to 1.4.12.Final > --------------------------------- > > Key: WFCORE-4670 > URL: https://issues.jboss.org/browse/WFCORE-4670 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Server > Reporter: Katarina Hermanova > Assignee: Richard Opalka > Priority: Major > Fix For: 10.0.0.Beta9 > > -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-198) Operator long-term strategy

by Martin Choma (Jira)

[ https://issues.jboss.org/browse/WFWIP-198?page=com.atlassian.jira.plugin.... ] Martin Choma commented on WFWIP-198: ------------------------------------ [~jmesnil] I see you have merged EAP7-1192 work into operator codebase. Do I understand correctly you have in fact chosen option number 1. {quote} 1. Operator will provide all options of internal objects. Everything I am able to configure directly with Kubernetes objects I will be able to configure with Operator {quote} Please confirm. I think this have consequence, that we should revisit operator configuration model. Now we are trying to map hierarchical kubernetes model (sometimes with 1:N relations) into flat one level operator model. > Operator long-term strategy > --------------------------- > > Key: WFWIP-198 > URL: https://issues.jboss.org/browse/WFWIP-198 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Choma > Assignee: Jeff Mesnil > Priority: Blocker > > Facts: > # Operator creates and manges internaly several kubernetes objects; StatefulSet, Pod, Service, Routes. By rough estimation these kubernetes objects expose approximately 50 options[2]. Operator now expose approximately 10 options [1]. > # EAP7-1192 is currently designed in way operator is integral part of solution. You can not turn off operator to EAP7-1192 properly work. > # User cant touch internal Kubernetes objects. Operator manages them and can overwrite changes anytime. > So given these facts question is what is long-term strategy with Operator? > # Operator will provide all options of internal objects. Everything I am able to configure directly with Kubernetes objects I will be able to configure with Operator > # Operator will expose just most useful options. If user wants to make something special he has to "turn off" operator and to be on his own. (Loosing transaction support provided by EAP7-1192) > # Operator will expose just most useful options. If user wants to make something special he can and Operator won't overwritten his changes. (I dont know if it is feasible?) > [1] https://github.com/wildfly/wildfly-operator/blob/master/doc/apis.adoc#wil... > [2] > https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.15/#pods... > https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.15/#stat... > https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.15/#serv... > https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.15/#ingr... -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4503) "Error" popup report java literal for suggested number

by Yeser Amer (Jira)

[ https://issues.jboss.org/browse/DROOLS-4503?page=com.atlassian.jira.plugi... ] Yeser Amer resolved DROOLS-4503. -------------------------------- Resolution: Done > "Error" popup report java literal for suggested number > ------------------------------------------------------ > > Key: DROOLS-4503 > URL: https://issues.jboss.org/browse/DROOLS-4503 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.26.0.Final > Reporter: Gabriele Cardosi > Assignee: Yeser Amer > Priority: Major > Labels: ScenarioSimulation > Attachments: ErrorPopup.png, FollowError.png, InsertedValue.png > > > When the expected value for a field is a java long, the error popup reports > "The expected value is '2' but the actual one is '3L'." > !ErrorPopup.png|thumbnail! > That means the java literal is used for the suggested (correct) value, while the inserted value as-is is shown as the one to correct. _Of course it is possible that this apply to all types whose java literal representation is different then "absolute" value._ > This is a little bit inconsistent and confusing, especially for someone not knowing java. > The worst consequence is that when user click "Apply", that literal is put inside the cell, > !InsertedValue.png|thumbnail! > and when sent to server it raise error (because server is expecting a number, not a string) > !FollowError.png|thumbnail! -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4503) "Error" popup report java literal for suggested number

by Yeser Amer (Jira)

[ https://issues.jboss.org/browse/DROOLS-4503?page=com.atlassian.jira.plugi... ] Yeser Amer reopened DROOLS-4503: -------------------------------- > "Error" popup report java literal for suggested number > ------------------------------------------------------ > > Key: DROOLS-4503 > URL: https://issues.jboss.org/browse/DROOLS-4503 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.26.0.Final > Reporter: Gabriele Cardosi > Assignee: Yeser Amer > Priority: Major > Labels: ScenarioSimulation > Attachments: ErrorPopup.png, FollowError.png, InsertedValue.png > > > When the expected value for a field is a java long, the error popup reports > "The expected value is '2' but the actual one is '3L'." > !ErrorPopup.png|thumbnail! > That means the java literal is used for the suggested (correct) value, while the inserted value as-is is shown as the one to correct. _Of course it is possible that this apply to all types whose java literal representation is different then "absolute" value._ > This is a little bit inconsistent and confusing, especially for someone not knowing java. > The worst consequence is that when user click "Apply", that literal is put inside the cell, > !InsertedValue.png|thumbnail! > and when sent to server it raise error (because server is expecting a number, not a string) > !FollowError.png|thumbnail! -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3652) DMN popover - Enter to apply

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3652?page=com.atlassian.jira.plugi... ] Jozef Marko commented on DROOLS-3652: ------------------------------------- [~uxdlc] hello, in the attached popover is also *Data Type* selectbox. What should be the behavior when the enter is pressed while selectbox has a focus? > DMN popover - Enter to apply > ----------------------------- > > Key: DROOLS-3652 > URL: https://issues.jboss.org/browse/DROOLS-3652 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Elizabeth Clayton > Assignee: Michael Anstis > Priority: Major > Labels: UX, drools-tools > Attachments: Screen Shot 2019-02-13 at 1.20.35 PM.png > > > When the user changes the field value (name in this example), it would be nice if hitting ENTER would apply the name, and take the focus highlight off. The other field is being applied dynamically, so the assumption is that this one is as well. > !Screen Shot 2019-02-13 at 1.20.35 PM.png|thumbnail! > p.s. this is the pop-over that needs to be updated to support Expression instead of Name. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3652) DMN popover - Enter to apply

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3652?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-3652: -------------------------------- Tester: Jozef Marko > DMN popover - Enter to apply > ----------------------------- > > Key: DROOLS-3652 > URL: https://issues.jboss.org/browse/DROOLS-3652 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Elizabeth Clayton > Assignee: Michael Anstis > Priority: Major > Labels: UX, drools-tools > Attachments: Screen Shot 2019-02-13 at 1.20.35 PM.png > > > When the user changes the field value (name in this example), it would be nice if hitting ENTER would apply the name, and take the focus highlight off. The other field is being applied dynamically, so the assumption is that this one is as well. > !Screen Shot 2019-02-13 at 1.20.35 PM.png|thumbnail! > p.s. this is the pop-over that needs to be updated to support Expression instead of Name. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4669) Licenses cleanup

by Brian Stansberry (Jira)

Brian Stansberry created WFCORE-4669: ---------------------------------------- Summary: Licenses cleanup Key: WFCORE-4669 URL: https://issues.jboss.org/browse/WFCORE-4669 Project: WildFly Core Issue Type: Task Components: Build System Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 10.0.0.CR1 Review the licenses.xml file and various license texts, do any necessary cleanup, e..g use the standard license names. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12188) Option READ_TIMEOUT is ignored

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12188?page=com.atlassian.jira.plugin... ] Brian Stansberry commented on WFLY-12188: ----------------------------------------- [~flavia.rainone] We'd discussed this a bit elsewhere; I'm saying the same here. +1 for documentation. If setting those options on the http-connector resource ever worked, let me know. If configuring the options on the http-connector resource isn't really useful or isn't achievable at a cost that's acceptable, then the resource should be marked as deprecated. That will result in a message in the server log if they are configured. And then in a future release we can remove the resource. Neither the need for docs nor the task to deprecate the resource are Blocker priority. > Option READ_TIMEOUT is ignored > ------------------------------ > > Key: WFLY-12188 > URL: https://issues.jboss.org/browse/WFLY-12188 > Project: WildFly > Issue Type: Bug > Components: EJB, Remoting > Affects Versions: 17.0.0.Final > Reporter: Joerg Baesner > Assignee: Flavia Rainone > Priority: Blocker > Labels: blocker-WF18 > > What's the difference of the {{READ_TIMEOUT}} in _ejb3_ subsystem vs. _remoting_ subsystem? See: > {code} > <remote connector-ref="http-remoting-connector" thread-pool-name="default"> > <channel-creation-options> > <option name="READ_TIMEOUT" value="${prop.remoting-connector.read.timeout:20}" type="xnio"/> > <option name="MAX_OUTBOUND_MESSAGES" value="1234" type="remoting"/> > </channel-creation-options> > </remote> > {code} > {code} > <subsystem xmlns="urn:jboss:domain:remoting:4.0"> > <endpoint/> > <http-connector name="http-remoting-connector" connector-ref="default" security-realm="ApplicationRealm"> >  > <properties> > <property name="org.jboss.remoting3.RemotingOptions.HEARTBEAT_INTERVAL" value="5000"/> > <property name="KEEP_ALIVE" value="true"/> > <property name="READ_TIMEOUT" value="10000"/> > <property name="WRITE_TIMEOUT" value="10000"/> > </properties> > </http-connector> > {code} > None of those options work. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2019