December 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-5094) org.jboss.test.jaxr.scout failures

by Dimitris Andreadis (JIRA)

org.jboss.test.jaxr.scout failures ---------------------------------- Key: JBAS-5094 URL: http://jira.jboss.com/jira/browse/JBAS-5094 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Test Suite Reporter: Dimitris Andreadis Assigned To: Thomas Diesler Fix For: JBossAS-4.2.3.GA After the jboss-juddi upgrade more org.jboss.test.jaxr.scout tests fail with: org.jboss.test.jaxr.scout.JaxrBaseTestCase(tests-scout-jaxr).testJaxrEssentials Failing for the past 1 build (since #101) java.lang.NoClassDefFoundError: org/apache/xmlbeans/XmlObject at org.apache.ws.scout.registry.ConnectionImpl.<init>(ConnectionImpl.java:64) at org.apache.ws.scout.registry.ConnectionFactoryImpl.createConnection(ConnectionFactoryImpl.java:88) at org.jboss.test.jaxr.scout.JaxrBaseTestCase.setUp(JaxrBaseTestCase.java:119) https://hudson.jboss.org/hudson/job/JBoss-AS-4.2.x-TestSuite-sun15/101/te... -- 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

17 years

3
5
0 / 0

[JBoss JIRA] Created: (JBAOP-489) Undeploy does not work if path has space characters

by Flavia Rainone (JIRA)

Undeploy does not work if path has space characters --------------------------------------------------- Key: JBAOP-489 URL: http://jira.jboss.com/jira/browse/JBAOP-489 Project: JBoss AOP Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.0.0.beta2 Environment: Fedora Linux Reporter: Flavia Rainone Assigned To: Flavia Rainone Fix For: 2.0.0.CR1 AspectXMLLoader generates a name for bindings based on the path name. During undeployment, if there is a space ' ' character in this path name, the binding name will contain a "%20" where there was a ' ' char. However, the same doesn't happen during deployment: the binding is deployed with the original path name, containing the ' ' char. The result is that the binding is not undeployed since AspectManager couldn't find a binding with the queried name. -- 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

17 years

1
3
0 / 0

[JBoss JIRA] Created: (JBCACHE-1248) Expose existInMemory method in Cache interface

by gmeroz (JIRA)

Expose existInMemory method in Cache interface ---------------------------------------------- Key: JBCACHE-1248 URL: http://jira.jboss.com/jira/browse/JBCACHE-1248 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: gmeroz Assigned To: Manik Surtani I'm using JDBCCacheLoader to persist a cache and sometimes i need to know if a node is in memory (i don't care if it is in the DB). I use exist(Fqn) method in the CacheImpl - Please expose it in the interface (so i'll be able to trust backward compatability) -- 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

17 years

2
2
0 / 0

[JBoss JIRA] Created: (JBRULES-1395) Add support to modify() block in java dialect consequences

by Edson Tirelli (JIRA)

Add support to modify() block in java dialect consequences ---------------------------------------------------------- Key: JBRULES-1395 URL: http://jira.jboss.com/jira/browse/JBRULES-1395 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Drl Parser/Builder Reporter: Edson Tirelli Assigned To: Edson Tirelli Fix For: 4.1.0 Add support to modify() block in java dialect consequences, similar to what we have for MVEL, but using java syntax: modify( $p ) { setStatus( "full" ), setAge( $p.getAge() + 1 ) } -- 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

17 years

1
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1852) Problems beween JBoss Seam and Portal when a pageflow is used in Seam

by Mehmet Salgar (JIRA)

Problems beween JBoss Seam and Portal when a pageflow is used in Seam --------------------------------------------------------------------- Key: JBPORTAL-1852 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1852 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Workflow Affects Versions: 2.6.3 Final Environment: JBoss Portal 2.6.3 and Seam 2.0.0.GA Reporter: Mehmet Salgar Hi, after the news that Seam 2 is functioning with the JBoss Portal, I just made a test against 2.6.3. Only thing I made complexer then the example is to use the pageflow instead of normal JSF navigation and that is the thing hurt me. It looks like there is a dependency at portal.sar (in the lib directory) to jBPM. It looks like an old version of the library compared to Seam version. I try to replace the jBPM with in portal.sar with 3.2.1 but that break something in the JBoss Portal. With old version in place, I am getting this exception when I deployed Seam Portal application, Caused by: java.lang.NoSuchMethodError: org.jbpm.jpdl.el.i pdl/el/ExpressionEvaluator;)V at org.jboss.seam.bpm.Jbpm.startup(Jbpm.java:76) Is it possible to update this libraries or is there way to make sure it would not collide the version I have in my EAR archive. -- 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

17 years

1
0
0 / 0

[JBoss JIRA] Created: (JBREM-887) ServerInvokerrCallbackHandler.createCallbackErrorHandler() inadvertently references callbackStore

by Ron Sigal (JIRA)

