November 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-3560) shutdown.sh fails because it cannot find org/jboss/logging/Logger

by Ovidiu Feodorov (JIRA)

shutdown.sh fails because it cannot find org/jboss/logging/Logger ----------------------------------------------------------------- Key: JBAS-3560 URL: http://jira.jboss.com/jira/browse/JBAS-3560 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Other Affects Versions: JBossAS-5.0.0.Beta Reporter: Ovidiu Feodorov Priority: Minor org/jboss/logging/Logger is no longer shipped with jbossall-client.jar, so the shutdown script fails: $ ./shutdown.sh -S Exception in thread "main" java.lang.NoClassDefFoundError: org/jboss/logging/Logger at org.jnp.interfaces.NamingContext.<clinit>(NamingContext.java:159) .... -- 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

19 years, 7 months

3
4
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1096) Error when set/get of portlet property

by Roy Russo (JIRA)

Error when set/get of portlet property -------------------------------------- Key: JBPORTAL-1096 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1096 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Core Affects Versions: 2.6.Alpha1 Reporter: Roy Russo Assigned To: Julien Viet Priority: Critical Fix For: 2.6.Alpha1 This fails in the Weather/News portlets: response.setProperty("expiration-cache", request.getPreferences().getValue("expires", "180")); 08:49:54,855 ERROR [ControllerCommand] Rendering portlet window default.News.WeatherPortletWindow triggered the following error : java.lang.IllegalArgumentException: Scope not recognized response_properties at org.jboss.portal.common.invocation.AbstractInvocationContext.getAttributeResolver(AbstractInvocationContext.java:88) at org.jboss.portal.common.invocation.AbstractInvocationContext.setAttribute(AbstractInvocationContext.java:121) at org.jboss.portal.common.invocation.Invocation.setAttribute(Invocation.java:80) at org.jboss.portal.portlet.impl.jsr168.PortletResponseImpl.setProperty(PortletResponseImpl.java:103) at org.jboss.samples.portlet.weather.WeatherPortlet.doView(WeatherPortlet.java:116) at javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:133) at javax.portlet.GenericPortlet.render(GenericPortlet.java:306) at org.jboss.portal.portlet.container.PortletContainer.invokeRender(PortletContainer.java:516) at org.jboss.portal.portlet.container.PortletContainer.dispatch(PortletContainer.java:438) at org.jboss.portal.portlet.container.PortletContainerInvoker$1.invoke(PortletContainerInvoker.java:73) at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:134) at org.jboss.portal.core.aspects.portlet.TransactionInterceptor.org$jboss$portal$core$aspects$portlet$TransactionInterceptor$invokeNotSupported$aop(TransactionInterceptor.java:85) at org.jboss.portal.core.aspects.portlet.TransactionInterceptor$invokeNotSupported_N4547270787964792031.invokeNext(TransactionInterceptor$invokeNotSupported_N4547270787964792031.java) at org.jboss.aspects.tx.TxPolicy.invokeInNoTx(TxPolicy.java:66) at org.jboss.aspects.tx.TxInterceptor$NotSupported.invoke(TxInterceptor.java:101) at org.jboss.portal.core.aspects.portlet.TransactionInterceptor$invokeNotSupported_N4547270787964792031.invokeNext(TransactionInterceptor$invokeNotSupported_N4547270787964792031.java) at org.jboss.portal.core.aspects.portlet.TransactionInterceptor.invokeNotSupported(TransactionInterceptor.java) at org.jboss.portal.core.aspects.portlet.TransactionInterceptor.invoke(TransactionInterceptor.java:55) at org.jboss.portal.portlet.invocation.PortletInterceptor.invoke(PortletInterceptor.java:38) at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:118) at org.jboss.portal.core.aspects.portlet.HeaderInterceptor.invoke(HeaderInterceptor.java:50) at org.jboss.portal.portlet.invocation.PortletInterceptor.invoke(PortletInterceptor.java:38) at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:118) at org.jboss.portal.portlet.aspects.portlet.ProducerCacheInterceptor.invoke(ProducerCacheInterceptor.java:51) at org.jboss.portal.portlet.invocation.PortletInterceptor.invoke(PortletInterceptor.java:38) at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:118) at org.jboss.portal.portlet.aspects.portlet.ModesInterceptor.invoke(ModesInterceptor.java:60) at org.jboss.portal.portlet.invocation.PortletInterceptor.invoke(PortletInterceptor.java:38) at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:118) at org.jboss.portal.bridge.BridgeInterceptor.invoke(BridgeInterceptor.java:46) at org.jboss.portal.portlet.invocation.PortletInterceptor.invoke(PortletInterceptor.java:38) at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:118) at org.jboss.portal.portlet.aspects.portlet.WindowStatesInterceptor.invoke(WindowStatesInterceptor.java:55) at org.jboss.portal.portlet.invocation.PortletInterceptor.invoke(PortletInterceptor.java:38) at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:118) at org.jboss.portal.portlet.aspects.portlet.PortletSessionSynchronizationInterceptor.invoke(PortletSessionSynchronizationInterceptor.java:78) at org.jboss.portal.portlet.invocation.PortletInterceptor.invoke(PortletInterceptor.java:38) at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:118) at org.jboss.portal.portlet.aspects.portlet.ContextTrackerInterceptor.invoke(ContextTrackerInterceptor.java:46) at org.jboss.portal.portlet.invocation.PortletInterceptor.invoke(PortletInterceptor.java:38) at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:118) at org.jboss.portal.portlet.aspects.portlet.ContextDispatcherInterceptor$InvokeNextCommand.execute(ContextDispatcherInterceptor.java:148) -- 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

