September 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-8409) org.jboss.test.osgi.simple.SimpleRuntimeTestCase

by Shelly McGowan (JIRA)

org.jboss.test.osgi.simple.SimpleRuntimeTestCase ------------------------------------------------ Key: JBAS-8409 URL: https://jira.jboss.org/browse/JBAS-8409 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Shelly McGowan -- 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

15 years, 10 months

2
5
0 / 0

[JBoss JIRA] Created: (JBRULES-2708) Throw exception for non-existing subProcess id

by Diego Lopez Leon (JIRA)

Throw exception for non-existing subProcess id ---------------------------------------------- Key: JBRULES-2708 URL: https://jira.jboss.org/browse/JBRULES-2708 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core (flow) Affects Versions: FUTURE Reporter: Diego Lopez Leon Assignee: Mark Proctor Priority: Minor Fix For: 5.1.1.FINAL When you reach a subprocess node which points to an nonexistent process id the process simply abort quietly -- 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

15 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (SECURITY-532) Create a commons project

by Marcus Moyses (JIRA)

Create a commons project ------------------------ Key: SECURITY-532 URL: https://jira.jboss.org/browse/SECURITY-532 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Task Security Level: Public (Everyone can see) Components: PicketBox Affects Versions: PicketBox_v3_0_CR1 Reporter: Marcus Moyses Assignee: Marcus Moyses Fix For: PicketBox_v3_0 We need a separate project where we have common classes and utilities needed for the security projects. -- 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

15 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-8460) Change the maven artifact id of the build-config module

by Brian Stansberry (JIRA)

Change the maven artifact id of the build-config module ------------------------------------------------------- Key: JBAS-8460 URL: https://jira.jboss.org/browse/JBAS-8460 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Build System Reporter: Brian Stansberry Assignee: Paul Gier Priority: Minor Fix For: 7.0.0.M1 It's now org.jboss.as:build-config. Make it org.jboss.as:jboss-as-build-config to be consistent with the other modules. A nit, but it's annoying as this difference causes this module to not be grouped with the others in eclipse. Makes doing things like refreshing all the AS projects after switching git branches less convenient. -- 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

15 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-7568) org.jboss.test.jca.test.TxConnectionManagerUnitTestCase

by Shelly McGowan (JIRA)

org.jboss.test.jca.test.TxConnectionManagerUnitTestCase ------------------------------------------------------- Key: JBAS-7568 URL: https://jira.jboss.org/jira/browse/JBAS-7568 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Shelly McGowan -- 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

15 years, 10 months

2
5
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2177) Fix org.jboss.ejb3.test.asynchronous.unit.AsynchronousTestCase failures

by jaikiran pai (JIRA)

Fix org.jboss.ejb3.test.asynchronous.unit.AsynchronousTestCase failures ----------------------------------------------------------------------- Key: EJBTHREE-2177 URL: https://jira.jboss.org/browse/EJBTHREE-2177 Project: EJB 3.0 Issue Type: Task Components: testsuite Reporter: jaikiran pai Assignee: jaikiran pai The http://mike.lab.bos.redhat.com:8380/hudson/job/JBoss-AS-6.x-tests-ejb3/71... tests are failing due to: DEPLOYMENTS IN ERROR: Deployment "vfs:///jboss/wc/jbossas/projects/ejb3/trunk/testsuite/target/test-lib/asynchronous-test.jar" is in error due to the following reason(s): java.lang.IllegalStateException: jboss.naming:application=asynchronous-test is already installed. at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:1370) [:2.2.0.Alpha7] at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:1316) [:2.2.0.Alpha7] at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:968) [:2.2.0.Alpha7] at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:957) [:2.2.0.Alpha7] at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:373) [:6.0.0-SNAPSHOT] at org.jboss.deployment.MainDeployer.redeploy(MainDeployer.java:277) [:6.0.0-SNAPSHOT] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_16] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_16] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_16] at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_16] at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157) [:6.0.0.Beta5] at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) [:6.0.0.Beta5] at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) [:6.0.0.Beta5] at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:271) [:6.0.0.Beta5] at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:670) [:6.0.0.Beta5] at org.jboss.system.server.jmx.MBeanServerWrapper.invoke(MBeanServerWrapper.java:138) [:6.0.0-SNAPSHOT (Build SVNTag:JBoss_6.0.0-SNAPSHOT date: 20100923)] at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1426) [:1.6.0_16] at javax.management.remote.rmi.RMIConnectionImpl.access$200(RMIConnectionImpl.java:72) [:1.6.0_16] at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1264) [:1.6.0_16] at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1359) [:1.6.0_16] at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:788) [:1.6.0_16] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_16] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_16] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_16] at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_16] at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:305) [:1.6.0_16] at sun.rmi.transport.Transport$1.run(Transport.java:159) [:1.6.0_16] at java.security.AccessController.doPrivileged(Native Method) [:1.6.0_16] at sun.rmi.transport.Transport.serviceCall(Transport.java:155) [:1.6.0_16] at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535) [:1.6.0_16] at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790) [:1.6.0_16] at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649) [:1.6.0_16] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_16] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_16] at java.lang.Thread.run(Thread.java:619) [:1.6.0_16] This is because the testcase deploys asynchronous-test.sar and asynchronous-test.jar, which results in the JavaEE naming conflicts. -- 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

