November 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-1973) [DMN Editor] Test marshalling of Decision Literal Expressions

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1973?page=com.atlassian.jira.plugi... ] Edson Tirelli updated DROOLS-1973: ---------------------------------- Fix Version/s: (was: 7.5.0.Final) > [DMN Editor] Test marshalling of Decision Literal Expressions > ------------------------------------------------------------- > > Key: DROOLS-1973 > URL: https://issues.jboss.org/browse/DROOLS-1973 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Jozef Marko > Assignee: Jozef Marko > > Test marshalling of literal expressions. Get inspiration for expressions in the [github dmn respository|https://github.com/kiegroup/drools/tree/master/kie-dmn/kie-dm...]. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1945) [DMN Editor] Logic validation

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1945?page=com.atlassian.jira.plugi... ] Edson Tirelli updated DROOLS-1945: ---------------------------------- Fix Version/s: (was: 7.5.0.Final) > [DMN Editor] Logic validation > ----------------------------- > > Key: DROOLS-1945 > URL: https://issues.jboss.org/browse/DROOLS-1945 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Optional > Labels: reported-by-qe > > The validation could reveal logical errors like missing ranges, subsumption, impossible matches. > The validation should depend on the selected hit policy. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1941) [DMN Editor] ToolBox: Add support for creating "source" nodes from a "target"

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1941?page=com.atlassian.jira.plugi... ] Edson Tirelli updated DROOLS-1941: ---------------------------------- Fix Version/s: (was: 7.5.0.Final) > [DMN Editor] ToolBox: Add support for creating "source" nodes from a "target" > ----------------------------------------------------------------------------- > > Key: DROOLS-1941 > URL: https://issues.jboss.org/browse/DROOLS-1941 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > > The "Toolbox" (see {{DMNFlowActionsToolboxControlProvider}}) currently supports creating "target" nodes from a "source" node and automatically joining "source" to "target" however [~tirelli] has requested the ability to select an existing "target" node and create a new "source" node from the Toolbox with the resulting connector joining "source" to "target". I.E. support creating the inverse of what is currently supported. > * Should be able to create a BKM from Decision (connection from BKM to Decision). At the moment you can select BKM and add Decision, but need to support selecting a Decision and making an incoming BKM > * Should be able to create a KnowledgeSources from bothh Decisions and BKMs. At the moment you can select a KnowledgeSource and adda Decision or BKM, but need to support selecting either a Decision or BKM and making an incoming KS -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1964) [DMN Editor] Input Data typeRef

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1964?page=com.atlassian.jira.plugi... ] Edson Tirelli updated DROOLS-1964: ---------------------------------- Fix Version/s: (was: 7.5.0.Final) > [DMN Editor] Input Data typeRef > ------------------------------- > > Key: DROOLS-1964 > URL: https://issues.jboss.org/browse/DROOLS-1964 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Jozef Marko > Assignee: Michael Anstis > Labels: reported-by-qe > > The Input Data nodes specifies the datatype via _typeRef_ attribute. Allowed are simple datatypes, enumerations of allowed values and complex data types like Person. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1971) [DMN Editor] Change DirectionalLine to extend AbstractOffsetMultiPointShape

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1971?page=com.atlassian.jira.plugi... ] Edson Tirelli updated DROOLS-1971: ---------------------------------- Fix Version/s: (was: 7.5.0.Final) > [DMN Editor] Change DirectionalLine to extend AbstractOffsetMultiPointShape > --------------------------------------------------------------------------- > > Key: DROOLS-1971 > URL: https://issues.jboss.org/browse/DROOLS-1971 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > Priority: Minor > > See:- > 1) https://github.com/manstis/kie-wb-common/commit/bde36c9a2f5b56d1adb13015c... > 2) https://github.com/manstis/kie-wb-common/commit/bde36c9a2f5b56d1adb13015c... > 3) <conan> manstis you want to extend {{AbstractOffsetMultiPointShape}} not {{AbstractDirectionalMultiPointShape}} as {{AbstractDirectionalMultiPointShape}} has 3 attributes, only applicable to orthogonal lines. you have neither a direction nor a direction. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1949) [DMN Editor]: Context Editor: Row heights should be based on content

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1949?page=com.atlassian.jira.plugi... ] Jozef Marko commented on DROOLS-1949: ------------------------------------- Thanks a lot, I prepared minimal coverage here https://github.com/manstis/kie-wb-common/pull/5. > [DMN Editor]: Context Editor: Row heights should be based on content > -------------------------------------------------------------------- > > Key: DROOLS-1949 > URL: https://issues.jboss.org/browse/DROOLS-1949 > 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)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9561) WildFly - Elytron - Programmatic login

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-9561?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-9561: ----------------------------------- Workaround Description: Before calling login call getSession(true) to ensure a session is created and available. > WildFly - Elytron - Programmatic login > -------------------------------------- > > Key: WFLY-9561 > URL: https://issues.jboss.org/browse/WFLY-9561 > Project: WildFly > Issue Type: Bug > Components: Security, Web (Undertow) > Affects Versions: 11.0.0.Final > Reporter: Stanislav Grushevskiy > Assignee: Darran Lofthouse > Fix For: 12.0.0.Alpha1 > > Attachments: test.zip > > > If Elytron security domain (in WildFly 11, default "standalone.xml") is used for programmatic login, cookie "JSESSIONID" is not set in response. So following requests are sent without "JSESSIONID". > @Path("login") > public class LoginService { > @Context > private HttpServletRequest request; > @POST > public void login(LoginForm form) throws ServletException { > request.login(form.getLogin(), form.getPassword()); > } > } > <?xml version="1.0" encoding="UTF-8"?> > <jboss-web> > <security-domain>application-security-domain</security-domain> > </jboss-web> > If I add manual interaction with Session in login method, "JSESSIONID" is set. > OR > If I delete "jboss-web.xml" and default old "ApplicationRealm" is used, "JSESSIONID" is set. > "JSESSIONID" is set in WildFly 10.0.0.Final and in 10.1.0.Final, because there is no Elytron there and "ApplicationRealm" is used. > Test project is attached, create application user (add-user.sh) with username "wildfly" and password "wildfly". > Run "mvn wildfly:deploy". > Go to http://localhost:8080/test/test.html and press "Login" button and then "Check Auth". > In this project you can uncomment code below (// uncomment the row below to get it working with elytron) to add session interaction or comment code below () to use old "ApplicationRealm". -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9561) WildFly - Elytron - Programmatic login

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-9561?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-9561: ----------------------------------- Fix Version/s: 12.0.0.Alpha1 > WildFly - Elytron - Programmatic login > -------------------------------------- > > Key: WFLY-9561 > URL: https://issues.jboss.org/browse/WFLY-9561 > Project: WildFly > Issue Type: Bug > Components: Security, Web (Undertow) > Affects Versions: 11.0.0.Final > Reporter: Stanislav Grushevskiy > Assignee: Darran Lofthouse > Fix For: 12.0.0.Alpha1 > > Attachments: test.zip > > > If Elytron security domain (in WildFly 11, default "standalone.xml") is used for programmatic login, cookie "JSESSIONID" is not set in response. So following requests are sent without "JSESSIONID". > @Path("login") > public class LoginService { > @Context > private HttpServletRequest request; > @POST > public void login(LoginForm form) throws ServletException { > request.login(form.getLogin(), form.getPassword()); > } > } > <?xml version="1.0" encoding="UTF-8"?> > <jboss-web> > <security-domain>application-security-domain</security-domain> > </jboss-web> > If I add manual interaction with Session in login method, "JSESSIONID" is set. > OR > If I delete "jboss-web.xml" and default old "ApplicationRealm" is used, "JSESSIONID" is set. > "JSESSIONID" is set in WildFly 10.0.0.Final and in 10.1.0.Final, because there is no Elytron there and "ApplicationRealm" is used. > Test project is attached, create application user (add-user.sh) with username "wildfly" and password "wildfly". > Run "mvn wildfly:deploy". > Go to http://localhost:8080/test/test.html and press "Login" button and then "Check Auth". > In this project you can uncomment code below (// uncomment the row below to get it working with elytron) to add session interaction or comment code below () to use old "ApplicationRealm". -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9561) WildFly - Elytron - Programmatic login

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-9561?page=com.atlassian.jira.plugin.... ] Darran Lofthouse commented on WFLY-9561: ---------------------------------------- I see the issue, before we store the identity in the session we are missing a check the session actually exists followed by a call to create it. > WildFly - Elytron - Programmatic login > -------------------------------------- > > Key: WFLY-9561 > URL: https://issues.jboss.org/browse/WFLY-9561 > Project: WildFly > Issue Type: Bug > Components: Security, Web (Undertow) > Affects Versions: 11.0.0.Final > Reporter: Stanislav Grushevskiy > Assignee: Darran Lofthouse > Attachments: test.zip > > > If Elytron security domain (in WildFly 11, default "standalone.xml") is used for programmatic login, cookie "JSESSIONID" is not set in response. So following requests are sent without "JSESSIONID". > @Path("login") > public class LoginService { > @Context > private HttpServletRequest request; > @POST > public void login(LoginForm form) throws ServletException { > request.login(form.getLogin(), form.getPassword()); > } > } > <?xml version="1.0" encoding="UTF-8"?> > <jboss-web> > <security-domain>application-security-domain</security-domain> > </jboss-web> > If I add manual interaction with Session in login method, "JSESSIONID" is set. > OR > If I delete "jboss-web.xml" and default old "ApplicationRealm" is used, "JSESSIONID" is set. > "JSESSIONID" is set in WildFly 10.0.0.Final and in 10.1.0.Final, because there is no Elytron there and "ApplicationRealm" is used. > Test project is attached, create application user (add-user.sh) with username "wildfly" and password "wildfly". > Run "mvn wildfly:deploy". > Go to http://localhost:8080/test/test.html and press "Login" button and then "Check Auth". > In this project you can uncomment code below (// uncomment the row below to get it working with elytron) to add session interaction or comment code below () to use old "ApplicationRealm". -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBAS-8319) [Regression in JBoss 5.x and 6.x compared to 4.x] VFS doesn't support fetching http resources

