July 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-3660) allow easy creation of executable war

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-3660?page=com.atlassian.jira.plugin.... ] James Perkins commented on WFLY-3660: ------------------------------------- Actually I lied, it might not be as easy as I thought :) I forgot about the data directory and the deployment directory that are currently not allowed to be overridden. They would need to be writable. At least the data directory would need to be... ...anyway just throwing some thoughts out there. > allow easy creation of executable war > ------------------------------------- > > Key: WFLY-3660 > URL: https://issues.jboss.org/browse/WFLY-3660 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Server > Affects Versions: 8.1.0.Final > Reporter: jieryn jieryn > Assignee: Jason Greene > Priority: Minor > > Other popular Servlet Containers and Application Servers support the building of an executable war bundle, via Apache Maven. This will allow you to easily bundle your WAR/EAR into an executable war which will unpack and launch the WAR/EAR, via java -jar myapp.war. > http://tomcat.apache.org/maven-plugin-2.0/tomcat7-maven-plugin/exec-war-m... > http://rmannibucau.wordpress.com/2014/03/11/executable-jar-with-tomee-and... -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3660) allow easy creation of executable war

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-3660?page=com.atlassian.jira.plugin.... ] James Perkins edited comment on WFLY-3660 at 7/23/14 11:56 AM: --------------------------------------------------------------- Seems doable from the wildfly-maven-plugin. It could make the final archive rather large though as I assume it would need to bundle everything in an uber JAR. Maybe not a huge deal though. I'd be happy to take this on. was (Author: jamezp): Seems doable from the wildfly-maven-plugin. It could make the final archive rather large though as I assume it would need to bundle everything in an uber JAR. Maybe not a huge deal though. > allow easy creation of executable war > ------------------------------------- > > Key: WFLY-3660 > URL: https://issues.jboss.org/browse/WFLY-3660 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Server > Affects Versions: 8.1.0.Final > Reporter: jieryn jieryn > Assignee: Jason Greene > Priority: Minor > > Other popular Servlet Containers and Application Servers support the building of an executable war bundle, via Apache Maven. This will allow you to easily bundle your WAR/EAR into an executable war which will unpack and launch the WAR/EAR, via java -jar myapp.war. > http://tomcat.apache.org/maven-plugin-2.0/tomcat7-maven-plugin/exec-war-m... > http://rmannibucau.wordpress.com/2014/03/11/executable-jar-with-tomee-and... -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3660) allow easy creation of executable war

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-3660?page=com.atlassian.jira.plugin.... ] James Perkins commented on WFLY-3660: ------------------------------------- Seems doable from the wildfly-maven-plugin. It could make the final archive rather large though as I assume it would need to bundle everything in an uber JAR. Maybe not a huge deal though. > allow easy creation of executable war > ------------------------------------- > > Key: WFLY-3660 > URL: https://issues.jboss.org/browse/WFLY-3660 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Server > Affects Versions: 8.1.0.Final > Reporter: jieryn jieryn > Assignee: Jason Greene > Priority: Minor > > Other popular Servlet Containers and Application Servers support the building of an executable war bundle, via Apache Maven. This will allow you to easily bundle your WAR/EAR into an executable war which will unpack and launch the WAR/EAR, via java -jar myapp.war. > http://tomcat.apache.org/maven-plugin-2.0/tomcat7-maven-plugin/exec-war-m... > http://rmannibucau.wordpress.com/2014/03/11/executable-jar-with-tomee-and... -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3660) allow easy creation of executable war

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-3660?page=com.atlassian.jira.plugin.... ] James Perkins updated WFLY-3660: -------------------------------- Priority: Minor (was: Major) > allow easy creation of executable war > ------------------------------------- > > Key: WFLY-3660 > URL: https://issues.jboss.org/browse/WFLY-3660 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Server > Affects Versions: 8.1.0.Final > Reporter: jieryn jieryn > Assignee: Jason Greene > Priority: Minor > > Other popular Servlet Containers and Application Servers support the building of an executable war bundle, via Apache Maven. This will allow you to easily bundle your WAR/EAR into an executable war which will unpack and launch the WAR/EAR, via java -jar myapp.war. > http://tomcat.apache.org/maven-plugin-2.0/tomcat7-maven-plugin/exec-war-m... > http://rmannibucau.wordpress.com/2014/03/11/executable-jar-with-tomee-and... -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 12 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-561) Having a shared Query Node as last node of a segment causes a NPE

by Mario Fusco (JIRA)

