February 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2294) Missing dependency in kie-api OSGi MANIFEST

by Iacopo Colonnelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2294?page=com.atlassian.jira.plugi... ] Iacopo Colonnelli updated DROOLS-2294: -------------------------------------- Issue Type: Bug (was: Feature Request) > Missing dependency in kie-api OSGi MANIFEST > ------------------------------------------- > > Key: DROOLS-2294 > URL: https://issues.jboss.org/browse/DROOLS-2294 > Project: Drools > Issue Type: Bug > Components: build > Affects Versions: 7.5.0.Final > Environment: OSGi > Reporter: Iacopo Colonnelli > Assignee: Petr Široký > > kie-api KieService contains method newKieModukeModel(), that tries to instantiate a new KieModuleModelImpl() object. Since KieModuleModelImpl class is included in package "org.drools.compiler.kproject.models", which is exported by drools-compiler module but NOT IMPORTED by kie-api module, calling newKieModuleModel() method results in a ClassDefNotFoundException. > Please add "org.drools.compiler.kproject.models" to kie-api's imported package -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3553) Improve message from CLI when writing into the directory without permission

by Katerina Novotna (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3553?page=com.atlassian.jira.plugi... ] Katerina Novotna commented on WFCORE-3553: ------------------------------------------ [~mstefank] The message is fine. Why is there that third line? {code:java} aaa > ./dir/without/permission {code} > Improve message from CLI when writing into the directory without permission > --------------------------------------------------------------------------- > > Key: WFCORE-3553 > URL: https://issues.jboss.org/browse/WFCORE-3553 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 4.0.0.Alpha6 > Reporter: Katerina Novotna > Assignee: Martin Stefanko > Priority: Minor > > *Description of problem:* > Cli displays java exception name when trying to write into the file without permission. > *Actual results:* > [standalone@embedded /] echo aaa > /dir/without/permission > java.nio.file.AccessDeniedException: /dir/without/permission > *Expected results:* > [standalone@embedded /] echo aaa > /dir/without/permission > Couldn't write into the /dir/without/permission. Permission denied. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9756) Wildfly Swarm Odata v4

by Arvind Gopinath (JIRA)

