March 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-9110) Read child resource operation

by Heiko Braun (JIRA)

Read child resource operation ----------------------------- Key: JBAS-9110 URL: https://issues.jboss.org/browse/JBAS-9110 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Heiko Braun Fix For: 7.0.0.Beta2 I realized one drawback with current API. In order to fetch all sever groups, I need to get the list of sever group names first, and for each group request the resource (N+1). In order to reduce the number of requests necessary to fetch resources like server groups, host, etc, I would suggest we add another generic operation that would be similar to read-children-names: :read-children-resource(child-type=<name>) It should return a list of resource representations that are children of <name> -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-9123) Host model server-config should always have "socket-binding-group-name" and "socket-binding-port-offset" attributes

by Brian Stansberry (JIRA)

Host model server-config should always have "socket-binding-group-name" and "socket-binding-port-offset" attributes ------------------------------------------------------------------------------------------------------------------- Key: JBAS-9123 URL: https://issues.jboss.org/browse/JBAS-9123 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Domain Management Affects Versions: 7.0.0.Beta1 Reporter: Brian Stansberry Assignee: Emanuel Muckenhuber Fix For: 7.0.0.Beta2 The "socket-binding-group-name" and "socket-binding-port-offset" attributes are only getting set on the ModelNode for a server-config resource if they were declared in xml. They should be set to "undefined" if not declared. This should be the general rule for all non-metric attributes. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-9082) Incorrect handling of runtime failures in composite operations if rollback is not enabled

by Brian Stansberry (JIRA)

Incorrect handling of runtime failures in composite operations if rollback is not enabled ----------------------------------------------------------------------------------------- Key: JBAS-9082 URL: https://issues.jboss.org/browse/JBAS-9082 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 7.0.0.Beta1 Reporter: Brian Stansberry Fix For: 7.0.0.Beta2 ServerControllerImpl.handleFailures() is delegating to BasicModelController.handleFailures() if rollback-on-runtime-failure is false. That's incorrect as it manipulates the operation result as if the entire op had been discarded, which isn't the case. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-9124) Cant access jnp://192.168.*.*:1099

by Arfat Shaikh (JIRA)

Cant access jnp://192.168.*.*:1099 ---------------------------------- Key: JBAS-9124 URL: https://issues.jboss.org/browse/JBAS-9124 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Web Services Affects Versions: JBossAS-5.1.0.GA Environment: Linux x86_64 GNU/Linux Reporter: Arfat Shaikh Assignee: Alessio Soldano cannot access jnp services from 1 production server(accessed as jnp://192.168.*.*:1099) to test server. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
5
0 / 0

[JBoss JIRA] Created: (JBAS-8950) cli: command history between the sessions

by Alexey Loubyansky (JIRA)

cli: command history between the sessions ----------------------------------------- Key: JBAS-8950 URL: https://issues.jboss.org/browse/JBAS-8950 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky It'd be nice to preserve command history between the cli sessions. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-9109) ls command

by Alexey Loubyansky (JIRA)

ls command ---------- Key: JBAS-9109 URL: https://issues.jboss.org/browse/JBAS-9109 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: CLI Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky It'd be nice to have an ls command that would list the contents of the current node path or the path specified as the argument. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-9114) support --help argument for the commands

by Alexey Loubyansky (JIRA)

support --help argument for the commands ---------------------------------------- Key: JBAS-9114 URL: https://issues.jboss.org/browse/JBAS-9114 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: CLI Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky Fix For: 7.0.0.Beta2 Currently, everything, including all the commands, is described in a single help file. Which is not convenient with the number of commands increasing. It'd be better to keep the general information in the main help file and put command-specific description in separate files that will be printed when the corresponding command is executed with --help argument. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-9059) Cannot build JBoss AS 7 using OpenJDK

by Shelly McGowan (JIRA)

Cannot build JBoss AS 7 using OpenJDK ------------------------------------- Key: JBAS-9059 URL: https://issues.jboss.org/browse/JBAS-9059 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Build System Affects Versions: 7.0.0.Beta1 Reporter: Shelly McGowan Assignee: Andrew Rubinger Fix For: 7.0.0.Beta2 Compilation fails with: ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.1:compile (default-compile) on project jboss-as-arquillian-common: Compilation failure [ERROR] /qa/services/hudson/hudson_workspace/workspace/JBoss-AS-7.0.x-testSuite-openjdk/arquillian/common/src/main/java/org/jboss/as/arquillian/container/JBossASDeploymentPackager.java:[59,16] inconvertible types [ERROR] found : org.jboss.shrinkwrap.api.Archive<capture#470 of ?> [ERROR] required: org.jboss.shrinkwrap.api.spec.WebArchive I've confirmed this is the latest version of OpenJDK: java-1.6.0-openjdk-1.6.0.0-1.20.b17.el5 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

3
9
0 / 0

[JBoss JIRA] Created: (JBAS-5474) @PostLoad -> LazyInitializationException: illegal access to loading collection ond a @OneToMany with FetchType.EAGER

by Stefan Lindner (JIRA)

@PostLoad -> LazyInitializationException: illegal access to loading collection ond a @OneToMany with FetchType.EAGER -------------------------------------------------------------------------------------------------------------------- Key: JBAS-5474 URL: http://jira.jboss.com/jira/browse/JBAS-5474 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB3 Affects Versions: JBossAS-4.2.2.GA Environment: Win XP SP2, Java 1.5.0_15-b04 Reporter: Stefan Lindner Assigned To: Carlo de Wolf Fix For: JBossAS-4.2.3.GA I have a bean with a @OneToMany relation mapping like private List<TherapieeinheitBean> therapieeinheiten; @OneToMany( cascade = {CascadeType.REFRESH}, fetch = FetchType.EAGER, mappedBy="therapiekatalog" ) with FetchType.EAGER and a simnple @PostLoad like @PostLoad public void postLoad() { System.out.println("!!!!!!!!!! postLoad !!!!!!!!!!"); System.out.print("size: " + therapieeinheiten.size()); } When an entity of this bean is loaded JBoss trows org.hibernate.LazyInitializationException: illegal access to loading collection at org.hibernate.collection.AbstractPersistentCollection.initialize(AbstractPersistentCollection.java:341) at org.hibernate.collection.AbstractPersistentCollection.read(AbstractPersistentCollection.java:86) at org.hibernate.collection.PersistentBag.iterator(PersistentBag.java:249) at de.visiodesk.therapiekatalog.TherapiekatalogBean.postLoad(TherapiekatalogBean.java:170) . . . and prints the messages WARN [LoadContexts] fail-safe cleanup (collections) : org.hibernate.engine.loading.CollectionLoadContext@2c8ce9<rs=Ingres-ResultSet[18523]> WARN [CollectionLoadContext] On CollectionLoadContext#cleanup, localLoadingCollectionKeys contained [206] entries afterwards. The PostLoad method should be called after the data was completely loaded. Is there a workaround for this Problem? I found some other ressources on the net where peole had the same problem, but I saw no resolution, no hint, no workaround. -- 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

15 years, 3 months

9
15
0 / 0

[JBoss JIRA] Created: (JBAS-9119) Include version info in LoginScreen

by Heiko Braun (JIRA)

Include version info in LoginScreen ----------------------------------- Key: JBAS-9119 URL: https://issues.jboss.org/browse/JBAS-9119 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Web Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.0.0.Beta2 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
1
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 March 2011