February 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMESSAGING-777) Revise creation of Object*Stream on Remoting/our Marshallers

by Clebert Suconic (JIRA)

Revise creation of Object*Stream on Remoting/our Marshallers ------------------------------------------------------------ Key: JBMESSAGING-777 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-777 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.2.0.Beta2 Reporter: Clebert Suconic Assigned To: Ovidiu Feodorov Fix For: 1.2.0.CR1 We have requested to create a new Object*Stream on every request... delegating the Object*Stream creation to the marshaller. A Object*Stream should be reused.. and created only once... Especially if using JavaSerialization, since : I - its creation is considered expensive II - Object*Stream has a weird internal buffer. overusing that stream creationg might cause intermitent errors IMO. It would be better if we could avoid recreating the streaming every time. -- 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, 2 months

3
3
0 / 0

[JBoss JIRA] Created: (JBAS-4102) Remove jbossretro-rt.jar and jboss-backport-concurrent.jar dependencies

by Dimitris Andreadis (JIRA)

Remove jbossretro-rt.jar and jboss-backport-concurrent.jar dependencies ----------------------------------------------------------------------- Key: JBAS-4102 URL: http://jira.jboss.com/jira/browse/JBAS-4102 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Other Reporter: Dimitris Andreadis Assigned To: Dimitris Andreadis Fix For: JBossAS-4.2.0.CR1 Using jdk5 as the base, there shouldn't be any need for retro weaving. -- 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, 2 months

1
1
0 / 0

[JBoss JIRA] Updated: (JBAS-1824) JACC: <role-name>*</role-name> in web.xml should allow configurable authorization bypass

by Anil Saldhana (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1824?page=all ] Anil Saldhana updated JBAS-1824: -------------------------------- Summary: JACC: <role-name>*</role-name> in web.xml should allow configurable authorization bypass (was: JACC: <role-name>*</role-name> in web.xml) Priority: Major (was: Minor) > JACC: <role-name>*</role-name> in web.xml should allow configurable authorization bypass > ---------------------------------------------------------------------------------------- > > Key: JBAS-1824 > URL: http://jira.jboss.com/jira/browse/JBAS-1824 > Project: JBoss Application Server > Issue Type: Feature Request > Components: Security > Affects Versions: JBossAS-4.0.2 Final > Environment: - > Reporter: Roland R?z > Assigned To: Anil Saldhana > Fix For: JBossAS-4.2.0.CR1 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > In some cases I wish to do authentication without authorisation. For example everybody has access to my web-resource, but I want to know who she/he is. > Therefore the accessing user must login. > So my web.xml contains the following snippet: > ... > <security-constraint> > <web-resource-collection> > <web-resource-name>Protected Helloworld example</web-resource-name> > <description/> > <url-pattern>/servlet/HelloWorldExample</url-pattern> > <http-method>POST</http-method> > <http-method>GET</http-method> > </web-resource-collection> > <auth-constraint> > <role-name>*</role-name> > </auth-constraint> > </security-constraint> > <login-config> > <auth-method>BASIC</auth-method> > <realm-name>public</realm-name> > </login-config> > ... > The web app runs with this configuration in Tomcat 5.5.8 standalone but not in Jboss. > To run it in Jboss I have to add the following element: > <security-role> > <role-name>aRole</role-name> > </security-role> > The JACC spec (section 3.1.3.1, paragraph 3)states : > " ?. When an auth-constraint names the reserved role-name, "*", all of the patterns in the containing security-constraint must be combined with all of the roles defined in the web application." > JBoss implemented this by combining all of the patterns with all roles defined in the web.xml and assumes that each role has to be defined in the web.xml. > But the web applications roles are probably defined in other files than the web.xml. In our case we use JACC with an external authentication provider. And each time, the roles changes, I also would have to modify the web.xml. > It is desirable if the auth-contraint with the role-name "*" acceppts "all" roles and not only those that are defined in the web.xml. > Or is this a JACC spec issue? > Regards, > Andrea -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAOP-360) DeadLock when multiple threads are loading aspects

by Clebert Suconic (JIRA)

DeadLock when multiple threads are loading aspects -------------------------------------------------- Key: JBAOP-360 URL: http://jira.jboss.com/jira/browse/JBAOP-360 Project: JBoss AOP Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 1.5.3.GA, 1.5.2.GA, 1.5.1.GA, 1.5.0.GA Reporter: Clebert Suconic Fix For: 1.5.4.GA, 2.0.0.alpha1 When multiple threads are loading aspect there is a possibility of a dead lock, of locks boucing between a WeakHashMap lock and ClassAdvisor. You will need a multiple thread test loading Aspects simultaneously. Tim Fox has found this as part of JBMESSAGING-797 -- 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, 2 months

3
8
0 / 0

[JBoss JIRA] Updated: (JBAS-2831) Allow run-as identity propagation across servers with configurable trust

by Anil Saldhana (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2831?page=all ] Anil Saldhana updated JBAS-2831: -------------------------------- Summary: Allow run-as identity propagation across servers with configurable trust (was: Allow run-as indentity propagation across servers with configurable trust) This is part of the Security Context work. > Allow run-as identity propagation across servers with configurable trust > ------------------------------------------------------------------------ > > Key: JBAS-2831 > URL: http://jira.jboss.com/jira/browse/JBAS-2831 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Security > Affects Versions: JBossAS-4.0.4RC1 > Reporter: Scott M Stark > Assigned To: Anil Saldhana > Fix For: JBossAS-5.0.1.CR1 > > > Look to provide propagation of the run-as identity across server calls with control over how the target server trusts this call is correct. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPORTAL-832) CMS saves pages in native encoding (ISO-8859-1 or Cp1251) but retrieve it in UTF-8. then national leters are damaged

