July 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBDEPLOY-234) Comprehensive classloading framework documentation

by Thomas Diesler (JIRA)

Comprehensive classloading framework documentation -------------------------------------------------- Key: JBDEPLOY-234 URL: https://jira.jboss.org/jira/browse/JBDEPLOY-234 Project: JBoss Deployers Issue Type: Task Components: general Reporter: Thomas Diesler Assignee: Ales Justin Fix For: JBDEPLOY-2.2.x Please provide comprehensive documentation for the deployer framework. It should cover the individual types of deployers, deployment states, dependency items, modules, etc. Improved javadoc is also covered by this issue. For trunk it is possible to publish the javadoc in the hudson QA environment. -- 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

13 years, 5 months

3
6
0 / 0

[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

13 years, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (JBXB-208) Provide an annotation based tutorial for JBossXB

by Thomas Diesler (JIRA)

Provide an annotation based tutorial for JBossXB ------------------------------------------------ Key: JBXB-208 URL: https://jira.jboss.org/jira/browse/JBXB-208 Project: JBoss XML Binding (JBossXB) Issue Type: Bug Reporter: Thomas Diesler You've specified the namespace using JBossXmlSchema annotation. Which is correct. You should still add namespace element to the XmlRootElement annotation, which is a bit confusing having JBossXmlSchema. You don't have to do that XmlElement annotations. Unfortunately, we don't have JAXB tutorial for JBossXB. But you can find one for JAXB on Sun's web-site and use javadoc. For examples you can see tests in XB http://anonsvn.jboss.org/repos/common/jbossxb/trunk/src/test/java/org/jbo... -- 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

13 years, 5 months

1
1
0 / 0

[JBoss JIRA] Resolved: (BPEL-85) Docu on the purpose of BPEL

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/BPEL-85?page=com.atlassian.jira.plugin.sy... ] Thomas Diesler resolved BPEL-85. -------------------------------- Resolution: Out of Date Out of Date > Docu on the purpose of BPEL > --------------------------- > > Key: BPEL-85 > URL: https://issues.jboss.org/browse/BPEL-85 > Project: jBPM BPEL > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Documents > Affects Versions: jBPM BPEL 1.0 alpha 4 > Reporter: Thomas Diesler > Assignee: Alejandro Guizar > Fix For: jBPM BPEL 1.2 GA > > > Please expand the user documentation to a section about the purpose of BPEL. It should show a not so trivial use case that illustrates (with pictures) why I should care about BPEL -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (JBDEPLOY-214) Add listener hooks for deployment processing

by Thomas Diesler (JIRA)

Add listener hooks for deployment processing -------------------------------------------- Key: JBDEPLOY-214 URL: https://jira.jboss.org/jira/browse/JBDEPLOY-214 Project: JBoss Deployers Issue Type: Feature Request Reporter: Thomas Diesler Currently JBossOSGi wraps the Deployers to do some post processing public void process(List<DeploymentContext> deploy, List<DeploymentContext> undeploy) { // Delegate to the original deployers deployers.process(deploy, undeploy); // OSGi bundles resolve phase afterDeployersProcess(deploy, undeploy); } Perhaps this should be supported by the Deployers natively -- 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

13 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (JBCL-168) Add support for getModule() on Requirement/Capability

by Thomas Diesler (JIRA)

Add support for getModule() on Requirement/Capability ----------------------------------------------------- Key: JBCL-168 URL: https://jira.jboss.org/browse/JBCL-168 Project: JBoss ClassLoader Issue Type: Task Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: JBossCL.2.2.0.Beta1 An alterante would be adding a mixin index to Capability so that you can get the Module, with AbstractCapability implementing it instead for this. e.g. public interface CapabilityModule { Module.getModule(); } if (capability instanceof CapabilityModule) { resolved = ((CapabilityModule) capability).getModule().isResovled(): } -- 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

13 years, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (JBFORUMS-122) Links should be recognized

by Thomas Diesler (JIRA)

Links should be recognized -------------------------- Key: JBFORUMS-122 URL: http://jira.jboss.com/jira/browse/JBFORUMS-122 Project: JBoss Forums Issue Type: Feature Request Components: Forum Enhancements Reporter: Thomas Diesler Assigned To: Sohil Shah Instead of [url]http://jira.jboss.com/jira/secure/CreateIssue.jspa[/url] I like to simply use http://jira.jboss.com/jira/secure/CreateIssue.jspa There are a lot of user provided links that I cannot click on. -- 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

13 years, 5 months

4
3
0 / 0

[JBoss JIRA] Created: (JBAS-7910) jmx-console does not display CompositeData properly

by Thomas Diesler (JIRA)

