November 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-6212) PrincipalSessionAttributeFilter does not forward request to next filter/resource in chain.

by Micah Cleveland (JIRA)

PrincipalSessionAttributeFilter does not forward request to next filter/resource in chain. ------------------------------------------------------------------------------------------- Key: JBAS-6212 URL: https://jira.jboss.org/jira/browse/JBAS-6212 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.2.3.GA Environment: Windows, JBoss 4.2.3, Spring MVC Reporter: Micah Cleveland I noticed that when the PrincipalSessionAttributeFilter is enabled within JBOSS and you try to navigate in a browser to a web app resource, the resource never gets call because the filter does not foward to the next filter/resource in the chain. I was hoping by enabling this filter I would have a way to call my custom login modules logout operation on session expiration. At a minimum enable me to get the principal name so that I can make appropriate database logout calls. It was my understanding that the PrincipalSessionAttributeFilter would place the Principal within the session so that I could access it within a SessionListener when the session is destroyed. -- 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

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-5817) SystemPropertiesService doesn't replace refs to other properties

by Naveen Malik (JIRA)

SystemPropertiesService doesn't replace refs to other properties ---------------------------------------------------------------- Key: JBAS-5817 URL: https://jira.jboss.org/jira/browse/JBAS-5817 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Other Affects Versions: JBossAS-4.2.3.GA Reporter: Naveen Malik Trying to use the SystemPropertiesService to load a properties file where some of the properties in the file have values that reference other properties. For example: my.first.property=someValue my.second.property=${my.first.property} The value of my.second.property is not resolved to "someValue". -- 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

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-4460) Jboss Password Encryption Security Flaw

by Scott Kesecki (JIRA)

Jboss Password Encryption Security Flaw --------------------------------------- Key: JBAS-4460 URL: http://jira.jboss.com/jira/browse/JBAS-4460 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Security Affects Versions: JBossAS-4.0.3 SP1 Reporter: Scott Kesecki Assigned To: Scott M Stark The Jboss salt to encrypt and decrypt passwords are stored in clear text in the jboss source that can be downloaded by everyone. Anyone that has a basic understanding of how java works can take the source tree get the class definition that has the password encryption and turn it into a a password decryption 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

15 years

2
1
0 / 0

[JBoss JIRA] Created: (JBREM-904) Remoting 1/2 compatibility layer

by David Lloyd (JIRA)

Remoting 1/2 compatibility layer -------------------------------- Key: JBREM-904 URL: http://jira.jboss.com/jira/browse/JBREM-904 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Reporter: David Lloyd Fix For: Remoting 3 M3 A protocol compatibility layer needs to be developed that allows a Remoting 3 server to respond to a Remoting 1/2 request, and also that allows a Remoting 3 client to connect to a Remoting 1/2 server. This will be required before integration with AS5 can be considered. Another item worth exploration is looking into providing a Remoting 1/2 compatibilty API that allows legacy applications to use the newer transports. -- 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

15 years

1
7
0 / 0

[JBoss JIRA] Created: (EJBTHREE-941) merge issue when removing from OneToMany in detached state (layered architecture)

by Rico Apfelbeck (JIRA)

merge issue when removing from OneToMany in detached state (layered architecture) --------------------------------------------------------------------------------- Key: EJBTHREE-941 URL: http://jira.jboss.com/jira/browse/EJBTHREE-941 Project: EJB 3.0 Issue Type: Bug Affects Versions: AS 4.2.0 CR1 Environment: 13:37:59,625 INFO [ServerInfo] Java version: 1.5.0_09,Sun Microsystems Inc. 13:37:59,625 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 1.5.0_09-b01,Sun Microsystems Inc. 13:37:59,625 INFO [ServerInfo] OS-System: Windows XP 5.1,x86 Reporter: Rico Apfelbeck We work on a client-server environment with a webstart-client with an own JVM. Only the server has access to the JPA. POJOs are transfered from client to server and back. Our Issue occurs in the following workflow: - We get an Object A on the server from the Entitymanager and transfer it to the client. - This Object has a OneToMany-relation to some Objects B (fetchtype: EAGER, cascade: ALL). In B we have a reference to A. - On the client we remove in A some B from the Set, for example with clean() and transfer A back to the server. - We merge A on the server. - There is no exception thrown. The returned A from the merge-call does not contain any B, reloading A by Id results in a restored list containing the removed Bs. While added new Bs to A are stored correctly, removing them doesn't result in the deletion of the removed Bs from the database. Updating B in the List in A results in updated Bs when merging A. Only the removal causes problems. We assume that the problem comes from checking the now empty list against the database. Reloading A before merging in the server and manually compare the List of Bs, using EntityManager.remove() when neccesary. helps our case, but that's not the way it shoud be. :) -- 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

