January 2010 - jboss-jira - Jboss List Archives

[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

12 years, 11 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

12 years, 11 months

1
1
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

12 years, 11 months

1
1
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

12 years, 11 months

4
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

12 years, 11 months

4
13
0 / 0

[JBoss JIRA] Created: (JBRULES-1787) Undocumented Panels for Eclipse Guided Rule Editor

by Steve Nunez (Illation) (JIRA)

Undocumented Panels for Eclipse Guided Rule Editor -------------------------------------------------- Key: JBRULES-1787 URL: https://jira.jboss.org/jira/browse/JBRULES-1787 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.0.7 Reporter: Steve Nunez (Illation) Assignee: Mark Proctor In the Guided Rule Editor section: http://downloads.jboss.com/drools/docs/4.0.7.19894.GA/html_single/index.h... There is an explanation of the guided editor. However there is no explanation of what to expect to see in the various tabs, except the first one. What I expect to see in the "Generated DRL (read-only)" tab is the actual DRL that will be sent to the compiler, similar to that we see in the "DRL Viewer" pane of a .dslr file. What I actually see is the same sort of text that I see in the .dslr file, with no idea if it's actually be rendered correctly (in a subsequent step). -- 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

12 years, 11 months

5
14
0 / 0

[JBoss JIRA] Created: (JBRULES-1889) figures not properly displayed in Drools Expert User Guide

by Jaroslaw Kijanowski (JIRA)

figures not properly displayed in Drools Expert User Guide ---------------------------------------------------------- Key: JBRULES-1889 URL: https://jira.jboss.org/jira/browse/JBRULES-1889 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-docs-expert Affects Versions: 5.0.0.M3 Reporter: Jaroslaw Kijanowski Assignee: Mark Proctor Affected figures: 1.1.; 1.4.; 1.5 -- 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

12 years, 11 months

4
6
0 / 0

[JBoss JIRA] Created: (JBAS-7447) PersistentManager for sessions is broken

by Emilio Davis (JIRA)

PersistentManager for sessions is broken ---------------------------------------- Key: JBAS-7447 URL: https://jira.jboss.org/jira/browse/JBAS-7447 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web (Tomcat) service Affects Versions: JBossAS-5.1.0.GA Reporter: Emilio Davis Assignee: Remy Maucherat Using the following context.xml <Context cookies="true" crossContext="true"> <Manager className="org.apache.catalina.session.PersistentManager" maxIdleSwap="1200" saveOnRestart="true"> <Store checkInterval="60" className="org.apache.catalina.session.JDBCStore" connectionURL="jdbc:mysql://localhost:3306/XXX?user=XXX&password=XXX" driverName="com.mysql.jdbc.Driver" sessionAppCol="app_name" sessionDataCol="session_data" sessionIdCol="session_id" sessionLastAccessedCol="last_access" sessionMaxInactiveCol="max_inactive" sessionTable="tomcat_sessions" sessionValidCol="valid_session"/> </Manager> <InstanceListener>org.jboss.web.tomcat.security.RunAsListener</InstanceListener> </Context> That used to work in jboss4.0.5GA and correct according to tomcat 6 documentation jboss 5.1.0GA fails to start tomcat with the following exception: 2009-11-02 23:11:54,292 INFO [org.jboss.web.tomcat.service.deployers.TomcatDeployment] (main) deplo y, ctxPath=/ 2009-11-02 23:11:55,619 ERROR [org.jboss.web.tomcat.service.deployers.JBossContextConfig] (main) XML error parsing: context.xml org.jboss.xb.binding.JBossXBException: Failed to parse source: Store not found as a child of Manager in unordered_sequence: attributes? at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:203) at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:183) at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:133) at org.jboss.web.tomcat.service.deployers.JBossContextConfig.processContextConfig(JBossContextCo nfig.java:573) at org.jboss.web.tomcat.service.deployers.JBossContextConfig.init(JBossContextConfig.java:536) at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:279) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117) at org.apache.catalina.core.StandardContext.init(StandardContext.java:5436) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4148) at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeployInternal(TomcatDeploymen t.java:310) at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeploy(TomcatDeployment.java:1 42) at org.jboss.web.deployers.AbstractWarDeployment.start(AbstractWarDeployment.java:461) at org.jboss.web.deployers.WebModule.startModule(WebModule.java:118) at org.jboss.web.deployers.WebModule.start(WebModule.java:97) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668) at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:206) at $Proxy38.start(Unknown Source) I opened a thread in the tomcat integration forum (http://www.jboss.org/index.html?module=bb&op=viewtopic&t=163337) but got no response. -- 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

12 years, 11 months

3
3
0 / 0

[JBoss JIRA] Created: (JBRULES-2289) Support JPA Resource Local EntityTransaction based Transactions

by Michael Youngstrom (JIRA)

Support JPA Resource Local EntityTransaction based Transactions --------------------------------------------------------------- Key: JBRULES-2289 URL: https://jira.jboss.org/jira/browse/JBRULES-2289 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 5.0.1.FINAL Reporter: Michael Youngstrom Assignee: Mark Proctor It would be nice if wherever JPA is used in Drools (drools-flow in particular) there was support for RESOURCE_LOCAL transactions through JPA's EntityTransaction interface as an alternative to JTA. Support for resource local transactions would reduce the base Drools Flow dependency footprint (no need for bitronix) as well as allow Drools to be used in a containerless or Tomcat like environment without a JTA implementation available. Although embeddable solutions are available they are often either buggy or complex. It would be nice to not have to deal with them if possible. If the idea is acceptable I'd be willing to put together an initial patch. -- 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

12 years, 11 months

2
2
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1771) NotSerializableException is thrown from DayCounter class

by Tyronne Wickramarathne (JIRA)

NotSerializableException is thrown from DayCounter class -------------------------------------------------------- Key: JBMESSAGING-1771 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1771 Project: JBoss Messaging Issue Type: Bug Components: Configuration and Management Affects Versions: 1.4.0.SP3.CP08 Environment: JBoss-SOA-4.3_CP2, JBM-1.4.0.SP3-CP08.patch01 Reporter: Tyronne Wickramarathne Even though the MessageCounter class implements Serializable interface as per JBMESSAGING-1430; the NotSerializableException is still thrown when accessing MessageCounter via JMX console. The root cause seems to be the DayCounter class. -- 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

12 years, 11 months

4
7
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2010