19 years, 7 months

2
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1121) Drag and drop for anon users in shared pages should warn you with an alert of some sort

by Alex Pinkin (JIRA)

Drag and drop for anon users in shared pages should warn you with an alert of some sort --------------------------------------------------------------------------------------- Key: JBPORTAL-1121 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1121 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.6.DR1 Reporter: Alex Pinkin Assigned To: Roy Russo Fix For: 2.6.Alpha1 When users first arrive to the portal home page after installing JBP, it is a good idea to allow them to test out drag and drop immediatly. However, editing shared pages doesn't persist for longer than the user session. We need to make sure that users understand that by giving them some kind of notification when they drag a portlet on a shared page as an anonymous user. -- 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

19 years, 7 months

4
5
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1066) Instance customizations

by Julien Viet (JIRA)

Instance customizations ----------------------- Key: JBPORTAL-1066 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1066 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Portal Core Affects Versions: 2.6.Alpha1 Reporter: Julien Viet Assigned To: Julien Viet Fix For: 2.6.Alpha1 -- 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

19 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-172) ActiveMQ qualification

by Mark Little (JIRA)

ActiveMQ qualification ---------------------- Key: JBESB-172 URL: http://jira.jboss.com/jira/browse/JBESB-172 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: ESB Core Affects Versions: 4.0 Beta 1 Maintenance Pack 1 Reporter: Mark Little Assigned To: Arvinder Singh Fix For: 4.0 We need to qualify agains ActiveMQ. Ideally this should just be a configuration change and updates to our manual(s). -- 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

19 years, 7 months

3
9
0 / 0

[JBoss JIRA] Created: (JGRP-332) Support concurrent flushing

by Vladimir Blagojevic (JIRA)

Support concurrent flushing --------------------------- Key: JGRP-332 URL: http://jira.jboss.com/jira/browse/JGRP-332 Project: JGroups Issue Type: Feature Request Affects Versions: 2.4 Reporter: Vladimir Blagojevic Assigned To: Vladimir Blagojevic Fix For: 2.5 JGroups 2.4 introduces FLUSH protocol that enables stop-the-world model for JGroups nodes. However, FLUSH protocol currently does not support coordination between nodes when it comes to concurrent requests for flush. For example, in JGroups 2.4 if more than one MuxChannel sitting on top of JChannel requests flush the behaviour is nondeterministic. Also, we should investigate how to combine concurrent flush requests coming from state transfer protocol with flush requests coming from GMS protocol. -- 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

19 years, 7 months

1
3
0 / 0

[JBoss JIRA] Created: (JBAS-3874) Deployment of JavaEE5 application client fails if element "application-client" has attribute "id"

by Wolfgang Knauf (JIRA)

