July 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBXB-214) SchemaBindingValidator: complex types with adapters should pass validation as simple types

by Alexey Loubyansky (JIRA)

SchemaBindingValidator: complex types with adapters should pass validation as simple types ------------------------------------------------------------------------------------------ Key: JBXB-214 URL: https://jira.jboss.org/jira/browse/JBXB-214 Project: JBoss XML Binding (JBossXB) Issue Type: Bug Affects Versions: JBossXB-2.0.2.Beta1 Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky Fix For: JBossXB-2.0.2.GA At the moment the fact that the complex type has an adapter associated with it is ignored during validation. And comparison of such complex types to XSD simple types fails. -- 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

17 years

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-7089) <h:column> level rendering is not working in JBOSS

by anil kumar (JIRA)

<h:column> level rendering is not working in JBOSS --------------------------------------------------- Key: JBAS-7089 URL: https://jira.jboss.org/jira/browse/JBAS-7089 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JSF Affects Versions: JBossAS-5.1.0.GA Environment: windows Reporter: anil kumar Assignee: Stan Silvert <h:column> level rendering is not working in JBOSS but works in Glassfish. <h:dataTable value="#{HeaderBean.records}" var="screenConfig"> <h:column> <h:outputText value="#{screenConfig.displayTitle}" rendered="#{'5' eq '5'}"> </h:outputText> </h:column> </h:dataTable> this is working perfectly. <h:dataTable value="#{HeaderBean.records}" var="screenConfig"> <h:column rendered="#{'5' eq '5'}"> > <h:outputText value="#{screenConfig.displayTitle}" </h:outputText> </h:column> </h:dataTable> where as above one is not working. I really don't understand why this is not working in JBOSS. -- 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

17 years

2
4
0 / 0

[JBoss JIRA] Created: (JBJCA-111) SJC: Temporary files must be deleted before deployment

by Jesper Pedersen (JIRA)

SJC: Temporary files must be deleted before deployment ------------------------------------------------------ Key: JBJCA-111 URL: https://jira.jboss.org/jira/browse/JBJCA-111 Project: JBoss JCA Issue Type: Bug Components: Deployer Affects Versions: 1.0.0.Alpha1 Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.0.Alpha2 Make sure that the temporary directory that resource adapters that are extracted to are cleaned up first. -- 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

17 years

1
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1681) fetch based on messageId doesn't work

by Konstantin Pupkov (JIRA)

fetch based on messageId doesn't work ------------------------------------- Key: JBMESSAGING-1681 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1681 Project: JBoss Messaging Issue Type: Bug Components: Messaging Core Affects Versions: 1.4.3.GA Environment: Linux, Ubuntu 9, JBoss 5.1.0.GA, My SQL 5, Java 6 Reporter: Konstantin Pupkov Assignee: Tim Fox here is me code on client: String msgId="ID:JBM-511cfd0b-b4a8-4148-bd69-127a1fdeecfe";-->no worries that message has been just created and 100% exists in my DB QueueReceiver recv= ConnectionFactory.getInstance().getSession().createReceiver(queue, "JMSMessageID='"+msgId+"'"); Message msg1= recv.receive();---->hungs on forever I tied QueueReceiver recv= ConnectionFactory.getInstance().getSession().createReceiver(queue, "JBMessageID='"+msgId+"'"); --> this is according to documentation. failed as well Please fix it and keep standard approach: JMSMessageID not JBMessageID. -- 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

17 years

3
14
0 / 0

[JBoss JIRA] Created: (JBDEPLOY-203) Fix the state usage when doing Deployers::checkComplete

by Ales Justin (JIRA)

Fix the state usage when doing Deployers::checkComplete ------------------------------------------------------- Key: JBDEPLOY-203 URL: https://jira.jboss.org/jira/browse/JBDEPLOY-203 Project: JBoss Deployers Issue Type: Bug Components: maindeployer Affects Versions: JBDEPLOY-2.0.8.GA Reporter: Ales Justin Assignee: Ales Justin Fix For: JBDEPLOY-2.2.x Currently we're using the wrong state to determine if some component is missing some dependency. Instead of DependencyItem::getWhenRequired we should use getDependentState. -- 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

17 years

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-7094) JaasSecurityDomain fails to decrypt some PBE passwords

by Marcus Moyses (JIRA)