[ https://issues.jboss.org/browse/WFLY-9756?page=com.atlassian.jira.plugin.... ] Arvind Gopinath updated WFLY-9756: ---------------------------------- Description: Hi Team, I am looking for sample code for exposing odata for the below example - I could able to run the below example and query through SQL client. Same if I want to expose through Odata v4, how it needs to be done? https://github.com/teiid/wildfly-swarm-teiid-examples/tree/master/vdb-dat... http://docs.wildfly-swarm.io/2017.12.1/#_teiid_odata <dependency> <groupId>org.wildfly.swarm</groupId> <artifactId>odata</artifactId> </dependency> was: Hi Team, I am looking for sample code for exposing odata for the below example - I could able to run the below example and query through SQL client. Same if I want to expose through Odata v4, how it needs to be done? https://github.com/teiid/wildfly-swarm-teiid-examples/tree/master/vdb-dat... > Wildfly Swarm Odata v4 > ---------------------- > > Key: WFLY-9756 > URL: https://issues.jboss.org/browse/WFLY-9756 > Project: WildFly > Issue Type: Feature Request > Reporter: Arvind Gopinath > Assignee: Jason Greene > Priority: Minor > > Hi Team, > I am looking for sample code for exposing odata for the below example - > I could able to run the below example and query through SQL client. Same if I want to expose through Odata v4, how it needs to be done? > https://github.com/teiid/wildfly-swarm-teiid-examples/tree/master/vdb-dat... > http://docs.wildfly-swarm.io/2017.12.1/#_teiid_odata > <dependency> > <groupId>org.wildfly.swarm</groupId> > <artifactId>odata</artifactId> > </dependency> -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9756) Wildfly Swarm Odata v4

by Arvind Gopinath (JIRA)

[ https://issues.jboss.org/browse/WFLY-9756?page=com.atlassian.jira.plugin.... ] Arvind Gopinath updated WFLY-9756: ---------------------------------- Description: Hi Team, I am looking for sample code for exposing odata for the below example - I could able to run the below example and query through SQL client. Same if I want to expose through Odata v4, how it needs to be done? https://github.com/teiid/wildfly-swarm-teiid-examples/tree/master/vdb-dat... was: Hi Team, I am looking for sample code for exposing odata for the below example - I could able to run the below example and query through SQL client. Same if I want to expose through Odata, how it needs to be done? https://github.com/teiid/wildfly-swarm-teiid-examples/tree/master/vdb-dat... > Wildfly Swarm Odata v4 > ---------------------- > > Key: WFLY-9756 > URL: https://issues.jboss.org/browse/WFLY-9756 > Project: WildFly > Issue Type: Feature Request > Reporter: Arvind Gopinath > Assignee: Jason Greene > Priority: Minor > > Hi Team, > I am looking for sample code for exposing odata for the below example - > I could able to run the below example and query through SQL client. Same if I want to expose through Odata v4, how it needs to be done? > https://github.com/teiid/wildfly-swarm-teiid-examples/tree/master/vdb-dat... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9756) Wildfly Swarm Odata v4

by Arvind Gopinath (JIRA)

[ https://issues.jboss.org/browse/WFLY-9756?page=com.atlassian.jira.plugin.... ] Arvind Gopinath updated WFLY-9756: ---------------------------------- Description: Hi Team, I am looking for sample code for exposing odata for the below example - I could able to run the below example and query through SQL client. Same if I want to expose through Odata, how it needs to be done? https://github.com/teiid/wildfly-swarm-teiid-examples/tree/master/vdb-dat... was: Hi Team, I am looking for sample code for exposing odata for the below example - > Wildfly Swarm Odata v4 > ---------------------- > > Key: WFLY-9756 > URL: https://issues.jboss.org/browse/WFLY-9756 > Project: WildFly > Issue Type: Feature Request > Reporter: Arvind Gopinath > Assignee: Jason Greene > Priority: Minor > > Hi Team, > I am looking for sample code for exposing odata for the below example - > I could able to run the below example and query through SQL client. Same if I want to expose through Odata, how it needs to be done? > https://github.com/teiid/wildfly-swarm-teiid-examples/tree/master/vdb-dat... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9756) Wildfly Swarm Odata v4

by Arvind Gopinath (JIRA)

Arvind Gopinath created WFLY-9756: ------------------------------------- Summary: Wildfly Swarm Odata v4 Key: WFLY-9756 URL: https://issues.jboss.org/browse/WFLY-9756 Project: WildFly Issue Type: Feature Request Reporter: Arvind Gopinath Assignee: Jason Greene Priority: Minor Hi Team, I am looking for sample code for exposing odata for the below example - -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9753) Promote best practice for PRs by using PR template

by Rostislav Svoboda (JIRA)

[ https://issues.jboss.org/browse/WFLY-9753?page=com.atlassian.jira.plugin.... ] Rostislav Svoboda updated WFLY-9753: ------------------------------------ Git Pull Request: https://github.com/wildfly/wildfly/pull/10809 > Promote best practice for PRs by using PR template > -------------------------------------------------- > > Key: WFLY-9753 > URL: https://issues.jboss.org/browse/WFLY-9753 > Project: WildFly > Issue Type: Task > Reporter: Rostislav Svoboda > Assignee: Rostislav Svoboda > > Promote best practice for PRs by using PR template > Templates on GitHub: > * https://github.com/blog/2111-issue-and-pull-request-templates > * https://github.com/blog/2495-multiple-issue-and-pull-request-templates -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9754) Global flag to supress transaction propagation for EJB clients inside of an server application

by Wolf-Dieter Fink (JIRA)

[ https://issues.jboss.org/browse/WFLY-9754?page=com.atlassian.jira.plugin.... ] Wolf-Dieter Fink reassigned WFLY-9754: -------------------------------------- Assignee: David Lloyd > Global flag to supress transaction propagation for EJB clients inside of an server application > ---------------------------------------------------------------------------------------------- > > Key: WFLY-9754 > URL: https://issues.jboss.org/browse/WFLY-9754 > Project: WildFly > Issue Type: Feature Request > Components: EJB > Environment: JEE application inside of WildFly using remote invocation to EJB's deployed in another WildFly instance > Reporter: Wolf-Dieter Fink > Assignee: David Lloyd > > The remote interface can be marked with an annotation to control transaction propagation with > org.jboss.ejb.client.annotation.ClientTransactionPolicy.* > This can be useful if the application need to ensure a specific Tx behaviour for this combination. > Remember the client does not know whether the server side is flagged to use Tx or not! > But there are different issues > - the Remote interface is polluted with WildFly specific annotations > consider the interface could be used in an environment without WildFly > - any call to the remote application should not propagate Tx context > - any call to a remote server should not propagate a Tx context > Consider former versions where able to control the Tx propagation by using JTA or JTS > To have more control for the application assembler or server administrator the transaction propagation should be controlled with deployment descriptor or server configuration. > possible solutions to disable the Tx propagation > - add a flag in ejb-client.xml application descriptor (affect this application) > - add a configuration for remote-outbound-connection (affect this connection including a possible cluster) > - add a configuration server wide (affect all remote outbound connections) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9754) Global flag to supress transaction propagation for EJB clients inside of an server application

by Wolf-Dieter Fink (JIRA)

Wolf-Dieter Fink created WFLY-9754: -------------------------------------- Summary: Global flag to supress transaction propagation for EJB clients inside of an server application Key: WFLY-9754 URL: https://issues.jboss.org/browse/WFLY-9754 Project: WildFly Issue Type: Feature Request Components: EJB Environment: JEE application inside of WildFly using remote invocation to EJB's deployed in another WildFly instance Reporter: Wolf-Dieter Fink The remote interface can be marked with an annotation to control transaction propagation with org.jboss.ejb.client.annotation.ClientTransactionPolicy.* This can be useful if the application need to ensure a specific Tx behaviour for this combination. Remember the client does not know whether the server side is flagged to use Tx or not! But there are different issues - the Remote interface is polluted with WildFly specific annotations consider the interface could be used in an environment without WildFly - any call to the remote application should not propagate Tx context - any call to a remote server should not propagate a Tx context Consider former versions where able to control the Tx propagation by using JTA or JTS To have more control for the application assembler or server administrator the transaction propagation should be controlled with deployment descriptor or server configuration. possible solutions to disable the Tx propagation - add a flag in ejb-client.xml application descriptor (affect this application) - add a configuration for remote-outbound-connection (affect this connection including a possible cluster) - add a configuration server wide (affect all remote outbound connections) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9755) Global flag to supress transaction propagation for EJB clients inside of an server application

by Wolf-Dieter Fink (JIRA)

Wolf-Dieter Fink created WFLY-9755: -------------------------------------- Summary: Global flag to supress transaction propagation for EJB clients inside of an server application Key: WFLY-9755 URL: https://issues.jboss.org/browse/WFLY-9755 Project: WildFly Issue Type: Feature Request Components: EJB Environment: JEE application inside of WildFly using remote invocation to EJB's deployed in another WildFly instance Reporter: Wolf-Dieter Fink The remote interface can be marked with an annotation to control transaction propagation with org.jboss.ejb.client.annotation.ClientTransactionPolicy.* This can be useful if the application need to ensure a specific Tx behaviour for this combination. Remember the client does not know whether the server side is flagged to use Tx or not! But there are different issues - the Remote interface is polluted with WildFly specific annotations consider the interface could be used in an environment without WildFly - any call to the remote application should not propagate Tx context - any call to a remote server should not propagate a Tx context Consider former versions where able to control the Tx propagation by using JTA or JTS To have more control for the application assembler or server administrator the transaction propagation should be controlled with deployment descriptor or server configuration. possible solutions to disable the Tx propagation - add a flag in ejb-client.xml application descriptor (affect this application) - add a configuration for remote-outbound-connection (affect this connection including a possible cluster) - add a configuration server wide (affect all remote outbound connections) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 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 February 2018