15 years

4
4
0 / 0

[JBoss JIRA] Created: (JBAS-5869) wsprovide.bat lack jbossws-client.jar in classpath

by Lauri Sax (JIRA)

wsprovide.bat lack jbossws-client.jar in classpath -------------------------------------------------- Key: JBAS-5869 URL: https://jira.jboss.org/jira/browse/JBAS-5869 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Other Affects Versions: JBossAS-4.2.3.GA Environment: windows vista java version "1.6.0_07" jboss 4.2.3.GA Reporter: Lauri Sax Priority: Minor On attempt to generate wsdl for existing WS wsprovide.bat throws an exception claiming org.jboss.ws.tools.jaxws.impl.JBossWSProviderFactoryImpl does not exist. "C:/Program Files/jboss-4.2.3.GA/bin/wsprovide.bat" --classpath "project_class_path" -wsdl test.SampleWebService JBossWS-Metro stack deployed Exception in thread "main" java.lang.IllegalStateException: Failed to load: org.jboss.ws.tools.jaxws.impl.JBossWSProviderFactoryImpl at org.jboss.wsf.spi.util.ServiceLoader.loadDefault(ServiceLoader.java:205) at org.jboss.wsf.spi.util.ServiceLoader.loadFromSystemProperty(ServiceLoader.java:138) at org.jboss.wsf.spi.util.ServiceLoader.loadService(ServiceLoader.java:68) at org.jboss.wsf.spi.tools.WSContractProvider.newInstance(WSContractProvider.java:65) at org.jboss.wsf.spi.tools.cmd.WSProvide.generate(WSProvide.java:170) at org.jboss.wsf.spi.tools.cmd.WSProvide.main(WSProvide.java:77) Caused by: java.lang.ClassNotFoundException: org.jboss.ws.tools.jaxws.impl.JBossWSProviderFactoryImpl at java.net.URLClassLoader$1.run(URLClassLoader.java:200) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at org.jboss.wsf.spi.util.ServiceLoader.loadDefault(ServiceLoader.java:200) ... 5 more -- 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

3
2
0 / 0

[JBoss JIRA] Created: (JBREFLECT-46) Fix NestedPropertyInfo::set

by Ales Justin (JIRA)

Fix NestedPropertyInfo::set --------------------------- Key: JBREFLECT-46 URL: https://jira.jboss.org/jira/browse/JBREFLECT-46 Project: JBoss Reflection Issue Type: Task Components: BeanInfo Affects Versions: JBossReflection.2.0.2.GA Reporter: Ales Justin Assignee: Ales Justin Fix For: JBossReflection.2.2.0-Beta1 NestedPropertyInfo should use TypeInfo::isInstance + TypeInfo::convertValue. -- 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

2
4
0 / 0

[JBoss JIRA] Created: (JBREFLECT-47) Set upper name to NestedPropertyInfo

by Ales Justin (JIRA)

Set upper name to NestedPropertyInfo ------------------------------------ Key: JBREFLECT-47 URL: https://jira.jboss.org/jira/browse/JBREFLECT-47 Project: JBoss Reflection Issue Type: Task Components: BeanInfo Affects Versions: JBossReflection.2.0.2.GA Reporter: Ales Justin Assignee: Ales Justin Fix For: JBossReflection.2.2.0-Beta1 -- 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

2
2
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-122) Use the ScopedClassPool from javassist

by Adrian Brock (JIRA)

Use the ScopedClassPool from javassist -------------------------------------- Key: JBMICROCONT-122 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-122 Project: JBoss MicroContainer Issue Type: Task Components: BeanInfo Affects Versions: JBossMC_2_0_0 Beta Reporter: Adrian Brock The javassist reflection utilities use the original shared classpool. This does not understand classloaders. This should be updated to use the newer ScopedClassPool from javassist. -- 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

15 years

5
8
0 / 0

[JBoss JIRA] Created: (JBXB-100) Add support for unmarshal(Source)

by Thomas Diesler (JIRA)

Add support for unmarshal(Source) --------------------------------- Key: JBXB-100 URL: http://jira.jboss.com/jira/browse/JBXB-100 Project: JBoss XML Binding (JBossXB) Issue Type: Feature Request Affects Versions: JBossXB-1.0.0.CR9 Reporter: Thomas Diesler JBossWS fragments the incomming SOAP message into Source elements. Currently its using DOMSource. The interface to JBossXB is inefficient since the DOMSource needs to be serialized into a String and then into an InputStream. It would be much better if JBossXB could unmarshall the Source directly. Later we could transparently switch from DOMSource to some more efficient implementation. -- 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

15 years, 1 month

4
7
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2008