September 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBMETA-361) CLONE - application.xml does not fully support property replacement

by Tom Fonteyne (JIRA)

[ https://issues.jboss.org/browse/JBMETA-361?page=com.atlassian.jira.plugin... ] Tom Fonteyne updated JBMETA-361: -------------------------------- Attachment: PropertyTest.ear > CLONE - application.xml does not fully support property replacement > ------------------------------------------------------------------- > > Key: JBMETA-361 > URL: https://issues.jboss.org/browse/JBMETA-361 > Project: JBoss Metadata > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: ear, web > Affects Versions: 7.0.4 > Reporter: Tom Fonteyne > Priority: Minor > Attachments: PropertyTest.ear > > > Property substitution in application.xml/web.xml does not work -- 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

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBMETA-361) CLONE - application.xml does not fully support property replacement

by Tom Fonteyne (JIRA)

[ https://issues.jboss.org/browse/JBMETA-361?page=com.atlassian.jira.plugin... ] Tom Fonteyne moved JBPAPP-10007 to JBMETA-361: ---------------------------------------------- Project: JBoss Metadata (was: JBoss Enterprise Application Platform) Key: JBMETA-361 (was: JBPAPP-10007) Affects Version/s: 7.0.4 (was: EAP 6.0.0) Component/s: ear web (was: Microcontainer and Deployers) Docs QE Status: (was: NEW) > CLONE - application.xml does not fully support property replacement > ------------------------------------------------------------------- > > Key: JBMETA-361 > URL: https://issues.jboss.org/browse/JBMETA-361 > Project: JBoss Metadata > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: ear, web > Affects Versions: 7.0.4 > Reporter: Tom Fonteyne > Priority: Minor > > Property substitution in application.xml/web.xml does not work -- 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

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBEE-97) See if the jstl dependency on xalan can be refactored out

by Paul Gier (Created) (JIRA)

See if the jstl dependency on xalan can be refactored out --------------------------------------------------------- Key: JBEE-97 URL: https://issues.jboss.org/browse/JBEE-97 Project: JBoss JavaEE Spec APIs Issue Type: Enhancement Components: jboss-jstl-api Affects Versions: JavaEE 6 Spec APIs 3.0.0.Beta1 Reporter: Paul Gier Assignee: Paul Gier Fix For: JavaEE 6 Spec APIs 3.0.0 The JSTL api has a dependency on the xalan fork which is only available in the JBoss repository. If this can be refactored out, then the complete set of dependencies will be available in central. -- 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, 11 months

3
4
0 / 0

[JBoss JIRA] (JBEE-119) jboss-rmi-api_1.0_spec is not declared on BOM

by George Gastaldi (JIRA)

George Gastaldi created JBEE-119: ------------------------------------ Summary: jboss-rmi-api_1.0_spec is not declared on BOM Key: JBEE-119 URL: https://issues.jboss.org/browse/JBEE-119 Project: JBoss JavaEE Spec APIs Issue Type: Bug Components: jboss-rmi-api Affects Versions: JavaEE 6 Spec APIs 3.0.1.Final Reporter: George Gastaldi Assignee: Paul Gier The RMI API is not declared as a dependency on the BOM, just the version. -- 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

13 years, 11 months

2
2
0 / 0

[JBoss JIRA] (AS7-5616) CLI deployment archive problem containing jdbc driver and datasource

by Stefano Maestri (JIRA)

Stefano Maestri created AS7-5616: ------------------------------------ Summary: CLI deployment archive problem containing jdbc driver and datasource Key: AS7-5616 URL: https://issues.jboss.org/browse/AS7-5616 Project: Application Server 7 Issue Type: Bug Components: JCA Affects Versions: 7.1.3.Final (EAP) Reporter: Stefano Maestri Assignee: Stefano Maestri Fix For: 7.1.4.Final (EAP) Hi, First of all, the new CLI deployment archive feature of 7.2.x solves a lot of problems for my migration from 5.1! I have 20+ standalone servers that now can be configured at deploy-time. Thanks! Playing with the latest nightly build from yesterday, my CLI archive consists of the following; - mywebapp.war - postgresql-9.1-902.jdbc4.jar - deploy.scr - undeploy.scr deploy.scr has the following lines; deploy postgresql-9.1-902.jdbc4.jar data-source add --name=MyDS --jndi-name=java:jboss/datasources/MyDS --driver-name=postgresql-9.1-902.jdbc4.jar --connection-url=[not important for this example] deploy mywebapp.war That is, install my jdbc driver, create the data-source, and finally deploy my webapp which uses the data-source. This does not work :-( The error is; [standalone@localhost:9999 /] deploy mycliarchive.cli ...... Failed to execute archive script: {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => "JBAS010468: Driver named \"postgresql-9.1-902.jdbc4.jar\" is not installed."}} -- 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

