[JBoss JIRA] Created: (JBMICROCONT-130) Array part of the Javassist reflection implementation is broken
by Adrian Brock (JIRA)
Array part of the Javassist reflection implementation is broken
---------------------------------------------------------------
Key: JBMICROCONT-130
URL: http://jira.jboss.com/jira/browse/JBMICROCONT-130
Project: JBoss MicroContainer
Issue Type: Task
Components: BeanInfo
Affects Versions: JBossMC_2_0_0 Beta
Reporter: Adrian Brock
Javassist is returning wrong values for interfaces of arrays and modifiers of array classes.
These errors have been suppressed in org.jboss.test.classinfo.test.JavassistArrayUnitTestCase
by subclassling the tests to do nothing:
protected void assertInterfaces(Class<?> clazz, ClassInfo classInfo) throws Throwable
{
// TODO this is broken for javassist
}
protected void assertModifiers(Class<?> clazz, ClassInfo classInfo) throws Throwable
{
// TODO this is broken for javassist
}
This needs fixing in javassist
--
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
14 years, 7 months
[JBoss JIRA] Created: (JBAS-3753) HAParititonImpl implements org.jgroups.ChannelListener
by Brian Stansberry (JIRA)
HAParititonImpl implements org.jgroups.ChannelListener
------------------------------------------------------
Key: JBAS-3753
URL: http://jira.jboss.com/jira/browse/JBAS-3753
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Clustering
Affects Versions: JBossAS-4.0.4.GA, JBossAS-3.2.8.SP1
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Fix For: JBossAS-5.0.1.CR1
Currently if a JChannel is shunned and disconnects, higher level services are unaware of this and can't take any remedial action.
We need to do something like implement ChannelListener so an HAPartition is aware when the events on the underlying channel occur. Then devise a scheme to propagate some of the events to user code. Preferably this will follow as much as possible the existing notification scheme; i.e. pass a new view to HAMembershipListener impls that doesn't include the current node.
--
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
14 years, 7 months
[JBoss JIRA] Created: (JBCLUSTER-139) Create a general purpose group RPC API
by Brian Stansberry (JIRA)
Create a general purpose group RPC API
--------------------------------------
Key: JBCLUSTER-139
URL: http://jira.jboss.com/jira/browse/JBCLUSTER-139
Project: JBoss Clustering
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Fix For: Q3Y6
Abstraction on top of JGroups RpcDispatcher.
Start with HAPartition as a base, but minus DRM and DS. Consider what Messaging has done as well as JBCACHE-311.
Consider separating the group membership API from the RPC API. RPC API would probably be a subinterface of the group membership one, as group RPC implies being aware of who the group is.
This is lower priority, as, except for AS, its an internal implementation detail that can be changed. But, AS exposes HAPartition as an API for end-user code.
--
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
14 years, 8 months
[JBoss JIRA] Created: (JBAS-4193) Validation requirement should come from the model factory
by Scott M Stark (JIRA)
Validation requirement should come from the model factory
---------------------------------------------------------
Key: JBAS-4193
URL: http://jira.jboss.com/jira/browse/JBAS-4193
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Deployment services, XML services
Reporter: Scott M Stark
Assigned To: Scott M Stark
Fix For: JBossAS-5.0.0.Beta2
A regression relative to how we parse application.xml without validation jbossas4.2 and earlier is showing up in placeholder application.xml deployments like:
<!DOCTYPE application PUBLIC
"-//Sun Microsystems, Inc.//DTD J2EE Application 1.3//EN"
"http://java.sun.com/dtd/application_1_3.dtd">
<application>
<display-name>Resource Loading Ear</display-name>
</application>
This fails because this dtd requires at least one module as well:
Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: vfsfil
e:/C:/home/svn/JBossHead/jboss-head/testsuite/output/lib/unpacked/loadingresourc
e2.ear/META-INF/application.xml@7,15
at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBPars
er.java:173)
at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java
:180)
at org.jboss.deployers.plugins.deployers.helpers.ObjectModelFactoryDeplo
yer.parse(ObjectModelFactoryDeployer.java:83)
... 70 more
Caused by: org.xml.sax.SAXException: The content of element type "application" i
s incomplete, it must match "(icon?,display-name,description?,module+,security-r
ole*)". @ vfsfile:/C:/home/svn/JBossHead/jboss-head/testsuite/output/lib/unpacke
d/loadingresource2.ear/META-INF/application.xml[7,15]
at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$MetaDataErrorHandler
.error(SaxJBossXBParser.java:406)
at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.dtd.XMLDTDValidator.handleEndElement(Unknown S
To allow for similar behavior, we need to allow the ObjectModelFactory used by the deployer to indicate whether validation is needed.
--
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
14 years, 8 months