[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
[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
[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
[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