15 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-8456) Fix for JBAS-4072 needs applying to trunk

by James Livingston (JIRA)

Fix for JBAS-4072 needs applying to trunk ----------------------------------------- Key: JBAS-8456 URL: https://jira.jboss.org/browse/JBAS-8456 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JCA service Affects Versions: 6.0.0.M4, JBossAS-5.1.0.GA Reporter: James Livingston Assignee: Jesper Pedersen Attachments: jbas-8456.diff JBAS-4072 which fixed the XA connection factory to allow "isFoo" in addition to "getFoo" for boolean properties was only applied to the 4.2 branch. It should be applied to trunk too. -- 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

15 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (JBMETA-224) Incompatible types compilation errors when building with OpenJDK Runtime Environment (IcedTea6 1.6)

by David Walluck (JIRA)

Incompatible types compilation errors when building with OpenJDK Runtime Environment (IcedTea6 1.6) --------------------------------------------------------------------------------------------------- Key: JBMETA-224 URL: https://jira.jboss.org/jira/browse/JBMETA-224 Project: JBoss Metadata Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 1.0.1.GA Reporter: David Walluck Assignee: Alexey Loubyansky Fix For: 1.0.2.GA Incompatible types errors when building with OpenJDK Runtime Environment (IcedTea6 1.6). Does not occur with Java(TM) SE Runtime Environment (build 1.6.0_15-b03). Build log follows: [INFO] [compiler:compile] [INFO] Compiling 664 source files to /home/david/dist/jboss-metadata/JPP-6/jboss-metadata-1.0.1/target/classes [INFO] ------------------------------------------------------------------------ [ERROR] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Compilation failure /home/david/dist/jboss-metadata/JPP-6/jboss-metadata-1.0.1/src/main/java/org/jboss/metadata/ejb/jboss/JBossAssemblyDescriptorMetaData.java:[434,71] incompatible types; inferred type argument(s) java.lang.Object do not conform to bounds of type variable(s) T found : <T>org.jboss.metadata.javaee.spec.SecurityRolesMetaData required: org.jboss.metadata.javaee.spec.SecurityRolesMetaData /home/david/dist/jboss-metadata/JPP-6/jboss-metadata-1.0.1/src/main/java/org/jboss/metadata/ejb/jboss/JBossAssemblyDescriptorMetaData.java:[447,77] incompatible types; inferred type argument(s) java.lang.Object do not conform to bounds of type variable(s) T found : <T>org.jboss.metadata.javaee.spec.MessageDestinationsMetaData required: org.jboss.metadata.javaee.spec.MessageDestinationsMetaData /home/david/dist/jboss-metadata/JPP-6/jboss-metadata-1.0.1/src/main/java/org/jboss/metadata/javaee/spec/MessageDestinationsMetaData.java:[61,37] incompatible types; inferred type argument(s) java.lang.Object do not conform to bounds of type variable(s) T found : <T>org.jboss.metadata.javaee.spec.MessageDestinationsMetaData required: org.jboss.metadata.javaee.spec.MessageDestinationsMetaData /home/david/dist/jboss-metadata/JPP-6/jboss-metadata-1.0.1/src/main/java/org/jboss/metadata/javaee/spec/EJBLocalReferencesMetaData.java:[58,37] incompatible types; inferred type argument(s) java.lang.Object do not conform to bounds of type variable(s) T found : <T>org.jboss.metadata.javaee.spec.EJBLocalReferencesMetaData required: org.jboss.metadata.javaee.spec.EJBLocalReferencesMetaData /home/david/dist/jboss-metadata/JPP-6/jboss-metadata-1.0.1/src/main/java/org/jboss/metadata/javaee/spec/EJBReferencesMetaData.java:[58,37] incompatible types; inferred type argument(s) java.lang.Object do not conform to bounds of type variable(s) T found : <T>org.jboss.metadata.javaee.spec.EJBReferencesMetaData required: org.jboss.metadata.javaee.spec.EJBReferencesMetaData /home/david/dist/jboss-metadata/JPP-6/jboss-metadata-1.0.1/src/main/java/org/jboss/metadata/javaee/spec/MessageDestinationReferencesMetaData.java:[59,37] incompatible types; inferred type argument(s) java.lang.Object do not conform to bounds of type variable(s) T found : <T>org.jboss.metadata.javaee.spec.MessageDestinationReferencesMetaData required: org.jboss.metadata.javaee.spec.MessageDestinationReferencesMetaData /home/david/dist/jboss-metadata/JPP-6/jboss-metadata-1.0.1/src/main/java/org/jboss/metadata/javaee/spec/PersistenceContextReferencesMetaData.java:[49,37] incompatible types; inferred type argument(s) java.lang.Object do not conform to bounds of type variable(s) T found : <T>org.jboss.metadata.javaee.spec.PersistenceContextReferencesMetaData required: org.jboss.metadata.javaee.spec.PersistenceContextReferencesMetaData /home/david/dist/jboss-metadata/JPP-6/jboss-metadata-1.0.1/src/main/java/org/jboss/metadata/javaee/spec/ResourceEnvironmentReferencesMetaData.java:[56,37] incompatible types; inferred type argument(s) java.lang.Object do not conform to bounds of type variable(s) T found : <T>org.jboss.metadata.javaee.spec.ResourceEnvironmentReferencesMetaData required: org.jboss.metadata.javaee.spec.ResourceEnvironmentReferencesMetaData /home/david/dist/jboss-metadata/JPP-6/jboss-metadata-1.0.1/src/main/java/org/jboss/metadata/javaee/spec/ResourceReferencesMetaData.java:[56,37] incompatible types; inferred type argument(s) java.lang.Object do not conform to bounds of type variable(s) T found : <T>org.jboss.metadata.javaee.spec.ResourceReferencesMetaData required: org.jboss.metadata.javaee.spec.ResourceReferencesMetaData /home/david/dist/jboss-metadata/JPP-6/jboss-metadata-1.0.1/src/main/java/org/jboss/metadata/javaee/spec/ServiceReferencesMetaData.java:[64,37] incompatible types; inferred type argument(s) java.lang.Object do not conform to bounds of type variable(s) T found : <T>org.jboss.metadata.javaee.spec.ServiceReferencesMetaData required: org.jboss.metadata.javaee.spec.ServiceReferencesMetaData /home/david/dist/jboss-metadata/JPP-6/jboss-metadata-1.0.1/src/main/java/org/jboss/metadata/javaee/spec/AnnotatedEJBReferencesMetaData.java:[59,37] incompatible types; inferred type argument(s) java.lang.Object do not conform to bounds of type variable(s) T found : <T>org.jboss.metadata.javaee.spec.AnnotatedEJBReferencesMetaData required: org.jboss.metadata.javaee.spec.AnnotatedEJBReferencesMetaData /home/david/dist/jboss-metadata/JPP-6/jboss-metadata-1.0.1/src/main/java/org/jboss/metadata/javaee/support/JavaEEMetaDataUtil.java:[48,18] incompatible types; inferred type argument(s) java.lang.Object do not conform to bounds of type variable(s) T found : <T>M required: M /home/david/dist/jboss-metadata/JPP-6/jboss-metadata-1.0.1/src/main/java/org/jboss/metadata/javaee/support/JavaEEMetaDataUtil.java:[145,26] incompatible types; inferred type argument(s) org.jboss.metadata.javaee.support.MappableMetaData,java.lang.Object do not conform to bounds of type variable(s) C,T found : <C,T>M required: M /home/david/dist/jboss-metadata/JPP-6/jboss-metadata-1.0.1/src/main/java/org/jboss/metadata/javaee/support/JavaEEMetaDataUtil.java:[154,26] incompatible types; inferred type argument(s) org.jboss.metadata.javaee.support.MappableMetaData,java.lang.Object do not conform to bounds of type variable(s) C,T found : <C,T>M required: M -- 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

