July 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBWEB-232) Allow StandardContext to expose start problems to callers instead of logging them

by Brian Stansberry (JIRA)

Brian Stansberry created JBWEB-232: -------------------------------------- Summary: Allow StandardContext to expose start problems to callers instead of logging them Key: JBWEB-232 URL: https://issues.jboss.org/browse/JBWEB-232 Project: JBoss Web Issue Type: Enhancement Security Level: Public (Everyone can see) Affects Versions: JBossWeb-7.0.10.GA Reporter: Brian Stansberry Assignee: Remy Maucherat See discussion of the log.txt attached to AS7-2322. That JIRA is about how AS7 handles exceptions, but in the case of the example the user attached, there is not much the AS can do. StandardContext is catching any exceptions that occur, logging at error, and then discarding the exception. I can see how this behavior might be appropriate for some usages, e.g. standalone Tomcat. And the logic after an exception is caught is complex, so I can see why just throwing a LifecycleException is not an option. But is it possible to have a configuration property on StandardContext such that instead of logging and discarding exceptions, it would *not* log them and retain the exception so the caller to start() could access it? Or perhaps throw it on in a LifecycleException at the end? Basically some mechanism such that the AS' WebDeploymentService could take responsibility for reporting the exception. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

2
1
0 / 0

[JBoss JIRA] (AS7-4355) Upgrade NekoHTML to 1.9.15

by Julio Pires (JIRA)

Julio Pires created AS7-4355: -------------------------------- Summary: Upgrade NekoHTML to 1.9.15 Key: AS7-4355 URL: https://issues.jboss.org/browse/AS7-4355 Project: Application Server 7 Issue Type: Library Upgrade Reporter: Julio Pires -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

2
1
0 / 0

[JBoss JIRA] (AS7-4356) Upgrade XOM to 1.2.7

by Julio Pires (JIRA)

Julio Pires created AS7-4356: -------------------------------- Summary: Upgrade XOM to 1.2.7 Key: AS7-4356 URL: https://issues.jboss.org/browse/AS7-4356 Project: Application Server 7 Issue Type: Library Upgrade Reporter: Julio Pires -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

2
1
0 / 0

[JBoss JIRA] (AS7-4351) Upgrade H2 driver to 1.3.165

by Julio Pires (JIRA)

Julio Pires created AS7-4351: -------------------------------- Summary: Upgrade H2 driver to 1.3.165 Key: AS7-4351 URL: https://issues.jboss.org/browse/AS7-4351 Project: Application Server 7 Issue Type: Component Upgrade Reporter: Julio Pires -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-8316) Simple command line installer

by Brian Stansberry (JIRA)

Simple command line installer ----------------------------- Key: JBAS-8316 URL: https://jira.jboss.org/browse/JBAS-8316 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Fix For: 7.0.0.M1 The AS is going to support two different running modes (see "Standalone Server" vs the rest of the discussion on http://community.jboss.org/docs/DOC-15215) and a flexible configuration for defining the "profile" a server will run. Profiles will not be represented via filesystem directories; rather they will be pure configuration. The two different running modes will result in slightly different filesystem layouts -- see discussion in http://community.jboss.org/thread/153858. The upshot of all this is using AS 7 will not be like previous versions where you could download the distribution, unzip, cd to bin/ and type ./run.sh -c some-std-config". Rather, I envision something like this: 1) download, unzip, cd bin 2) ./install.sh --someparamstotellitwhatyouwant Params to tell it what you want would be whether you're running in standalone mode or full domain, which of a set of pre-packaged profiles you want, maybe some more stuff. From this, installer would create the appropriate filesystem layout, generate a domain.xml+host.mxl or standalone.xml 3) ./run.sh -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

3
9
0 / 0

[JBoss JIRA] (JBRULES-3499) MVEL failing on new added packages

by Mauricio Salatino (JIRA)