Deployment of JavaEE5 application client fails if element "application-client" has attribute "id" ------------------------------------------------------------------------------------------------- Key: JBAS-3874 URL: http://jira.jboss.com/jira/browse/JBAS-3874 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployment services Affects Versions: JBossAS-5.0.0.Beta1 Reporter: Wolfgang Knauf Assigned To: Dimitris Andreadis I copied the following ear file to the deploy directory of the default configuration and restarted the server: http://www.informatik.fh-wiesbaden.de/~knauf/SWTVertiefung2006/stateless/... (Works fine with JBoss 4 + EJB3) It did not deploy with this error in server.log: 2006-11-21 20:26:44,562 DEBUG [org.jboss.ejb3.deployers.AppClientParsingDeployer] Found application-client.xml file: jar:file:/C:/Temp/jboss-5.0.0.Beta1/server/default/deploy/Stateless.ear!/StatelessClient.jar 2006-11-21 20:26:44,921 ERROR [org.jboss.ejb3.deployers.AppClientParsingDeployer] Error during deployment: jar:file:/C:/Temp/jboss-5.0.0.Beta1/server/default/deploy/Stateless.ear!/StatelessClient.jar org.jboss.deployers.spi.DeploymentException: Error parsing meta data Stateless.ear/StatelessClient.jar/META-INF/application-client.xml at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49) at org.jboss.deployers.plugins.deployers.helpers.ObjectModelFactoryDeployer.parse(ObjectModelFactoryDeployer.java:87) at org.jboss.deployers.plugins.deployers.helpers.AbstractParsingDeployer.parse(AbstractParsingDeployer.java:145) at org.jboss.deployers.plugins.deployers.helpers.AbstractParsingDeployer.createMetaData(AbstractParsingDeployer.java:112) at org.jboss.deployers.plugins.deployers.helpers.AbstractParsingDeployer.createMetaData(AbstractParsingDeployer.java:88) at org.jboss.ejb3.deployers.AppClientParsingDeployer.deploy(AppClientParsingDeployer.java:61) at org.jboss.deployers.plugins.deployer.AbstractSimpleDeployer.commitDeploy(AbstractSimpleDeployer.java:52) at org.jboss.deployers.plugins.deployer.DeployerWrapper.commitDeploy(DeployerWrapper.java:145) at org.jboss.deployers.plugins.deployment.MainDeployerImpl.commitDeploy(MainDeployerImpl.java:440) at org.jboss.deployers.plugins.deployment.MainDeployerImpl.process(MainDeployerImpl.java:381) at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:366) at org.jboss.system.server.profileservice.ProfileServiceBootstrap.bootstrap(ProfileServiceBootstrap.java:246) at org.jboss.kernel.plugins.bootstrap.AbstractBootstrap.run(AbstractBootstrap.java:89) at org.jboss.system.server.profileservice.ServerImpl.doStart(ServerImpl.java:401) at org.jboss.system.server.profileservice.ServerImpl.start(ServerImpl.java:340) at org.jboss.Main.boot(Main.java:210) at org.jboss.Main$1.run(Main.java:508) at java.lang.Thread.run(Thread.java:595) Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: jar:file:/C:/DOCUME~1/.../LOCALS~1/Temp/nestedjar62569.tmp!/META-INF/application-client.xml@5,116 at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:164) at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:180) at org.jboss.deployers.plugins.deployers.helpers.ObjectModelFactoryDeployer.parse(ObjectModelFactoryDeployer.java:83) ... 16 more Caused by: java.lang.IllegalArgumentException: id at org.jboss.ejb3.metamodel.ApplicationClientDDObjectFactory.newRoot(ApplicationClientDDObjectFactory.java:137) at org.jboss.xb.binding.DelegatingObjectModelFactory.newRoot(DelegatingObjectModelFactory.java:70) at org.jboss.xb.binding.ObjectModelBuilder.startElement(ObjectModelBuilder.java:309) at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:323) at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source) at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl$NSContentDispatcher.scanRootElementHook(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:160) ... 18 more application-client.xml looks like this: <?xml version="1.0" encoding="UTF-8"?> <application-client id="Application-client_ID" version="5" 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/application-client_5.xsd"> <display-name>StatelessClient</display-name> <ejb-ref> <ejb-ref-name>ejb/GeometricModel</ejb-ref-name> <ejb-ref-type>Session</ejb-ref-type>  <home>java.lang.Object</home> <remote>de.fhw.swtvertiefung.knauf.stateless.GeometricModel</remote> </ejb-ref> </application-client> The ID attribute is valid, "application-client_5.xsd" defines this: <xsd:complexType name="application-clientType"> <xsd:sequence> <xsd:group ref="javaee:descriptionGroup"/> .... <xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType> By the way: the ID attribute is autogenerated by Eclipse/WebToolsPlatform (the above project was converted from Java2EE 1.4). -- 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

