[JBoss JIRA] (JGRP-2443) Merge ObjectMessage and ObjectMessageSerializable
by Bela Ban (Jira)
[ https://issues.redhat.com/browse/JGRP-2443?page=com.atlassian.jira.plugin... ]
Bela Ban resolved JGRP-2443.
----------------------------
Resolution: Done
> Merge ObjectMessage and ObjectMessageSerializable
> -------------------------------------------------
>
> Key: JGRP-2443
> URL: https://issues.redhat.com/browse/JGRP-2443
> Project: JGroups
> Issue Type: Enhancement
> Reporter: Bela Ban
> Assignee: Bela Ban
> Priority: Major
> Fix For: 5.0
>
>
> {{ObjectMessage}} has an {{object}} as payload, {{ObjectMessageSerializable}} inherits this and adds {{serialized_obj}}.
> The former has ~32 bytes in memory, the latter 40.
> The goal is not to increase the size of {{ObjectMessage}} to 40.
> Solution:
> * Create an ObjectWrapper class, taking an object and a serialized_version
> * This is used in the merged {{ObjectMessage}} class (size is still ~32 bytes)
> * When we have a SizeStreamable object, we set it as payload, otherwise we create an {{ObjectWrapper}} and set it as object.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (WFLY-13041) Upgrade to Galleon 4.2.4
by Jean Francois Denise (Jira)
Jean Francois Denise created WFLY-13041:
-------------------------------------------
Summary: Upgrade to Galleon 4.2.4
Key: WFLY-13041
URL: https://issues.redhat.com/browse/WFLY-13041
Project: WildFly
Issue Type: Component Upgrade
Components: Build System
Reporter: Jean Francois Denise
Assignee: Jean Francois Denise
Both galleon-plugins and galleon.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (WFCORE-4823) Upgrade to Galleon 4.2.4
by Jean Francois Denise (Jira)
Jean Francois Denise created WFCORE-4823:
--------------------------------------------
Summary: Upgrade to Galleon 4.2.4
Key: WFCORE-4823
URL: https://issues.redhat.com/browse/WFCORE-4823
Project: WildFly Core
Issue Type: Component Upgrade
Components: Build System
Reporter: Jean Francois Denise
Assignee: Jean Francois Denise
Both galleon-plugins and galleon.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (WFLY-13040) Global directory user experience improvements
by Martin Svehla (Jira)
Martin Svehla created WFLY-13040:
------------------------------------
Summary: Global directory user experience improvements
Key: WFLY-13040
URL: https://issues.redhat.com/browse/WFLY-13040
Project: WildFly
Issue Type: Feature Request
Components: EE, Management
Reporter: Martin Svehla
Assignee: Brian Stansberry
This is follow up issue for https://issues.redhat.com/browse/WFLY-1160.
During development there were discussed few ways of improving user experience of global directory that weren't implemented as part of the original feature:
1. If some class from global directory throws an exception, it would be helpful is user was informed which jar contains this class.
2. If global directory contains corrupted jar file (e.g. text file which was renamed to .jar), deployment won't be successfully deployed. Server logs contains information that zip file could not be opened. Cli only prints out that deployment is missing dependencies - which isn't necessarily true.
It's possible that deployment isn't missing any dependencies - in this case, it would be better just to display a warning that there is a corrupted jar in global directory.
3. It would be good if users could specify dependencies for their libraries, something like this:
{code:java}
/subsystem=ee/global-directory=my-common-libs:add(path=lib, relative-to=jboss.home.dir, dependencies=[{name=org.hibernate.something,export=true,import=false}])
{code}
4. If jar contains class that has same name and package as some java ee class, for example custom javax.ws.rs.client.Client, it can cause error during execution:
{code:java}
org.jboss.resteasy.spi.UnhandledException: java.lang.LinkageError: loader constraint violation: loader (instance of org/jboss/modules/ModuleClassLoader) previously initiated loading for a different type with name "javax/ws/rs/client/Client"
{code}
It would be better if user was informed about duplicity during deployment.
5. If global directory has following hierarchy:
a/a.1.jar
---- A.class
b/a.2.jar
---- A.class
---- B.class
and class B uses A's feature that is only available in a.2.jar version of A.class then
it fails during execution when class B tries to access this feature of class A (because class A is loaded from a.1.jar and A in a.2.jar is ignored).
As before, it would be better if user was informed about presence of duplicate class A in global directory during deployment.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months