April 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-732) Ability to declare a dependency on a service name

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-732?page=com.atlassian.jira.plugin.s... ] Stuart Douglas commented on WFLY-732: ------------------------------------- I think that the combination of inter deployment dependencies and @DependsOn is enough to satisfy all use cases that were discussed. Service names are non-portable and subject to change, so I don't really want to implement this directly unless there is no better solution. > Ability to declare a dependency on a service name > ------------------------------------------------- > > Key: WFLY-732 > URL: https://issues.jboss.org/browse/WFLY-732 > Project: WildFly > Issue Type: Feature Request > Reporter: Brad Maxwell > Assignee: Stuart Douglas > Fix For: Awaiting Volunteers > > > We have several use cases where we need dependencies between different deployments. > Such as > Singleton in ear1 which injects an ejb from ear2 using @EJB. At shutdown we need the Singleton to call a method to clean up on the ejb, however the ejb is sometimes shutdown before the Singleton. Using @DependsOn would allow the Singleton to depend on the EJB if the EJB is in the same ear as the Singleton, however it is not. > There are other use cases where resources are injected and we need the resources to still be deployed at shutdown so we can clean up the resources before they are undeployed. > Having a service name to depend on would be useful and if the name was configurable such that it does not based on the exact name of the deployment, it would be useful as using maven changes the deployment names when we rebuild and we do not want to have to change the code each time we rebuild. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBRULES-2423) "from" does not work correctly with events in STREAM mode

by Davide Sottara (JIRA)

