September 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-4833) replace filter does not work

by James Perkins (JIRA)

James Perkins created AS7-4833: ---------------------------------- Summary: replace filter does not work Key: AS7-4833 URL: https://issues.jboss.org/browse/AS7-4833 Project: Application Server 7 Issue Type: Bug Components: Logging Reporter: James Perkins Assignee: James Perkins Fix For: 7.1.3.Final (EAP), 7.2.0.Alpha1 {{<replace/>}} filters do not work. The parser is using the incorrect node to find the attributes. -- 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, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (JBWEB-193) SeLinux policy for JBoss Enterprise Web Server

by Sam Weaver (JIRA)

SeLinux policy for JBoss Enterprise Web Server ---------------------------------------------- Key: JBWEB-193 URL: https://issues.jboss.org/browse/JBWEB-193 Project: JBoss Web Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Sam Weaver Assignee: Remy Maucherat Priority: Minor SeLinux causes JBoss EWS to stop working, or randomly fail to start. Therefore requesting an SeLinux policy for JBoss EWS. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
1
0 / 0

[JBoss JIRA] (JBWEB-242) Memory Leak in PerThreadTagHandlerPool

by Martin Ball (JIRA)

13 years, 9 months

3
4
0 / 0

[JBoss JIRA] (AS7-4265) cli command to add/remove AS modules

by Alexey Loubyansky (JIRA)

Alexey Loubyansky created AS7-4265: -------------------------------------- Summary: cli command to add/remove AS modules Key: AS7-4265 URL: https://issues.jboss.org/browse/AS7-4265 Project: Application Server 7 Issue Type: Task Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky Fix For: 7.1.2.Final I think it'd be useful to have a command to add modules to the AS which given the jars, dependencies, etc would generate the structure in the modules dir, copy the jars and generate the xml. -- 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, 9 months

2
3
0 / 0

[JBoss JIRA] (HIBERNATE-139) [HHH-7629] Initialize PersistentCollection with fetchType LAZY returns NPE

by Ricardo Martinelli Oliveira (JIRA)

Ricardo Martinelli Oliveira created HIBERNATE-139: ----------------------------------------------------- Summary: [HHH-7629] Initialize PersistentCollection with fetchType LAZY returns NPE Key: HIBERNATE-139 URL: https://issues.jboss.org/browse/HIBERNATE-139 Project: Hibernate Integration Issue Type: Support Patch Reporter: Ricardo Martinelli Oliveira Assignee: Steve Ebersole @JoinTable(name = "JOIN_TABLE", joinColumns = { @JoinColumn(name = "JOIN_TABLE_ID", referencedColumnName = "ID") }, inverseJoinColumns = { @JoinColumn(name = "ENTITY_ID", referencedColumnName = "ID") }) @ManyToMany(fetch = FetchType.LAZY) private Set<JoinTable> aProperty; When fetching this entity, and after initialize, I get all the valid attribute values but the aProperty is defined as PersistenceCollection. This collection is not intialized yet. When I initialize this collection as follow: (PersistentCollection) entity).forceInitialization(); Or Hibernate.initialize(entity); I got NullPointerException: Caused by: java.lang.NullPointerException at org.hibernate.engine.internal.StatefulPersistenceContext.getLoadedCollectionOwnerOrNull(StatefulPersistenceContext.java:790) at org.hibernate.event.spi.AbstractCollectionEvent.getLoadedOwnerOrNull(AbstractCollectionEvent.java:75) at org.hibernate.event.spi.InitializeCollectionEvent.<init>(InitializeCollectionEvent.java:36) at org.hibernate.internal.SessionImpl.initializeCollection(SessionImpl.java:1803) at org.hibernate.collection.internal.AbstractPersistentCollection.forceInitialization(AbstractPersistentCollection.java:489) at org.hibernate.Hibernate.initialize(Hibernate.java:77) When I check source code of class org.hibernate.engine.internal.StatefulPersistenceContext.getLoadedCollectionOwnerOrNull(StatefulPersistenceContext.java:790) CollectionEntry ce = getCollectionEntry( collection ); 790 if ( ce.getLoadedPersister() == null ) { 791 return null; // early exit... 792 } Looks like the CollectionEntry ce is null. This collection entry is fetched from collectionEntries.get(coll); // Identity map of CollectionEntry instances, by the collection wrapper 121 private IdentityMap<PersistentCollection, CollectionEntry> collectionEntries; I checked Jboss docs, it mentioned the way to initilialize the collection is as I have done above. http://docs.jboss.org/hibernate/orm/3.3/reference/en/html/performance.htm... -- 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, 9 months