by Roy Russo (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-832?page=all ] Roy Russo updated JBPORTAL-832: ------------------------------- Assignee: Sohil Shah (was: Roy Russo) > CMS saves pages in native encoding (ISO-8859-1 or Cp1251) but retrieve it in UTF-8. then national leters are damaged > -------------------------------------------------------------------------------------------------------------------- > > Key: JBPORTAL-832 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-832 > Project: JBoss Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Portal CMS > Environment: jboss4.0.3sp1 > Reporter: Mike Khlu > Assigned To: Sohil Shah > Attachments: ??????? ? ???-??? ???????.PNG, issue-screenshot.GIF, jbossportali18nbug.GIF, russian-in-1251.txt, russian-in-utf8.html > > > When I input ru-characters in the text area it has been puted into table in native encoding (cp1251) - !!! not UTF-8. But pages are sends in UTF-8, and it damaged. > I think that I have to encode the request in UTF-8 ??? > --------------------------------------------- > create file.html in Ru (in cms admin) with this text > abc??? > then look at the last record of JBP_CMS_VERSION_BINVAL > (six bytes in BINVAL_DATA field): > 61 62 63 e0 e1 e2 > it is cp1251 encoding !!!! > why this text non unicoded ??? > then when i retrive it i have - 'abc???' > I think that problem isn't in ContentTypeInterceptor because it succefully > sets UTF8, because localized resources seems right (in russian). > may be it is need to store text in CLobs insdead blobs ??? (a use Derby) or customize Jackrabbit ??? > ----------------------------------------------------------- > but when I upload file on UTF-8 with russian characters - all correct. > I think that cms saves the content in one byte encoding (cp1250 or same). -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPORTAL-730) "Copy" should copy the live revision

by Roy Russo (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-730?page=all ] Roy Russo updated JBPORTAL-730: ------------------------------- Assignee: Sohil Shah (was: Roy Russo) > "Copy" should copy the live revision > ------------------------------------ > > Key: JBPORTAL-730 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-730 > Project: JBoss Portal > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Portal CMS > Affects Versions: 2.6.Beta1 > Reporter: Thomas Heute > Assigned To: Sohil Shah > Priority: Optional > > The current "copy" feature using Jackrabbit Workspace.copy() seems to copy the latest revision and only that one. > Jackrabbit implementation won't help here (since it should be faster to do it at this level) > If we decide to copy a unique revision we should copy the Live version. (can be different from the latest) > Now the question is: should we copy all revisions or only the live one ? -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPORTAL-731) File with no "live" version

by Roy Russo (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-731?page=all ] Roy Russo updated JBPORTAL-731: ------------------------------- Assignee: Sohil Shah (was: Roy Russo) > File with no "live" version > --------------------------- > > Key: JBPORTAL-731 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-731 > Project: JBoss Portal > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Portal CMS > Affects Versions: 2.6 Final > Reporter: Thomas Heute > Assigned To: Sohil Shah > > There is probably a need to avoid having a "live" version of a content, that could be used to: > 1) Save a file without publishing it yet (because it is on-going work for example) > 2) Write a file to be published later. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1225) Remove JSF from admin console

by Roy Russo (JIRA)

Remove JSF from admin console ----------------------------- Key: JBPORTAL-1225 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1225 Project: JBoss Portal Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Portal Core Affects Versions: 2.6.Beta1 Reporter: Roy Russo Assigned To: Roy Russo Fix For: 2.6.Beta1 Reuse beans and do pure jsp -- 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, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-3431) AuthorizationInterceptor throwing ArrayIndexOutOfBoundsException

by Anil Saldhana (JIRA)

AuthorizationInterceptor throwing ArrayIndexOutOfBoundsException ---------------------------------------------------------------- Key: JBAS-3431 URL: http://jira.jboss.com/jira/browse/JBAS-3431 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JMX, Security Affects Versions: JBossAS-4.0.4.GA Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: JBossAS-5.0.0.Beta, JBossAS-4.0.5.CR1 As Originally reported in JBJMX-97, the user says: ========================================================================================== I have secured the jmx-invoker-service using JAAS and the standard UsersRolesLoginModule. I am able to authenticate (basic authentication) through the web UI and manage the console using the same login config. I am getting a remote connection to the JMX server from an InitialContext that is populated with the user name and password: env.put(Context.SECURITY_PRINCIPAL, userName); env.put(Context.SECURITY_CREDENTIALS, password); Then I look up the MBeanServerConnection and try to get the MBeanInfo MBeanServerConnection server = lookup("jmx/invoker/RMIAdaptor", MBeanServerConnection.class); ObjectName name = new ObjectName(theName); MBeanInfo info = server.getMBeanInfo(name); At this point the server throws an ArrayIndexOutOfBoundsException from org.jboss.jmx.connector.invoker.AuthorizationInterceptor line 107. If I try and set an attribute: server.setAttribute(name, new Attribute("searchText", searchText)); I get instead at the same line: java.lang.ClassCastException: javax.management.Attribute at org.jboss.jmx.connector.invoker.AuthorizationInterceptor.invoke(AuthorizationInterceptor.java:107) at org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:108) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) ========================================================================================== -- 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, 2 months

3
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 February 2007