15 years, 10 months

5
6
0 / 0

[JBoss JIRA] Created: (JBMETA-299) Add support for <addressing> <respect-binding> & <mtom-threshold> subelements of <port-component-ref> element

by Richard Opalka (JIRA)

Add support for <addressing> <respect-binding> & <mtom-threshold> subelements of <port-component-ref> element -------------------------------------------------------------------------------------------------------------- Key: JBMETA-299 URL: https://jira.jboss.org/browse/JBMETA-299 Project: JBoss Metadata Issue Type: Feature Request Security Level: Public (Everyone can see) Components: common Reporter: Richard Opalka Assignee: Richard Opalka Fix For: jboss-metadata-common-2.0.0-alpha-17 <xsd:complexType name="port-component-refType"> <xsd:annotation> <xsd:documentation> The port-component-ref element declares a client dependency on the container for resolving a Service Endpoint Interface to a WSDL port. It optionally associates the Service Endpoint Interface with a particular port-component. This is only used by the container for a Service.getPort(Class) method call. </xsd:documentation> </xsd:annotation> <xsd:sequence> <xsd:element name="service-endpoint-interface" type="javaee:fully-qualified-classType"> <xsd:annotation> <xsd:documentation> The service-endpoint-interface element defines a fully qualified Java class that represents the Service Endpoint Interface of a WSDL port. </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="enable-mtom" type="javaee:true-falseType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation> Used to enable or disable SOAP MTOM/XOP mechanism on the client side for a port-component. Not to be specified for JAX-RPC runtime </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="mtom-threshold" type="javaee:xsdNonNegativeIntegerType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation> When MTOM is enabled, binary data above this size in bytes should be XOP encoded or sent as attachment. Default value is 0. Not to be specified for JAX-RPC runtime </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="addressing" type="javaee:addressingType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation> This specifies the WS-Addressing requirements for a JAX-WS web service. It corresponds to javax.xml.ws.soap.Addressing annotation or its feature javax.xml.ws.soap.AddressingFeature. See the addressingType for more information. Not to be specified for JAX-RPC runtime </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="respect-binding" type="javaee:respect-bindingType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation> Corresponds to the javax.xml.ws.RespectBinding annotation or its corresponding javax.xml.ws.RespectBindingFeature web service feature. This is used to control whether a JAX-WS implementation must respect/honor the contents of the wsdl:binding in the WSDL that is associated with the service. Not to be specified for JAX-RPC runtime </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="port-component-link" type="javaee:string" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation> The port-component-link element links a port-component-ref to a specific port-component required to be made available by a service reference. The value of a port-component-link must be the port-component-name of a port-component in the same module or another module in the same application unit. The syntax for specification follows the syntax defined for ejb-link in the EJB 2.0 specification. </xsd:documentation> </xsd:annotation> </xsd:element> </xsd:sequence> <xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType> -- 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

15 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBMETA-298) @WebServiceRef type attribute have to be specified if this annotation is used on class type

by Richard Opalka (JIRA)

@WebServiceRef type attribute have to be specified if this annotation is used on class type ------------------------------------------------------------------------------------------- Key: JBMETA-298 URL: https://jira.jboss.org/browse/JBMETA-298 Project: JBoss Metadata Issue Type: Bug Security Level: Public (Everyone can see) Components: common Reporter: Richard Opalka Assignee: Richard Opalka Fix For: jboss-metadata-common-2.0.0-alpha-17 -- 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

15 years, 10 months

1
2
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2010