Mario Fusco created DROOLS-561: ---------------------------------- Summary: Having a shared Query Node as last node of a segment causes a NPE Key: DROOLS-561 URL: https://issues.jboss.org/browse/DROOLS-561 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Mario Fusco Assignee: Mark Proctor Having a shared Query Node as last node of a segment causes a NPE as in the following test case {code} @Test public void testSharedQueryNode() throws Exception { String drl = "query find( Integer $i, String $s )\n" + " $i := Integer( toString() == $s )\n" + "end\n" + "\n" + "rule R2 salience -1 when\n" + " $s : String()\n" + " ?find( i, $s; )\n" + "then\n" + "end\n" + "rule R1 when\n" + " $s : String()\n" + " ?find( i, $s; )\n" + " $i : Integer( this == 1 ) from i\n" + "then\n" + " delete( $s );\n" + "end\n"; KieHelper helper = new KieHelper(); helper.addContent( drl, ResourceType.DRL ); KieSession ksession = helper.build().newKieSession(); ksession.insert("1"); ksession.insert(1); ksession.fireAllRules(); } {code} causes a NullPointerException like: java.lang.NullPointerException at org.drools.core.common.LeftTupleSetsImpl.removeInsert(LeftTupleSetsImpl.java:136) at org.drools.core.phreak.RuleNetworkEvaluator.deleteLeftChild(RuleNetworkEvaluator.java:754) at org.drools.core.phreak.PhreakQueryNode.doLeftDeletes(PhreakQueryNode.java:175) at org.drools.core.phreak.PhreakQueryNode.doNode(PhreakQueryNode.java:31) at org.drools.core.phreak.RuleNetworkEvaluator.evalQueryNode(RuleNetworkEvaluator.java:464) at org.drools.core.phreak.RuleNetworkEvaluator.innerEval(RuleNetworkEvaluator.java:353) at org.drools.core.phreak.RuleNetworkEvaluator.outerEval(RuleNetworkEvaluator.java:161) at org.drools.core.phreak.RuleNetworkEvaluator.evaluateNetwork(RuleNetworkEvaluator.java:116) at org.drools.core.phreak.RuleExecutor.reEvaluateNetwork(RuleExecutor.java:216) at org.drools.core.phreak.RuleExecutor.evaluateNetworkAndFire(RuleExecutor.java:91) at org.drools.core.common.DefaultAgenda.fireNextItem(DefaultAgenda.java:964) at org.drools.core.common.DefaultAgenda.fireAllRules(DefaultAgenda.java:1234) -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3660) allow easy creation of executable war

by jieryn jieryn (JIRA)

jieryn jieryn created WFLY-3660: ----------------------------------- Summary: allow easy creation of executable war Key: WFLY-3660 URL: https://issues.jboss.org/browse/WFLY-3660 Project: WildFly Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Server Affects Versions: 8.1.0.Final Reporter: jieryn jieryn Assignee: Jason Greene Other popular Servlet Containers and Application Servers support the building of an executable war bundle, via Apache Maven. This will allow you to easily bundle your WAR/EAR into an executable war which will unpack and launch the WAR/EAR, via java -jar myapp.war. http://tomcat.apache.org/maven-plugin-2.0/tomcat7-maven-plugin/exec-war-m... http://rmannibucau.wordpress.com/2014/03/11/executable-jar-with-tomee-and... -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2738) Deprecated resource is present in r-r-d of /subsystem=security/security-domain=*

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-2738?page=com.atlassian.jira.plugin.... ] Brian Stansberry commented on WFLY-2738: ---------------------------------------- Good question. That seems to be the heart of this JIRA. It seems the code actually works as expected and this a request for a behavior change and not really a bug. The problem is the child registration at the *complete path element* login-module=* is an alias. But there's nothing that says the *child type login-module alone* is an alias. It's a valid child-type. It's not the case in this particular security subsystem example, but it's perfectly possible that one complete path element for a given type is an alias while another is not. If practical we could change the behavior to examine all the children registration of a given type and not report the type at all if all of them are aliases. *However* if we change the behavior, we also must change read-children-types to have a matching semantic. {code} [standalone@localhost:9990 /] /subsystem=security/security-domain=other/acl=classic:read-children-types { "outcome" => "success", "result" => [ "acl-module", "login-module" ] } {code} We would need to add an include-aliases param, default value of false to match r-r-d, and then not include the child-type in the result if r-r-d wouldn't include it. I'm ok with making that change, but it is a breaking change, and it's likely quite a bit more work than I expected. So before doing that, please chat with Harald or Heiko to get a sense about how important this is to them. > Deprecated resource is present in r-r-d of /subsystem=security/security-domain=* > -------------------------------------------------------------------------------- > > Key: WFLY-2738 > URL: https://issues.jboss.org/browse/WFLY-2738 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.0.0.CR1 > Reporter: Harald Pehl > Assignee: Emmanuel Hugonnet > Priority: Minor > Fix For: 9.0.0.CR1 > > > When executing > {code} > /subsystem=security/security-domain=*:read-resource-description(recursive-depth=2) > {code} > the acl subresource contains both the deprecated child-resource {{login-module}} and the new one called {{acl-module}}: > {code} > ... > "acl" => { > "description" => "Access control list configuration. Configures a list of ACL modules to be used.", > "model-description" => {"classic" => { > "description" => "Access control list configuration. Configures a list of ACL modules to be used.", > ... > "operations" => undefined, > "children" => { > "acl-module" => { > "description" => "ACL module", > "model-description" => {"*" => { > "description" => "List of authentication modules", > ... > "operations" => undefined, > "children" => {} > }} > }, > "login-module" => { > "description" => "Login module", > "model-description" => {"*" => undefined} > } > } > }} > }, > ... > {code} > However the deprecated subresource {{login-modules}} should only appear if setting {{include-aliases=true}} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 12 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-553) Build does not build on maven 3.2.2 with an empty repository

