July 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Moved: (JBAS-7073) ValueExpression is not working with JBOSS 5.1.0

by Stan Silvert (JIRA)

[ https://jira.jboss.org/jira/browse/JBAS-7073?page=com.atlassian.jira.plug... ] Stan Silvert moved JSFUNIT-216 to JBAS-7073: -------------------------------------------- Project: JBoss Application Server (was: JSFUnit) Key: JBAS-7073 (was: JSFUNIT-216) Component/s: JSF (was: Core) Security: Public > ValueExpression is not working with JBOSS 5.1.0 > ----------------------------------------------- > > Key: JBAS-7073 > URL: https://jira.jboss.org/jira/browse/JBAS-7073 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JSF > Environment: windows environment > Reporter: anil kumar > Assignee: Stan Silvert > Priority: Critical > > sample code is here, its giving /welcomeJSF.jsp(26,12) According to TLD or attribute directive in tag file, attribute title does not accept any expressions > welcomeJSF.jsp > <%@page contentType="text/html"%> > <%@page pageEncoding="UTF-8"%> > <%@ page import="javax.el.ValueExpression" %> > <%@ page import="javax.el.ExpressionFactory" %> > <%@ page import ="com.sun.el.ExpressionFactoryImpl"%> > > <%@taglib prefix="f" uri="http://java.sun.com/jsf/core"%> > <%@taglib prefix="h" uri="http://java.sun.com/jsf/html"%> > <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" > "http://www.w3.org/TR/html4/loose.dtd"> > <%-- > This file is an entry point for JavaServer Faces application. > --%> > <f:view> > <html> > <head> > <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> > <title>JSP Page</title> > </head> > <body> > > <% > ExpressionFactory el = new ExpressionFactoryImpl(); > ValueExpression testExpression = el.createValueExpression( " Test" , new String().getClass()); > %> > > <h:form> > <h:commandLink title="<%=testExpression%>" id="next" action="#"> > <h:outputText value="Next Page »" /> > </h:commandLink> > <h1><h:outputText value="JavaServer Faces" /></h1> > > </h:form> > </body> > </html> > </f:view> -- 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

16 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (JGRP-1008) PING: remove functionality for accessing GossipRouters and static lists

by Bela Ban (JIRA)

PING: remove functionality for accessing GossipRouters and static lists ----------------------------------------------------------------------- Key: JGRP-1008 URL: https://jira.jboss.org/jira/browse/JGRP-1008 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Bela Ban Fix For: 3.0 If initial_hosts is used, switch to TCPPING instead. If gossip_hosts is used, use TCPGOSSIP instead. We can remove this (duplicate) functionality -- 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

16 years, 6 months

1
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1860) adda check and don't process EJB2 metadata in Ejb3AnnotationHandler

by Alexey Loubyansky (JIRA)

adda check and don't process EJB2 metadata in Ejb3AnnotationHandler ------------------------------------------------------------------- Key: EJBTHREE-1860 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1860 Project: EJB 3.0 Issue Type: Task Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky Fix For: 1.1.9 This is inspired by JBMETA-208. As I explained in JBMETA-208, EJB2 metadata shouldn't even get that far. But I'll add one if-statement anyway to make sure we don't run into an issue like that again. -- 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

16 years, 6 months

2
5
0 / 0

[JBoss JIRA] Created: (JBAS-6372) Add data source configuration files for Ingres RDBMS support

by murray armfield (JIRA)