by Anand Babu (JIRA)

[ https://issues.jboss.org/browse/JBAS-8319?page=com.atlassian.jira.plugin.... ] Anand Babu commented on JBAS-8319: ---------------------------------- How to migrate services of MainDeployer and SubDeployer to wildfly or EAP. MainDeployer we used ejb-jar annotation. But I am unable to find for SubDeployer. > [Regression in JBoss 5.x and 6.x compared to 4.x] VFS doesn't support fetching http resources > --------------------------------------------------------------------------------------------- > > Key: JBAS-8319 > URL: https://issues.jboss.org/browse/JBAS-8319 > Project: Application Server 3 4 5 and 6 > Issue Type: Bug > Components: ProfileService > Affects Versions: JBossAS-5.0.1.GA, JBossAS-5.1.0.GA, 6.0.0.M4, 6.0.0.M5 > Environment: Bug has been observed on all three versions: > * JBoss 5.0.1 GA (jboss-vfs 2.1.2 GA) > * JBoss 5.1.0 GA (jboss-vfs 2.1.0 GA) > * JBoss 6.0.0 M4 (jboss-vfs 3.0.0 CR5) > Reporter: Savas Ali Tokmen > Assignee: Emanuel Muckenhuber > Labels: deployer, deployment, remote > Fix For: 6.0.0.CR1 > > Attachments: stacktrace-jboss-5.txt, stacktrace-jboss-6.txt, stacktrace-jboss6-m5.txt > > > I'm currently working on the porting of our JBoss 4.2 infrastructure to JBoss 5.x, and even maybe 6.x. > Since JBoss doesn't allow automated remote deployment (i.e., via JMX for example -a manual access to the JBoss console is necessary) of applications (WAR, EJBs, EARs, etc.), we used to call the JBoss MainDeployer's deploy method with a URL pointing to an HTTP URL which contains all our deployable artifacts. > As of JBoss 5.x, this broke. I'm attaching stack traces for JBoss 5.1.0 and JBoss 6.0.0 M3: > * In JBoss 5 we clearly see that org.jboss.virtual.VFS.getVFS throws: java.io.IOException: No context factory for http://192.168.0.12:58407/simple-war-1.0.3-SNAPSHOT.war > * In JBoss 6 the exception is even more interesting: Invalid or unreadable WAR file : /simple-war-1.0.3-SNAPSHOT.war -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 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 November 2017