July 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBWEB-65) context.xml is ignored.

by Nicolas Leroux (JIRA)

context.xml is ignored. ----------------------- Key: JBWEB-65 URL: http://jira.jboss.com/jira/browse/JBWEB-65 Project: JBoss Web Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBoss Web Standalone 4.0.4 RC1 Reporter: Nicolas Leroux Assigned To: Mladen Turk The context.xml file is ignored by jboss. It's thus impossible to setup the docRoot property. I followed the wiki: http://wiki.jboss.org/wiki/Wiki.jsp?page=UsingContextDotXML without any success (The context.xml is in my META-INF). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-4282) Can't create a root context web app

by Stan Silvert (JIRA)

Can't create a root context web app ----------------------------------- Key: JBAS-4282 URL: http://jira.jboss.com/jira/browse/JBAS-4282 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web (Tomcat) service Affects Versions: JBossAS-5.0.0.Beta2 Reporter: Stan Silvert Assigned To: Remy Maucherat I am unable to deploy a web app as root context using the instructions here: http://wiki.jboss.org/wiki/Wiki.jsp?page=SetupARootContextApp One thing that is unclear is if ROOT.war "must" be removed from /deploy. In 4.2, root context web apps do not require removal of ROOT.war. IMHO, this is how it should work. If you deploy a WAR as the root context, it should simply override whatever was there before. If ROOT.war is removed, 5.0 will allow a root context web app as long as it is deployed from an EAR and specified as such in application.xml. Otherwise, it will fail. If you choose to deploy a stand-alone WAR and specify it as root context using jboss-web.xml, it will always fail - regardless of whether or not you remove ROOT.war. I have committed a test for root deployment in both 4.2 and 5.0. The test passes in 4.2, but not in 5.0. You can run it with: build one-test -Dtest=org.jboss.test.web.test.RootContextUnitTestCase -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 2 months

3
3
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-307) Upgrade javassist to 3.8.0.GA

by Kabir Khan (JIRA)

Upgrade javassist to 3.8.0.GA ----------------------------- Key: JBMICROCONT-307 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-307 Project: JBoss MicroContainer Issue Type: Thirdparty Change Reporter: Kabir Khan Assigned To: Kabir Khan Fix For: JBossMC.2.0.0.CR1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 2 months

1
4
0 / 0

[JBoss JIRA] Updated: (JBAOP-209) Change any usage of java.rmi.MarshalledObject with JBoss Serialization's equivalent.

by Kabir Khan (JIRA)