Add data source configuration files for Ingres RDBMS support ------------------------------------------------------------ Key: JBAS-6372 URL: https://jira.jboss.org/jira/browse/JBAS-6372 Project: JBoss Application Server Issue Type: Patch Security Level: Public (Everyone can see) Components: Other Affects Versions: JBossAS-5.0.1.CR1, JBossAS-4.2.4.GA, JBossAS-5.1.0.Beta1, JBossAS-6.0.0.Alpha1 Environment: N/A Reporter: murray armfield Priority: Optional Fix For: JBossAS-5.0.1.CR1, JBossAS-4.2.4.GA, JBossAS-5.1.0.Beta1, JBossAS-6.0.0.Alpha1 I'm working on getting JBoss going against the Ingres RDBMS database server. I've got some initial config files that can be included as part of the data source configurations. I have other patches for different components, but this issue is just to get two data source definitions added to the jbossas/trunk/connector/src/etc/example-config directory, one for a local-tx-datasource and one for a xa-datasource. -- 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

16 years, 6 months

3
8
0 / 0

[JBoss JIRA] Created: (JGRP-1000) COMPRESS corrupts some messages

by Dennis Reed (JIRA)

COMPRESS corrupts some messages ------------------------------- Key: JGRP-1000 URL: https://jira.jboss.org/jira/browse/JGRP-1000 Project: JGroups Issue Type: Bug Affects Versions: 2.4.5 Reporter: Dennis Reed Assignee: Dennis Reed COMPRESS.down() stores the compressed message in a temporary buffer the same size as the original message. If the compressed size of a message is larger than the original, then part of the message is lost, with no errors reported. -- 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

16 years, 6 months

2
5
0 / 0

[JBoss JIRA] Updated: (JBAS-7050) "ClassNotFoundException: org.jboss.resource.deployers.management.DsDataSourceTemplateInfo" on remote calls to ManagementView.getTemplate()

by Ian Springer (JIRA)

[ https://jira.jboss.org/jira/browse/JBAS-7050?page=com.atlassian.jira.plug... ] Ian Springer updated JBAS-7050: ------------------------------- Summary: "ClassNotFoundException: org.jboss.resource.deployers.management.DsDataSourceTemplateInfo" on remote calls to ManagementView.getTemplate() (was: Unable to create any kind of datasource or connection factory) Component/s: ProfileService > "ClassNotFoundException: org.jboss.resource.deployers.management.DsDataSourceTemplateInfo" on remote calls to ManagementView.getTemplate() > ------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBAS-7050 > URL: https://jira.jboss.org/jira/browse/JBAS-7050 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: ProfileService > Affects Versions: JBossAS-5.1.0.GA > Reporter: Lukas Krejci > Assignee: Scott M Stark > Priority: Blocker > Fix For: JBossAS-5.2.0.Beta1 > > > When trying to create a datasource in AS5 using JON, the following exception occurs: > java.lang.ClassNotFoundException: org.jboss.resource.deployers.management.DsDataSourceTemplateInfo > at org.jboss.remoting.serialization.ClassLoaderUtility.loadClass(ClassLoaderUtility.java:103) > at org.jboss.remoting.loading.RemotingClassLoader.loadClass(RemotingClassLoader.java:86) > at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320) > at java.lang.Class.forName0(Native Method) > at java.lang.Class.forName(Class.java:247) > at org.jboss.remoting.loading.ObjectInputStreamWithClassLoader.resolveClass(ObjectInputStreamWithClassLoader.java:179) > at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1575) > at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1496) > at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1732) > at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329) > at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351) > at org.jboss.aop.joinpoint.InvocationResponse.readExternal(InvocationResponse.java:119) > at java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1792) > at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1751) > at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329) > at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1947) > at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1871) > at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753) > at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329) > at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351) > at org.jboss.remoting.serialization.impl.java.JavaSerializationManager.receiveObjectVersion2_2(JavaSerializationManager.java:238) > at org.jboss.remoting.serialization.impl.java.JavaSerializationManager.receiveObject(JavaSerializationManager.java:138) > at org.jboss.remoting.marshal.serializable.SerializableUnMarshaller.read(SerializableUnMarshaller.java:123) > at org.jboss.invocation.unified.marshall.InvocationUnMarshaller.read(InvocationUnMarshaller.java:59) > at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.versionedRead(MicroSocketClientInvoker.java:1220) > at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:850) > at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:165) > at org.jboss.remoting.Client.invoke(Client.java:1724) > at org.jboss.remoting.Client.invoke(Client.java:629) > at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:60) > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) > at org.jboss.aspects.remoting.MergeMetaDataInterceptor.invoke(MergeMetaDataInterceptor.java:74) > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) > at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:65) > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) > at org.jboss.aop.generatedproxies.AOPProxy$1.getTemplate(AOPProxy$1.java) > at org.rhq.plugins.jbossas5.ApplicationServerComponent.createConfigurationBasedResource(ApplicationServerComponent.java:415) > at org.rhq.plugins.jbossas5.ApplicationServerComponent.createResource(ApplicationServerComponent.java:295) > 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.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:526) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:619) > at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:72) > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) > at org.jboss.aspects.remoting.MergeMetaDataInterceptor.invoke(MergeMetaDataInterceptor.java:74) > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) > at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:65) > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) > at org.jboss.aop.generatedproxies.AOPProxy$1.getTemplate(AOPProxy$1.java) > at org.rhq.plugins.jbossas5.ApplicationServerComponent.createConfigurationBasedResource(ApplicationServerComponent.java:415) > at org.rhq.plugins.jbossas5.ApplicationServerComponent.createResource(ApplicationServerComponent.java:295) > 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.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:526) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:619) > I was only able to find this class in jboss-embedded-all maven module. -- 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

16 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-7070) EJB3 version check should be based on JBossMetaData.isEJB3x()