Mauricio Salatino created JBRULES-3499: ------------------------------------------ Summary: MVEL failing on new added packages Key: JBRULES-3499 URL: https://issues.jboss.org/browse/JBRULES-3499 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Mauricio Salatino Assignee: Mark Proctor Fix For: 5.4.0.Final, 5.5.0.Beta1 Attachments: mvel-issue.zip In this simple rule: when r: Request( amount > 500 ) String( this == r.id ) from requests For some reason MVEL is failing with the following exception: Testcase: hello(com.salaboy.mvelissue.MvelTest): Caused an ERROR unable to invoke method: com.salaboy.mvelissue.Request.getId: target of method is null java.lang.RuntimeException: unable to invoke method: com.salaboy.mvelissue.Request.getId: target of method is null at org.mvel2.optimizers.impl.refl.nodes.GetterAccessor.getValue(GetterAccessor.java:66) When a new set of rules is being added to the kbase and an activation is generated. I've included a version of the failing rule working with a workaround, but both should work -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

4
5
0 / 0

[JBoss JIRA] Created: (AS7-784) Remove deployment doesn't really remove it

by Stan Silvert (JIRA)

Remove deployment doesn't really remove it ------------------------------------------ Key: AS7-784 URL: https://issues.jboss.org/browse/AS7-784 Project: Application Server 7 Issue Type: Bug Affects Versions: 7.0.0.Beta3 Reporter: Stan Silvert Assignee: Brian Stansberry Steps: 1) Deploy something by copying an archive to the standalone/deployments directory. 2) Using the CLI or Console, remove the deployment. i.e. /deployment=mywar.war/:remove The deployment will stop, but the .war file and .deployed marker remain on the file system. When you restart the server, mywar.war will deploy again. The problem is that "remove" doesn't really remove. It only stops the deployment until the next full restart. If you try to do some other operation on the deployment you will get a NoSuchElementException. And from the file system, it looks like the deployment is still deployed. So we need to do something to fully "remove" the deployment. Perhaps we need (yet another) marker file called .removed -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

6
10
0 / 0

[JBoss JIRA] (JBJCA-847) CodeGenerator Maven configuration misconfigures src/build paths, sets incorrect java version.

by Murray Todd Williams (JIRA)

Murray Todd Williams created JBJCA-847: ------------------------------------------ Summary: CodeGenerator Maven configuration misconfigures src/build paths, sets incorrect java version. Key: JBJCA-847 URL: https://issues.jboss.org/browse/JBJCA-847 Project: IronJacamar Issue Type: Bug Components: Code Generator Affects Versions: 1.1.0.Beta1 Reporter: Murray Todd Williams Assignee: Jesper Pedersen If one uses the CodeGenerator (via command line or Eclipse plugin) with the option to export to Maven, the resulting code (a) cannot be imported into an Eclipse Maven project, (b) cannot run a test via "mvn test" and (c) generates Eclipse code errors because the source/target are set to Java 1.5 but the @Override annotation is not allowed for Interface overrides in Java 1.5. (I've lumped these all into one JIRA ticket report because I think it can all be resolved with some tweaks to the pom.xml generation.) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

4
18
0 / 0

[JBoss JIRA] (AS7-5193) OSGi console allows to start/stop the system bundle

by Thomas Diesler (JIRA)

Thomas Diesler created AS7-5193: ----------------------------------- Summary: OSGi console allows to start/stop the system bundle Key: AS7-5193 URL: https://issues.jboss.org/browse/AS7-5193 Project: Application Server 7 Issue Type: Bug Components: Console, OSGi Reporter: Thomas Diesler Assignee: David Bosschaert Fix For: 7.2.0.CR1 Start/Stop on the system bundle are invalid operations -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

3
6
0 / 0

[JBoss JIRA] (AS7-5120) Improve jboss maven plugin to allow to start server as embedded

by Charles Moulliard (JIRA)

Charles Moulliard created AS7-5120: -------------------------------------- Summary: Improve jboss maven plugin to allow to start server as embedded Key: AS7-5120 URL: https://issues.jboss.org/browse/AS7-5120 Project: Application Server 7 Issue Type: Feature Request Reporter: Charles Moulliard The existing jboss maven plugin allows to deploy a WAR/EAR project in a JBOSS instance installed on the machine but does not allow to start JBOSS within maven process as we can do with Glassfish or OPS4J PaxExam - https://github.com/ops4j/org.ops4j.pax.exam2/blob/exam3-milestones/contai.... So this could be interesting to improve existing maven plugin to support embedded mode -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

3
8
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 2012