jmx-console does not display CompositeData properly --------------------------------------------------- Key: JBAS-7910 URL: https://jira.jboss.org/jira/browse/JBAS-7910 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Thomas Diesler The JMX spec defines with Open MBean generic data transfer types that are self describing. The jmx-console should display these open types properly instead of just showing their string representation. http://localhost:8080/jmx-console/HtmlAdaptor?action=inspectMBean&name=os... listBundles javax.management.openmbean.TabularDataSupport(tabularType=javax.management.openmbean.TabularType(name=BUNDLES,rowType=javax.management.openmbean.CompositeType(name=BUNDLE,items=((itemName=ExportedPackages,itemType=javax.management.openmbean.ArrayType(name=[Ljava.lang.String;,dimension=1,elementType=javax.management.openmbean.SimpleType(name=java.lang.String),primitiveArray=false)),(itemName=Fragment,itemType=javax.management.openmbean.SimpleType(name=java.lang.Boolean)),(itemName=Fragments,itemType=javax.management.openmbean.ArrayType(name=[Ljava.lang.Long;,dimension=1,elementType=javax.management.openmbean.SimpleType(name=java.lang.Long),primitiveArray=false)),(itemName=Headers,itemType=javax.management.openmbean.TabularType(name=HEADERS,rowType=javax.management.openmbean.CompositeType(name=HEADER,items=((itemName=Key,itemType=javax.management.openmbean.SimpleType(name=java.lang.String)),(itemName=Value,itemType=javax.management.openmbean.SimpleType(name=java.lang.String)))),indexNames=(Key))),(itemName=Hosts,itemType=javax.management.openmbean.ArrayType(name=[Ljava.lang.Long;,dimension=1,elementType=javax.management.openmbean.SimpleType(name=java.lang.Long),primitiveArray=false)),(itemName=Identifier,itemType=javax.management.openmbean.SimpleType(name=java.lang.Long)),(itemName=ImportedPackages,itemType=javax.management.openmbean.ArrayType(name=[Ljava.lang.String;,dimension=1,elementType=javax.management.openmbean.SimpleType(name=java.lang.String),primitiveArray=false)),(itemName=LastModified,itemType=javax.management.openmbean.SimpleType(name=java.lang.Long)),(itemName=Location,itemType=javax.management.openmbean.SimpleType(name=java.lang.String)),(itemName=PersistentlyStarted,itemType=javax.management.openmbean.SimpleType(name=java.lang.Boolean)),(itemName=RegisteredServices,itemType=javax.management.openmbean.ArrayType(name=[Ljava.lang.Long;,dimension=1,elementType=javax.management.openmbean.SimpleType(name=java.lang.Long),primitiveArray=false)),(itemName=RemovalPending,itemType=javax.management.openmbean.SimpleType(name=java.lang.Boolean)),(itemName=Required,itemType=javax.management.openmbean.SimpleType(name=java.lang.Boolean)), ... -- 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

13 years, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1152) service-ref in ejb-jar.xml is ignored

by Thomas Diesler (JIRA)

service-ref in ejb-jar.xml is ignored ------------------------------------- Key: EJBTHREE-1152 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1152 Project: EJB 3.0 Issue Type: Bug Reporter: Thomas Diesler Fix For: AS 5.0.0.Beta3 [tdiesler@tddell trunk]$ ant -Dtest=org.jboss.test.ws.jaxws.samples.serviceref.ServiceRefEJBTestCase one-test one-test: [junit] Running org.jboss.test.ws.jaxws.samples.serviceref.ServiceRefEJBTestCase [junit] Tests run: 3, Failures: 0, Errors: 1, Time elapsed: 8.761 sec [junit] Test org.jboss.test.ws.jaxws.samples.serviceref.ServiceRefEJBTestCase FAILED Caused by: javax.naming.NameNotFoundException: service1 not bound at org.jnp.server.NamingServer.getBinding(NamingServer.java:542) at org.jnp.server.NamingServer.getBinding(NamingServer.java:550) at org.jnp.server.NamingServer.getObject(NamingServer.java:556) at org.jnp.server.NamingServer.lookup(NamingServer.java:296) at org.jnp.server.NamingServer.lookup(NamingServer.java:270) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:669) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:776) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:629) at javax.naming.InitialContext.lookup(InitialContext.java:351) at org.jboss.test.ws.jaxws.samples.serviceref.EJBClient.echo(EJBClient.java:52) <ejb-jar version="3.0" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd"> <enterprise-beans> <session> <ejb-name>EJBClient</ejb-name> <remote>org.jboss.test.ws.jaxws.samples.serviceref.EJBRemote</remote> <ejb-class>org.jboss.test.ws.jaxws.samples.serviceref.EJBClient</ejb-class> <session-type>Stateless</session-type> <transaction-type>Container</transaction-type> <service-ref> <service-ref-name>service1</service-ref-name> <service-interface>javax.xml.ws.Service</service-interface> <wsdl-file>META-INF/wsdl/TestEndpoint.wsdl</wsdl-file> <service-qname xmlns:ns1="http://serviceref.samples.jaxws.ws.test.jboss.org/">ns1:TestEndpointService</service-qname> </service-ref> <service-ref> <service-ref-name>service2</service-ref-name> <service-interface>org.jboss.test.ws.jaxws.samples.serviceref.TestEndpointService</service-interface> <wsdl-file>META-INF/wsdl/TestEndpoint.wsdl</wsdl-file> <service-qname xmlns:ns1="http://serviceref.samples.jaxws.ws.test.jboss.org/">ns1:TestEndpointService</service-qname> <port-component-ref> <service-endpoint-interface>org.jboss.test.ws.jaxws.samples.serviceref.TestEndpoint</service-endpoint-interface> <enable-mtom>true</enable-mtom> </port-component-ref> </service-ref> </session> </enterprise-beans> </ejb-jar> -- 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

13 years, 5 months

4
13
0 / 0

[JBoss JIRA] Created: (JBDEPLOY-275) Allow for sub deployment to have declarative structure

by Ales Justin (JIRA)

Allow for sub deployment to have declarative structure ------------------------------------------------------- Key: JBDEPLOY-275 URL: https://issues.jboss.org/browse/JBDEPLOY-275 Project: JBoss Deployers Issue Type: Task Reporter: Ales Justin Assignee: Ales Justin Currently jboss-structure.xml can only be used on the top level deployment. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2011