19 years, 7 months

3
3
0 / 0

[JBoss JIRA] Created: (JBAS-3590) JBoss maps java.math.BigDecimal to numeric(19, 2) for Firebird 1.5 DB. Firebird complains precision must be <= 18.

by knaveofhearts (JIRA)

JBoss maps java.math.BigDecimal to numeric(19,2) for Firebird 1.5 DB. Firebird complains precision must be <= 18. ------------------------------------------------------------------------------------------------------------------ Key: JBAS-3590 URL: http://jira.jboss.com/jira/browse/JBAS-3590 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB3 Affects Versions: JBossAS-4.0.4.GA Environment: JBossAS-4.0.4.GA, Firebird 1.5, Fedora Core 5 Linux. Reporter: knaveofhearts Assigned To: Bill Burke This is a problem with EJB 3 entity persistence with CMP. I have several classes in which member variables are declared as BigDecimal. The classes all work fine with HSQLDB, which I have been using for rapid development, using the create-drop capability. I tried to switch the backend to Firebird 1.5 by changing the two relevant files (if I recall, persistence.xml and the []-ds.xml file), and managed to remove all the problems (e.g., Fireword reserve words like "role", "user", and "type" that I used as class or attribute names) except for BigDecimal fields. The server log says that BigDecimal is being mapped to numeric(19,2), but the maximum precision for Firebird is 18. If I replace all the BigDecimal fields with double, then my basic DB access tests run okay. I have posted this problem to two JBoss forums (EJB3 and Persistence) and to one Firebird forum (Firebird-Java), but have gotten no replies. If there is an easy fix, I would appreciate learning about it. -- 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

19 years, 7 months

3
3
0 / 0

[JBoss JIRA] Created: (JBREM-635) Remove misleading error message from HTTPUnMarshaller.

by Ron Sigal (JIRA)

Remove misleading error message from HTTPUnMarshaller. ------------------------------------------------------ Key: JBREM-635 URL: http://jira.jboss.com/jira/browse/JBREM-635 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.2.0.Beta1 (Bluto) Reporter: Ron Sigal Assigned To: Ron Sigal Priority: Minor Fix For: 2.2.0.Beta1 (Bluto) In read() the code try { if (isBinaryData(metadata)) return super.read(inputStream, metadata); } catch (Exception e) { log.warn("Can not get Content-Type from header for http unmarshalling."); } can return a warning about content-type even if the exception is thrown by super.read(). -- 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

19 years, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-3539) CLONE -jboss-client.jar misses MarshalledInvocation$DeclaredMethods

by Matthew L Daniel (JIRA)

CLONE -jboss-client.jar misses MarshalledInvocation$DeclaredMethods ------------------------------------------------------------------- Key: JBAS-3539 URL: http://jira.jboss.com/jira/browse/JBAS-3539 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.0.0 Final Reporter: Matthew L Daniel Assigned To: Scott M Stark Fix For: Closed issues from sourceforge Attachments: JBAS-1163_2.patch SourceForge Submitter: igorfie . Latest CVS version of JBoss 4.0.0 is missing org/jboss/invocation/MarshalledInvocation$DeclaredMethodsAction from the jboss-client.jar. As a result org.jboss.ant.JMX fails with NoClassDefFoundError. The following patch should fix the problem. Index: build.xml =================================================================== RCS file: /cvsroot/jboss/jboss/build.xml,v retrieving revision 1.173.2.2 diff -u -r1.173.2.2 build.xml --- build.xml 17 Oct 2004 18:49:28 -0000 1.173.2.2 +++ build.xml 26 Oct 2004 03:57:20 -0000 @@ -470,6 +470,7 @@ <include name="org/jboss/invocation/MarshallingInvokerInterceptor.class"/> <include name="org/jboss/invocation/PayloadKey.class"/> <include name="org/jboss/invocation/MarshalledInvocation.class"/> + <include name="org/jboss/invocation/MarshalledInvocation$DeclaredMethodsAction.class"/> <include name="org/jboss/invocation/MarshalledValue.class"/> <include name="org/jboss/invocation/MarshalledValueInputStream.class"/> <include name="org/jboss/invocation/MarshalledValueOutputStream*.class"/> -- 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

19 years, 7 months

2
3
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 November 2006