[ https://jira.jboss.org/jira/browse/JBAOP-209?page=com.atlassian.jira.plug... ] Kabir Khan updated JBAOP-209: ----------------------------- Fix Version/s: 2.0.0.GA (was: 2.0.0.CR15) > Change any usage of java.rmi.MarshalledObject with JBoss Serialization's equivalent. > ------------------------------------------------------------------------------------ > > Key: JBAOP-209 > URL: https://jira.jboss.org/jira/browse/JBAOP-209 > Project: JBoss AOP > Issue Type: Feature Request > Affects Versions: 1.3.5 > Reporter: Bill Burke > Assignee: Bill Burke > Priority: Minor > Fix For: 2.0.0.GA > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAOP-43) ThreadMetadata serialization

by Kabir Khan (JIRA)

[ https://jira.jboss.org/jira/browse/JBAOP-43?page=com.atlassian.jira.plugi... ] Kabir Khan updated JBAOP-43: ---------------------------- Fix Version/s: 2.0.0.GA (was: 2.0.0.CR15) > ThreadMetadata serialization > ---------------------------- > > Key: JBAOP-43 > URL: https://jira.jboss.org/jira/browse/JBAOP-43 > Project: JBoss AOP > Issue Type: Feature Request > Affects Versions: 2.0.0.alpha1 > Reporter: Bill Burke > Assignee: Bill Burke > Priority: Minor > Fix For: 2.0.0.GA > > > ThreadMetadata should be serialized separately and merged with remote ThreadMetaData. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAOP-6) Compile time reweaving

by Kabir Khan (JIRA)

[ https://jira.jboss.org/jira/browse/JBAOP-6?page=com.atlassian.jira.plugin... ] Kabir Khan updated JBAOP-6: --------------------------- Fix Version/s: 2.0.0.GA (was: 2.0.0.CR15) > Compile time reweaving > ---------------------- > > Key: JBAOP-6 > URL: https://jira.jboss.org/jira/browse/JBAOP-6 > Project: JBoss AOP > Issue Type: Feature Request > Affects Versions: 2.0.0.alpha1 > Reporter: Bill Burke > Assignee: Bill Burke > Priority: Minor > Fix For: 2.0.0.GA > > > Support for compile time reweaving. Currently AOPC ignores a class that implements Advised -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAOP-69) InvocationResponse should catch/wrap exceptions

by Kabir Khan (JIRA)

[ https://jira.jboss.org/jira/browse/JBAOP-69?page=com.atlassian.jira.plugi... ] Kabir Khan updated JBAOP-69: ---------------------------- Fix Version/s: 2.0.0.GA (was: 2.0.0.CR15) > InvocationResponse should catch/wrap exceptions > ----------------------------------------------- > > Key: JBAOP-69 > URL: https://jira.jboss.org/jira/browse/JBAOP-69 > Project: JBoss AOP > Issue Type: Feature Request > Affects Versions: 2.0.0.alpha1 > Reporter: Bill Burke > Assignee: Bill Burke > Priority: Minor > Fix For: 2.0.0.GA > > > InvocationResponse in dynamicInvoke should catch all thrown exceptions and stuff them into InvocationResponse. > The "client" of dynamicInvoke should look in IR to see if an exception is in there and rethrow it. It should also set the response attachments of the invocation as well. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-5784) Upgrade JBoss JAXR to 1.2.0.SP2

by Richard Opalka (JIRA)

Upgrade JBoss JAXR to 1.2.0.SP2 ------------------------------- Key: JBAS-5784 URL: https://jira.jboss.org/jira/browse/JBAS-5784 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Richard Opalka Assignee: Richard Opalka -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-1678) BRMS: bad formatting when adding a global to a package

by Jaroslaw Kijanowski (JIRA)

BRMS: bad formatting when adding a global to a package ------------------------------------------------------ Key: JBRULES-1678 URL: http://jira.jboss.com/jira/browse/JBRULES-1678 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-brms Reporter: Jaroslaw Kijanowski Assigned To: Mark Proctor Fix For: 5.0.0.M1 When I add a second global it gets attached to the previous statement, so there's no new line/space (see attached screen) and you have to fix this manually going to the Advanced view -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 2 months

2
5
0 / 0

[JBoss JIRA] Created: (JBAOP-616) Move interceptor chain creation logic (pointcutResolved) to AdviceBinding

by Flavia Rainone (JIRA)

Move interceptor chain creation logic (pointcutResolved) to AdviceBinding ------------------------------------------------------------------------- Key: JBAOP-616 URL: https://jira.jboss.org/jira/browse/JBAOP-616 Project: JBoss AOP Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Flavia Rainone Assignee: Flavia Rainone AdviceBinding contains all interceptor factories and, thus, should be responsible for invoking the factories to create interceptors, instead of allowing access to its internal data to have others perform this. This task includes the following steps: - the creation of an InterceptorChainFactory, that encapsulates completely the logic of creation of interceptor chains, creating CflowInterceptors, GenertedAdvisorInterceptors, plain interceptors whenever needed. - the internal fields of the AdviceBinding will be replaced by this factory (except the pointcut). Ideally, this factory will not be accessed by any other part of the code. - perform retrieval of the appropriate interceptor chain factory accordingly to the instrumentation mode. - add a self removal operation to AdviceBinding. This operation will remove all created interceptors from their chains. Having this structure (ie., logic of chain creation moved to inside AdviceBinding) is the only way that allows the efficient removal of bindings, without performing any matching or search. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 2 months

2
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2008