[JBoss JIRA] Created: (JBCL-169) Support attribute matching from OSGi
by Thomas Diesler (JIRA)
Support attribute matching from OSGi
------------------------------------
Key: JBCL-169
URL: https://jira.jboss.org/browse/JBCL-169
Project: JBoss ClassLoader
Issue Type: Task
Reporter: Thomas Diesler
Assignee: Ales Justin
And another thing that needs to happen is to bubble the attribute matching from OSGi to jboss classloading.
The only reason I originally created OSGi*Capability/Requirement was to implement the attribute matching without modifying
jboss classloading so it could be used in older versions of jboss5. That restriction was broken by other changes a long time ago.
We might never have got into this horrible situation if I hadn't done that.
You should be able to do things like the following in jboss-classloading.xml:
<capabilities>
<package name="foo" attributes="a=b,c=d"/>
</capabilities>
<requirements>
<package name="bar" match-attributes="(vendor=acme)"/>
</requirements>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 11 months
[JBoss JIRA] Created: (JBDEPLOY-225) Create ErrorHandler to DeploymentControllerContext
by Thomas Diesler (JIRA)
Create ErrorHandler to DeploymentControllerContext
---------------------------------------------------
Key: JBDEPLOY-225
URL: https://jira.jboss.org/jira/browse/JBDEPLOY-225
Project: JBoss Deployers
Issue Type: Feature Request
Reporter: Thomas Diesler
The MC Framework incorrectly uninstalls the bundle if there is a failure in bundle.start()
The controller context reached its required stage DESCRIBED after bundle install. A subsequent call to bundle.start() is supposed to transition to stages CLASSLOADER and then INSTALLED, which corresponds to the Bundle states RESOLVED and ACTIVE respectively.
If the transition to INSTALLED fails, the controller context gets undeployed, which causes the bundle to transition to UNINSTALLED.
The desired behaviour is:
* on fail to resolve: remain in state INSTALLED
* on fail to start: remain in state RESOLVED
The proposed solution is to add an ErrorHandler to the DeploymentControllerContext
if it is an OSGi deployment
--
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
14 years, 11 months
[JBoss JIRA] Created: (JBXB-210) Property order cannot be defained on super type
by Thomas Diesler (JIRA)
Property order cannot be defained on super type
-----------------------------------------------
Key: JBXB-210
URL: https://jira.jboss.org/jira/browse/JBXB-210
Project: JBoss XML Binding (JBossXB)
Issue Type: Bug
Affects Versions: JBossXB-2.0.1.GA
Reporter: Thomas Diesler
Caused by: org.jboss.xb.binding.JBossXBRuntimeException: Property order is not specified for type org.jboss.osgi.blueprint.parser.xb.TReference bound to a sequence. Property order can be specified using @XmlType.propOrder or @XmlAccessorOrder. List of properties: referenceListeners dependsOn initialization componentName description any interfaceNames otherAttributes timeout filter availability
at org.jboss.xb.builder.JBossXBNoSchemaBuilder.assertPropOrderNotRequired(JBossXBNoSchemaBuilder.java:1278)
at org.jboss.xb.builder.JBossXBNoSchemaBuilder.generateType(JBossXBNoSchemaBuilder.java:1071)
at org.jboss.xb.builder.JBossXBNoSchemaBuilder.generateBean(JBossXBNoSchemaBuilder.java:779)
at org.jboss.xb.builder.JBossXBNoSchemaBuilder.generateBean(JBossXBNoSchemaBuilder.java:767)
at org.jboss.xb.builder.JBossXBNoSchemaBuilder.generateTypeBinding(JBossXBNoSchemaBuilder.java:523)
at org.jboss.xb.builder.JBossXBNoSchemaBuilder.resolveTypeBinding(JBossXBNoSchemaBuilder.java:482)
at org.jboss.xb.builder.JBossXBNoSchemaBuilder.bindProperty(JBossXBNoSchemaBuilder.java:1684)
@XmlType(name = "Treference", namespace = BlueprintContext.XMLNS_BLUEPRINT)
public class TReference extends TServiceReference
@XmlType(name = "TserviceReference", namespace = BlueprintContext.XMLNS_BLUEPRINT, propOrder = { "description" })
public class TServiceReference extends TComponent
--
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
14 years, 11 months