[ https://issues.jboss.org/browse/JBRULES-2423?page=com.atlassian.jira.plug... ] Davide Sottara resolved JBRULES-2423. ------------------------------------- Fix Version/s: 5.5.0.Final (was: 6.0.0.Alpha1) Resolution: Done > "from" does not work correctly with events in STREAM mode > --------------------------------------------------------- > > Key: JBRULES-2423 > URL: https://issues.jboss.org/browse/JBRULES-2423 > Project: JBRULES > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: drools-core (fusion) > Affects Versions: 5.0.0.M1 > Environment: Drools Fusion 5.0+ with engine in STREAM mode > Reporter: Davide Sottara > Assignee: Edson Tirelli > Priority: Critical > Labels: from, fusion, stream > Fix For: 5.5.0.Final > > > In the simple test case below, Message is an instantaneous event (i.e. duration = 0) with a list of destinations. > -------------------------------------------------------------------------------------------------------------------------------------- > declare Message > @role( event ) > @timestamp(start) > @duration(duration) > end > > rule "Hello World" > when > m : Message( status == Message.HELLO, $myMessage : message, $destinations : dest) > $s : String() from $destinations > then > System.out.println( "Dear " + $s + " : >>> " + $myMessage ); > end > -------------------------------------------------------------------------------------------------------------------------------------- > if the engine is configured to work in STREAM mode, the output is > Dear NULL :>>> Hello World > ... > since the Strings extracted from the Collection "dest" have already been retracted by > the time the rule is fired, following the retraction of the Message event. > The problem does not show in CLOUD mode. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBRULES-3626) Add support for strong negation

by Davide Sottara (JIRA)

[ https://issues.jboss.org/browse/JBRULES-3626?page=com.atlassian.jira.plug... ] Davide Sottara reopened JBRULES-3626: ------------------------------------- Pending re-integration > Add support for strong negation > ------------------------------- > > Key: JBRULES-3626 > URL: https://issues.jboss.org/browse/JBRULES-3626 > Project: JBRULES > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Davide Sottara > Assignee: Davide Sottara > Priority: Minor > Fix For: 6.0.0.Alpha1 > > > Drools "not" operator implements a type of "negation by failure", i.e. not X() behaves as the negation of "exists" or, in other words, translates as "it is NOT asserted that ...". > However, another form of stronger negation is needed to express conditionals such as "it is asserted that NOT ..." > It should be possible, then, to assert facts both in a "positive" and "negative" way, to assert THAT and THAT NOT. > The language should also support a "neg" CE to create "negative" patterns which will match with negative facts. I.e. it should be possible to write rules such as: > when $p : Person() and Car( owner == $p ) then > // a positive, matching Car is present in the WM > when $p : Person() and neg Car( owner == $p ) then > // a negative, matching Car is present in the WM > when $p : Person() and not Car( owner == $p ) then > // neither a positive nor a negative fact exists in the WM > For a more detailed description and motivation see e.g.: > https://oxygen.informatik.tu-cottbus.de/publications/wagner/WebRules2Neg.pdf -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBRULES-3701) Add ability to trait a map

by Davide Sottara (JIRA)

[ https://issues.jboss.org/browse/JBRULES-3701?page=com.atlassian.jira.plug... ] Davide Sottara reassigned JBRULES-3701: --------------------------------------- Assignee: Davide Sottara (was: Mark Proctor) > Add ability to trait a map > -------------------------- > > Key: JBRULES-3701 > URL: https://issues.jboss.org/browse/JBRULES-3701 > Project: JBRULES > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: drools-core (expert) > Affects Versions: 5.5.0.Final > Reporter: Ming Fang > Assignee: Davide Sottara > > Add ability to trait a Map as described by Mark Proctor here > http://drools.46999.n3.nabble.com/rules-users-Maps-as-Object-in-Drools-td... > <quote> > //code below is illustrative of what is possible, if changes where mad for above idea. > // Create interface > Person > @Trait > String : name > int : age > end > // Identify the Map instance, and wrap it with the Person interface. > rule > $m : Map[ this['name'] != null, this['age'] != null ) > then > don( $m : Person.class ); > end > // Now the map is identified in a type safe manner. > rule > Person( name == "darth", age == 150 ) > then > …. > end > </quote> -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBRULES-3127) PackageBuilder should support an ordered iteration of added/merged packages

by Davide Sottara (JIRA)

[ https://issues.jboss.org/browse/JBRULES-3127?page=com.atlassian.jira.plug... ] Davide Sottara resolved JBRULES-3127. ------------------------------------- Fix Version/s: 5.5.0.Final Resolution: Done > PackageBuilder should support an ordered iteration of added/merged packages > ---------------------------------------------------------------------------- > > Key: JBRULES-3127 > URL: https://issues.jboss.org/browse/JBRULES-3127 > Project: JBRULES > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: drools-compiler > Reporter: Davide Sottara > Assignee: Mark Proctor > Priority: Minor > Fix For: 5.5.0.Final > > > The getPackages() method returns an array of packages which is based on the internal map's iteration order. > Instead, the order should depend on the package addition/merge sequence. > E.g. if a KnowledgeBuilder adds the following resources: > r1 -> package p1 > r2 -> package p2 > r3 -> package p2 > r4 -> package p3 > r5 -> package p1 > the sequence in the array should be p1, p3, p2 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-730) Special Characters in User Names

by Guillaume Grossetie (JIRA)

[ https://issues.jboss.org/browse/WFLY-730?page=com.atlassian.jira.plugin.s... ] Guillaume Grossetie commented on WFLY-730: ------------------------------------------ Is this issue related to the ./add-user.sh script which do not supports "-" in user names ? If this is the case, I can make a quick fix in [1] to add "-" to the valid punctuation list. [1] https://github.com/wildfly/wildfly/blob/master/domain-management/src/main... > Special Characters in User Names > -------------------------------- > > Key: WFLY-730 > URL: https://issues.jboss.org/browse/WFLY-730 > Project: WildFly > Issue Type: Feature Request > Components: Scripts > Reporter: Fernando Ribeiro > Fix For: Awaiting Volunteers > > > When working with domains, I've noticed that having special characters that are valid in host names (like "-") in user names should be supported to prevent having "fake" host names configured in host.xml files and displayed in the management interfaces. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-732) Ability to declare a dependency on a service name

by Dimitris Andreadis (JIRA)

[ https://issues.jboss.org/browse/WFLY-732?page=com.atlassian.jira.plugin.s... ] Dimitris Andreadis commented on WFLY-732: ----------------------------------------- Is this still worked on, or have you left it Stuart? > Ability to declare a dependency on a service name > ------------------------------------------------- > > Key: WFLY-732 > URL: https://issues.jboss.org/browse/WFLY-732 > Project: WildFly > Issue Type: Feature Request > Reporter: Brad Maxwell > Assignee: Stuart Douglas > Fix For: Awaiting Volunteers > > > We have several use cases where we need dependencies between different deployments. > Such as > Singleton in ear1 which injects an ejb from ear2 using @EJB. At shutdown we need the Singleton to call a method to clean up on the ejb, however the ejb is sometimes shutdown before the Singleton. Using @DependsOn would allow the Singleton to depend on the EJB if the EJB is in the same ear as the Singleton, however it is not. > There are other use cases where resources are injected and we need the resources to still be deployed at shutdown so we can clean up the resources before they are undeployed. > Having a service name to depend on would be useful and if the name was configurable such that it does not based on the exact name of the deployment, it would be useful as using maven changes the deployment names when we rebuild and we do not want to have to change the code each time we rebuild. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1086) Provide deployment manifest information via the CLI

by Dimitris Andreadis (JIRA)

[ https://issues.jboss.org/browse/WFLY-1086?page=com.atlassian.jira.plugin.... ] Dimitris Andreadis updated WFLY-1086: ------------------------------------- Priority: Critical (was: Major) > Provide deployment manifest information via the CLI > --------------------------------------------------- > > Key: WFLY-1086 > URL: https://issues.jboss.org/browse/WFLY-1086 > Project: WildFly > Issue Type: Feature Request > Components: CLI, Domain Management > Reporter: Brian Stansberry > Priority: Critical > > We've gotten a user request for providing the contents of a deployment's MANIFEST.MF via the CLI. > The request is to include an option to get the manifest info for a single deployment, and also the info for all deployments. > This task needs to be evaluated in relationship to the larger request to provide read (and possibly in some cases write) access to all files within a deployment. The manifest is essentially just one file with a standard location. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1291) Invalid package capabilities for registered modules

by Thomas Diesler (JIRA)

Thomas Diesler created WFLY-1291: ------------------------------------ Summary: Invalid package capabilities for registered modules Key: WFLY-1291 URL: https://issues.jboss.org/browse/WFLY-1291 Project: WildFly Issue Type: Bug Components: OSGi Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: 8.0.0.Alpha1 A jar registered with the OSGi layer exports the full transitive graph of reachable packages. It should however only expose its own package capabilities. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1290) VFSResourceLoader does not allow to iterate resources

by Thomas Diesler (JIRA)

Thomas Diesler created WFLY-1290: ------------------------------------ Summary: VFSResourceLoader does not allow to iterate resources Key: WFLY-1290 URL: https://issues.jboss.org/browse/WFLY-1290 Project: WildFly Issue Type: Bug Components: OSGi, Server Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: 8.0.0.Alpha1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2013