2
2
0 / 0

[JBoss JIRA] (AS7-2371) Web Console: In the past the JMX console could flush queues/topics, etc, can that be added to the console

by Jim Tyrrell (Created) (JIRA)

Web Console: In the past the JMX console could flush queues/topics, etc, can that be added to the console ---------------------------------------------------------------------------------------------------------- Key: AS7-2371 URL: https://issues.jboss.org/browse/AS7-2371 Project: Application Server 7 Issue Type: Feature Request Components: Console Reporter: Jim Tyrrell Assignee: Heiko Braun -- 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, 9 months

3
4
0 / 0

[JBoss JIRA] (AS7-5101) Support unmanaged deployments in the console

by Brian Stansberry (JIRA)

Brian Stansberry created AS7-5101: ------------------------------------- Summary: Support unmanaged deployments in the console Key: AS7-5101 URL: https://issues.jboss.org/browse/AS7-5101 Project: Application Server 7 Issue Type: Feature Request Components: Console Reporter: Brian Stansberry Assignee: Heiko Braun The AS supports the notion of "unmanaged" deployments, where, rather than uploading the deployment content to the server, which then serves it from its internal content repo, instead the filesystem path to the content is provided and the content is served directly from that location. This mechanism is particularly helpful with exploded deployments; it's what the filesystem deployment scanner uses when it detects an exploded deployment. The CLI supports this via the --unmanaged flag that can be passed to the "deploy" command. The console should expose this functionality as well. If this were used in a managed domain, it's the responsibility of the user to ensure that the content is available at the provided path on all relevant hosts in the domain. EAP itself takes no responsibility for managing that content. -- 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, 9 months

2
3
0 / 0

[JBoss JIRA] (AS7-5638) Verify interaction with filesystem deployments

by Heiko Braun (JIRA)

Heiko Braun created AS7-5638: -------------------------------- Summary: Verify interaction with filesystem deployments Key: AS7-5638 URL: https://issues.jboss.org/browse/AS7-5638 Project: Application Server 7 Issue Type: Feature Request Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.2.0.CR1 It seems possible to modify filesystem deployments from within the console. This should not be the case -- 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, 9 months

1
2
0 / 0

[JBoss JIRA] (AS7-2334) Web Console: Eager clustering checkbox enabled/disabled

by Jim Tyrrell (Created) (JIRA)

Web Console: Eager clustering checkbox enabled/disabled ------------------------------------------------------- Key: AS7-2334 URL: https://issues.jboss.org/browse/AS7-2334 Project: Application Server 7 Issue Type: Feature Request Components: Console Reporter: Jim Tyrrell Assignee: Heiko Braun Out of the box this probably should be checked by default so you get the typical in the past JGroups messages in the logging showing that clustering between two instances has occurred. -- 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, 9 months

6
7
0 / 0

[JBoss JIRA] (AS7-4344) Cannot execute deploy operation from within activation

by Thomas Diesler (JIRA)

Thomas Diesler created AS7-4344: ----------------------------------- Summary: Cannot execute deploy operation from within activation Key: AS7-4344 URL: https://issues.jboss.org/browse/AS7-4344 Project: Application Server 7 Issue Type: Sub-task Components: OSGi, Server Reporter: Thomas Diesler -- 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, 9 months

1
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