13 years, 11 months

3
4
0 / 0

[JBoss JIRA] (AS7-5600) File paths are not appended correctly

by Nicholas DiPiazza (JIRA)

Nicholas DiPiazza created AS7-5600: -------------------------------------- Summary: File paths are not appended correctly Key: AS7-5600 URL: https://issues.jboss.org/browse/AS7-5600 Project: Application Server 7 Issue Type: Bug Components: JMS Affects Versions: 7.2.0.Alpha1 Environment: I tested this on Windows XP only so far. Reporter: Nicholas DiPiazza Assignee: Jeff Mesnil Priority: Blocker I am specifying a journal-directory as an absolute path. <journal-directory path="C:/JBoss/jboss-journal" /> This worked on WJBoss 7.1.1.Final which uses HornetQ 2.2.13. I moved to the latest snapshot from Hudson which is currently Ijboss-as-7.2.0.Alpha1. It will append the path to the JBoss data directory. Thus I get this error: Cannot open file "C:\JBoss\server-backup\jboss-as-7.2.0.Alpha1-SNAPSHOT\standalone\data\C:\JBoss\jboss-journal\server.lock" -- 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

13 years, 11 months

4
7
0 / 0

[JBoss JIRA] (AS7-5614) Reconfigure of JavaMail service on-the-fly

by Vadim Gusev (JIRA)

Vadim Gusev created AS7-5614: -------------------------------- Summary: Reconfigure of JavaMail service on-the-fly Key: AS7-5614 URL: https://issues.jboss.org/browse/AS7-5614 Project: Application Server 7 Issue Type: Bug Components: Mail Affects Versions: 7.1.1.Final Reporter: Vadim Gusev Assignee: Tomaz Cerar Since JavaMail implemented on Jboss AS7 we can't reconfigure JavaMail service on-the-fly. We always should restart the server to apply new configuration. -- 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

13 years, 11 months

2
2
0 / 0

[JBoss JIRA] (AS7-5615) Web service methods cannot be static & final - implement deployment check for that

by Richard Opalka (JIRA)

Richard Opalka created AS7-5615: ----------------------------------- Summary: Web service methods cannot be static & final - implement deployment check for that Key: AS7-5615 URL: https://issues.jboss.org/browse/AS7-5615 Project: Application Server 7 Issue Type: Feature Request Components: Web Services Reporter: Richard Opalka Assignee: Richard Opalka We already check that JAXWS webservice endpoint class cannot be final. We also need to implement (reflection based) check that all webservice methods are not final and static. The deployment should fail if such method is detected. -- 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

13 years, 11 months

1
1
0 / 0

[JBoss JIRA] (JGRP-1519) RELAY2: relaying of multicasts between multiple clusters leads to cycles

by Bela Ban (JIRA)

Bela Ban created JGRP-1519: ------------------------------ Summary: RELAY2: relaying of multicasts between multiple clusters leads to cycles Key: JGRP-1519 URL: https://issues.jboss.org/browse/JGRP-1519 Project: JGroups Issue Type: Bug Reporter: Bela Ban Assignee: Bela Ban Fix For: 3.2 - Run 2 Draw instances for LON.xml, SFO.xml and NYC.xml (RELAY2.relay_multicasts needs to be enabled) - Draw in any instance: this leads to the multicast being relayed forever - Note that these cycles don't occur with 2 clusters -- 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

13 years, 11 months

1
3
0 / 0

[JBoss JIRA] (AS7-5601) <pooled-connection-factory> should default reconnectAttempts to "-1"

by Justin Bertram (JIRA)

Justin Bertram created AS7-5601: ----------------------------------- Summary: <pooled-connection-factory> should default reconnectAttempts to "-1" Key: AS7-5601 URL: https://issues.jboss.org/browse/AS7-5601 Project: Application Server 7 Issue Type: Bug Components: JMS Reporter: Justin Bertram Assignee: Jeff Mesnil When a <pooled-connection-factory> is deployed programmatically the messaging subsystem initializes reconnectAttempts to 0 which breaks the code in the HornetQ JCA RA (see org.hornetq.ra.HornetQResourceAdapter#setParams) and keeps it from overriding the reconnectAttempts and setting it to -1. This leads to unexpected behavior for MDBs connecting to a remote provider. -- 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

13 years, 11 months

2
2
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 September 2012