JaasSecurityDomain fails to decrypt some PBE passwords ------------------------------------------------------ Key: JBAS-7094 URL: https://jira.jboss.org/jira/browse/JBAS-7094 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Security Affects Versions: JBossAS-5.1.0.GA Reporter: Marcus Moyses Assignee: Marcus Moyses Fix For: JBossAS-5.2.0.Beta1 Certain passwords when encrypted with PBE result in a String with leading zeros. These leading zeros are not printed with the String so decrypting the password fails because of invalid number of bytes. An exception is thrown: javax.crypto.IllegalBlockSizeException: Input length (with padding) not multiple of 8 bytes -- 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

17 years

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-7088) expressions like 'ne', 'eq' are not working in jboss

by anil kumar (JIRA)

expressions like 'ne','eq' are not working in jboss --------------------------------------------------- Key: JBAS-7088 URL: https://jira.jboss.org/jira/browse/JBAS-7088 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JSF Affects Versions: JBossAS-5.1.0.GA Environment: windows Reporter: anil kumar Assignee: Stan Silvert <h:dataTable value="#{HeaderBean.records}" var="screenConfig"> <h:column rendered="#{screenConfig.displayTitle ne 'dashboard'}"> <h:outputText value="#{screenConfig.displayTitle}"> </h:outputText> </h:column> </h:dataTable> expressions like 'ne','eq' are not working in jboss but its working fine in Glassfish. please suggest me on fixing this issue. -- 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

17 years

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-7093) communitcation from scriptlet to jsf managed bean is not working

by anil kumar (JIRA)

communitcation from scriptlet to jsf managed bean is not working ---------------------------------------------------------------- Key: JBAS-7093 URL: https://jira.jboss.org/jira/browse/JBAS-7093 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JSF Affects Versions: JBossAS-5.1.0.GA Environment: windows Reporter: anil kumar Assignee: Stan Silvert Here is the sample code. <% for (int i = 1; i < 5; i++) { HeaderBean header = new HeaderBean(); header.setScreenID("" + i); application.setAttribute("HeaderBean", header); %> <h:outputText value="#{HeaderBean.screenID}"> </h:outputText> <%}%> its always displaying the last value,the out put is "4444" instead of "1234". Is this expected behavior? -- 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

17 years

2
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1858) NPE if in resource-env-ref no injection target is specified

by Wolfgang Knauf (JIRA)

NPE if in resource-env-ref no injection target is specified ----------------------------------------------------------- Key: EJBTHREE-1858 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1858 Project: EJB 3.0 Issue Type: Bug Affects Versions: 1.1.7 Reporter: Wolfgang Knauf Attachments: ResourceEnvRefNPE.jar If an ENC entry for java:/comp/EJBContext is declared and NO injection target is specified, this results in a NPE. <resource-env-ref> <resource-env-ref-name>EnvNameOfSessionContext</resource-env-ref-name> <resource-env-ref-type>javax.ejb.SessionContext</resource-env-ref-type> <mapped-name>java:comp/EJBContext</mapped-name> </resource-env-ref> The exception is: ... Caused by: java.lang.NullPointerException at org.jboss.injection.InjectionUtil.createInjectors(InjectionUtil.java:105) at org.jboss.injection.ResourceHandler.loadXmlResourceEnvRefs(ResourceHandler.java:227) at org.jboss.injection.ResourceHandler.loadXml(ResourceHandler.java:343) at org.jboss.ejb3.EJBContainer.processMetadata(EJBContainer.java:597) at org.jboss.ejb3.Ejb3Deployment.processEJBContainerMetadata(Ejb3Deployment.java:434) at org.jboss.ejb3.Ejb3Deployment.start(Ejb3Deployment.java:543) ... 69 more Looking at the code in ResourceHandler.loadXmlResourceEnvRefs, this is the only place where the check "if(envRef.getInjectionTargets() != null)" is missing ;-). I will attach a sample. -- 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

17 years

2
4
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1861) Upgrade microcontainer to 2.0.8.GA

by jaikiran pai (JIRA)

Upgrade microcontainer to 2.0.8.GA ---------------------------------- Key: EJBTHREE-1861 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1861 Project: EJB 3.0 Issue Type: Thirdparty Change Affects Versions: 1.1.8 Reporter: jaikiran pai Assignee: jaikiran pai In order to be able to use the @DisableAOP feature in MC, we need to upgrade to this latest version of MC. -- 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

17 years

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