by Alexey Loubyansky (JIRA)

EJB3 version check should be based on JBossMetaData.isEJB3x() ------------------------------------------------------------- Key: JBAS-7070 URL: https://jira.jboss.org/jira/browse/JBAS-7070 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB3 Affects Versions: JBossAS-5.1.0.GA Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky Fix For: JBossAS-5.2.0.Beta1 org.jboss.ejb3.deployers.Ejb3Deployer does it this way: !(metaData.isEJB2x() || metaData.isEJB1x()). Instead, it should use metaData.isEJB3x(). This is inspired by JBMETA-208. -- 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

16 years, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-4905) Resolve EJB3 / Web Service integration issues

by Thomas Diesler (JIRA)

Resolve EJB3 / Web Service integration issues --------------------------------------------- Key: JBAS-4905 URL: http://jira.jboss.com/jira/browse/JBAS-4905 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Reporter: Thomas Diesler Assigned To: Thomas Diesler Fix For: JBossAS-4.2.3.GA This is a container for relevant ejb3/jbossws integration issues -- 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

16 years, 6 months

3
4
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1531) Consider multi-thread replication

by Tim Fox (JIRA)

Consider multi-thread replication --------------------------------- Key: JBMESSAGING-1531 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1531 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assignee: Tim Fox Fix For: 2.1.0.beta Because of the indeterminism of multi-threading, replication is performed over a single thread which has consequences for throughput. Multi-thread replication is a very tricky area but we should consider possible approaches here -- 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

16 years, 6 months

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-7069) BaseWrapperManagedConnection tries to close a probaby unusable connection without any timeouts

by Christian Daszenies (JIRA)

BaseWrapperManagedConnection tries to close a probaby unusable connection without any timeouts ---------------------------------------------------------------------------------------------- Key: JBAS-7069 URL: https://jira.jboss.org/jira/browse/JBAS-7069 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.2.3.GA Reporter: Christian Daszenies org/jboss/resource/adapter/jdbc/BaseWrapperManagedConnection calls con.close() in destroy() on a probably unusable and not responding connection. destroy() is called when a (OracleValid)ConnectionChecker marks a connection as unusable, in our case because of a timeout in isValidConnection(Connection) when BaseWrapperManagedConnection calls close() on the same connection the process hangs infinitely -- 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

16 years, 6 months

1
0
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 July 2009