ServerInvokerrCallbackHandler.createCallbackErrorHandler() inadvertently references callbackStore ------------------------------------------------------------------------------------------------- Key: JBREM-887 URL: http://jira.jboss.com/jira/browse/JBREM-887 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.4.0.Beta1 (Pinto) Reporter: Ron Sigal Assigned To: Ron Sigal Priority: Minor Fix For: 2.4.0.Beta1 (Pinto) org.jboss.remoting.callback.ServerInvokerCallbackHandler.createCallbackErrorHandler() inadvertently references callbackStore instead of callbackErrorHandler: // now try by class name if(callbackStore == null) { try { Class errorHandlerClass = Class.forName(errorHandlerName); callbackErrorHandler = (CallbackErrorHandler) errorHandlerClass.newInstance(); } catch(Exception e) { log.debug("Could not create callback error handler from the configuration value " + "given (" + errorHandlerName + ") as a fully qualified class name."); if(trace) { log.trace("Error is: " + e.getMessage(), e); } } } -- 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

17 years

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-1396) BRDRLPersistence not rendering nested patterns in not/exists

by Michael Neale (JIRA)

BRDRLPersistence not rendering nested patterns in not/exists ------------------------------------------------------------ Key: JBRULES-1396 URL: http://jira.jboss.com/jira/browse/JBRULES-1396 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-brms Affects Versions: 4.0.3 Reporter: Michael Neale Assigned To: Michael Neale Fix For: 4.1.0 -- 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

17 years

1
1
0 / 0

[JBoss JIRA] Created: (JBBUILD-440) Add property that causes jboss-deploy to be skipped.

by Paul Gier (JIRA)

Add property that causes jboss-deploy to be skipped. ---------------------------------------------------- Key: JBBUILD-440 URL: http://jira.jboss.com/jira/browse/JBBUILD-440 Project: JBoss Build System Issue Type: Feature Request Components: maven-jboss-deploy-plugin Reporter: Paul Gier Assigned To: Paul Gier Fix For: maven-jboss-deploy-plugin-1.6 It would be helpful in some situations to be able to have the jboss deploy plugin configured, but be able to skip it for things like the hudson build. -- 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

17 years

1
1
0 / 0

[JBoss JIRA] Created: (JBBUILD-437) Allow for thirdparty artifact name to differ from maven artifactId

by Andrew Lee Rubinger (JIRA)

Allow for thirdparty artifact name to differ from maven artifactId ------------------------------------------------------------------ Key: JBBUILD-437 URL: http://jira.jboss.com/jira/browse/JBBUILD-437 Project: JBoss Build System Issue Type: Feature Request Affects Versions: maven-jboss-deploy-plugin-1.5 Reporter: Andrew Lee Rubinger Assigned To: Paul Gier Defining case for this is jbossas/projects/metadata Maven Artifact ID is "jboss-metadata", but in repository.jboss.org this is placed into "jboss/metadata/", not "jboss/jboss-metadata". Please provide a hook for the override of the thirdparty artifact name. -- 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

17 years

3
7
0 / 0

[JBoss JIRA] Created: (JBAS-5093) NoClassDefFoundError: org/jboss/metadata/annotation/AbstractAnnotationImpl

by Thomas Diesler (JIRA)

NoClassDefFoundError: org/jboss/metadata/annotation/AbstractAnnotationImpl -------------------------------------------------------------------------- Key: JBAS-5093 URL: http://jira.jboss.com/jira/browse/JBAS-5093 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Thomas Diesler Fix For: JBossAS-5.0.0.Beta3 Regression in JNDI lookup http://jbws.dyndns.org:8180/hudson/job/Native-Integration-AS-5.0.0/lastBu... java.lang.NoClassDefFoundError: org/jboss/metadata/annotation/AbstractAnnotationImpl at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:620) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124) at java.net.URLClassLoader.defineClass(URLClassLoader.java:260) at java.net.URLClassLoader.access$100(URLClassLoader.java:56) at java.net.URLClassLoader$1.run(URLClassLoader.java:195) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:620) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124) at java.net.URLClassLoader.defineClass(URLClassLoader.java:260) at java.net.URLClassLoader.access$100(URLClassLoader.java:56) at java.net.URLClassLoader$1.run(URLClassLoader.java:195) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:242) at sun.rmi.server.LoaderHandler.loadClass(LoaderHandler.java:154) at java.rmi.server.RMIClassLoader$2.loadClass(RMIClassLoader.java:620) at java.rmi.server.RMIClassLoader.loadClass(RMIClassLoader.java:247) at sun.rmi.server.MarshalInputStream.resolveClass(MarshalInputStream.java:197) at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1544) at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1466) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1699) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305) at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1908) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1832) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1719) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305) at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1908) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1832) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1719) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348) at java.rmi.MarshalledObject.get(MarshalledObject.java:135) at org.jnp.interfaces.MarshalledValuePair.get(MarshalledValuePair.java:72) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:712) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:629) at javax.naming.InitialContext.lookup(InitialContext.java:351) at org.jboss.ejb3.client.ClientLauncher.loadXML(ClientLauncher.java:97) at org.jboss.ejb3.client.ClientLauncher.launch(ClientLauncher.java:168) -- 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

17 years

2
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 December 2007