by Geoffrey De Smet (JIRA)

[ https://issues.jboss.org/browse/DROOLS-553?page=com.atlassian.jira.plugin... ] Geoffrey De Smet resolved DROOLS-553. ------------------------------------- Resolution: Deferred Regression in maven 3.2.2. Fixed by Maven 3.2.3 (see jira link above). Closing this issue on our side. > Build does not build on maven 3.2.2 with an empty repository > ------------------------------------------------------------ > > Key: DROOLS-553 > URL: https://issues.jboss.org/browse/DROOLS-553 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Geoffrey De Smet > Assignee: Michael Biarnes Kiefer > Priority: Blocker > > Our community contributors should be able to just build our stuff with the latest maven version. Currently that doesn't work. > Building with maven 3.0.5 works. > To reproduce: > - Use maven 3.2.2 > - Build droolsjbpm-build-bootstrap > - Do not build uberfire first > - rm ~/.m2/repository/org/uberfire > => this will force droolsjbpm-build-bootstrap to download the uberfire-bom 6.2.0-SNAPSHOT, which fails with maven 3.2.2: > {code} > $ mvn clean install -Dfull -DskipTests -U > [INFO] Scanning for projects... > [ERROR] The build could not read 1 project -> [Help 1] > [ERROR] > [ERROR] The project org.kie:kie-parent-with-dependencies:6.2.0-SNAPSHOT (/Users/.../OptaPlanner/droolsjbpm-build-bootstrap/kie-parent-with-dependencies/pom.xml) has 1 error > [ERROR] Non-resolvable import POM: Could not find artifact org.uberfire:uberfire-bom:pom:0.4.2-SNAPSHOT @ org.kie:kie-parent-with-dependencies:[unknown-version], /Users/.../OptaPlanner/droolsjbpm-build-bootstrap/kie-parent-with-dependencies/pom.xml, line 137, column 19 -> [Help 2] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please read the following articles: > [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException > [ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1197) Prefill does not work for the last connection url when HA Datasource failover is enabled

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1197?page=com.atlassian.jira.plugin... ] Jesper Pedersen resolved JBJCA-1197. ------------------------------------ Resolution: Done > Prefill does not work for the last connection url when HA Datasource failover is enabled > ---------------------------------------------------------------------------------------- > > Key: JBJCA-1197 > URL: https://issues.jboss.org/browse/JBJCA-1197 > Project: IronJacamar > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JDBC > Affects Versions: 1.0.26.Final, 1.1.6.Final, 1.2.0.Beta3 > Reporter: Masafumi Miura > Assignee: Masafumi Miura > Fix For: 1.0.27.Final, 1.1.7.Final, 1.2.0.Beta4 > > > See [https://bugzilla.redhat.com/show_bug.cgi?id=1120892] -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1197) Prefill does not work for the last connection url when HA Datasource failover is enabled

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1197?page=com.atlassian.jira.plugin... ] Jesper Pedersen updated JBJCA-1197: ----------------------------------- Fix Version/s: 1.0.27.Final 1.1.7.Final 1.2.0.Beta4 Assignee: Masafumi Miura (was: Jesper Pedersen) Affects Version/s: 1.2.0.Beta3 1.1.6.Final 1.0.26.Final > Prefill does not work for the last connection url when HA Datasource failover is enabled > ---------------------------------------------------------------------------------------- > > Key: JBJCA-1197 > URL: https://issues.jboss.org/browse/JBJCA-1197 > Project: IronJacamar > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JDBC > Affects Versions: 1.0.26.Final, 1.1.6.Final, 1.2.0.Beta3 > Reporter: Masafumi Miura > Assignee: Masafumi Miura > Fix For: 1.0.27.Final, 1.1.7.Final, 1.2.0.Beta4 > > > See [https://bugzilla.redhat.com/show_bug.cgi?id=1120892] -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 12 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 July 2014