[JBoss JIRA] Created: (JBSER-112) Adjust JBossSerialization to support JBossMarshalling
by Ron Sigal (JIRA)
Adjust JBossSerialization to support JBossMarshalling
-----------------------------------------------------
Key: JBSER-112
URL: https://jira.jboss.org/jira/browse/JBSER-112
Project: JBoss Serialization
Issue Type: Feature Request
Affects Versions: 1.0.3 GA
Reporter: Ron Sigal
Assignee: Ron Sigal
Fix For: 1.1.0 Beta
The JBossMarshalling project presents a unitied API for marshalling and unmarshalling objects. It supports a number of pluggable facilities, including object and class resolvers, externalizers, and so forth. There is a native implementation (River) and an implementation that is compatible with standard Java serialization. A number of changes are necessary to support an implementation this is based on, and compatible with, JBossSerialization.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 4 months
[JBoss JIRA] Created: (JBRULES-1539) Support enum fields as drop-downs in BRMS
by Harlan Iverson (JIRA)
Support enum fields as drop-downs in BRMS
-----------------------------------------
Key: JBRULES-1539
URL: http://jira.jboss.com/jira/browse/JBRULES-1539
Project: JBoss Drools
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: drools-brms
Environment: n/a
Reporter: Harlan Iverson
Assigned To: Mark Proctor
Priority: Optional
It would be nice if enum [real Java 5+] fields were first class citizens, and the BRMS UI had the same functionality as the BRMS-defined enums described in JBRULES-1090.
For example, if Driver.locationRiskProfile in the insurance example were changed to a RiskLevel enum, the BRMS would use reflection (or similar) to create a drop-down box based on the RiskLevel members.
Another optional extension of that would be the ability to assign displayed text for enums in the same way that JBRULES-1090 describes:
RiskLevel : ['LOW=Low Risk', 'MED=Medium Risk']
where LOW and MED would correspond to enum values.
--
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
17 years, 4 months
[JBoss JIRA] Created: (JBXB-192) Incorrect particle is logged when trace is enabled
by Alexey Loubyansky (JIRA)
Incorrect particle is logged when trace is enabled
--------------------------------------------------
Key: JBXB-192
URL: https://jira.jboss.org/jira/browse/JBXB-192
Project: JBoss XML Binding (JBossXB)
Issue Type: Bug
Affects Versions: JBossXB-2.0.1.Beta2
Reporter: Alexey Loubyansky
Assignee: Alexey Loubyansky
Fix For: JBossXB-2.0.1.Beta3
In SundayContentHandler in the pop() method it should be cursor.getParticle() instead of cursor.getCurrentParticle().
private StackItem pop()
{
StackItem item = stack.pop();
if(trace)
{
if(item.cursor == null)
log.trace("poped " + ((ElementBinding)item.particle.getTerm()).getQName() + "=" + item.particle);
else
log.trace("poped " + item.cursor.getCurrentParticle().getTerm());
}
return item;
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 4 months