November 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBVFS-79) VFSPermission should imply a FilePermission

by Anil Saldhana (JIRA)

VFSPermission should imply a FilePermission ------------------------------------------- Key: JBVFS-79 URL: https://jira.jboss.org/jira/browse/JBVFS-79 Project: JBoss VFS Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Anil Saldhana Adrian says: ============================== vfs permissions implying other permissions. e.g. permission to vfsfile:/something/in/my/codesource should imply http://java.sun.com/j2se/1.4.2/docs/api/java/security/Permission.html#imp... permission to file:/something/in/my/codesource and using the java.io.File api to access it. see for example FileURLConnection /** * Return a permission for reading of the file */ public Permission getPermission() throws IOException { return new FilePermission(file.getPath(), "read"); } This is also important for making sure you can't use vfs urls to open connections to things you are not allowed to access. Although I think in that case, the actual vfs implementation code will barf later if you don't have the permission? =========================================== -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (JBVFS-78) VFSPermission

by Anil Saldhana (JIRA)

VFSPermission ------------- Key: JBVFS-78 URL: https://jira.jboss.org/jira/browse/JBVFS-78 Project: JBoss VFS Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Anil Saldhana Extend the FilePermission class. JBNAME-8 is a reference. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-1797) Migrate Ruleflow from 4.0 to 5.0 during compilation

by Nimesh Muley (JIRA)

Migrate Ruleflow from 4.0 to 5.0 during compilation --------------------------------------------------- Key: JBRULES-1797 URL: https://jira.jboss.org/jira/browse/JBRULES-1797 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-compiler (flow) Affects Versions: 5.0.0.M2 Reporter: Nimesh Muley Assignee: Mark Proctor Priority: Critical Fix For: 5.0.0.M3 The format of rule flow has changed from 4.0 to 5.0. Due to this, ruleflows are not backward compatible. If the ruleflow is of version 4.0 and automatic migration flag is switched on in 5.0 then the rule flow should be migrated to 5.0 before executing it. Thus having backward support for ruleflows in 5.0 release. -- 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, 7 months

2
4
0 / 0

[JBoss JIRA] Created: (JBRULES-1836) Cannot rename status in Guvnor

by Jaroslaw Kijanowski (JIRA)

Cannot rename status in Guvnor ------------------------------ Key: JBRULES-1836 URL: https://jira.jboss.org/jira/browse/JBRULES-1836 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-guvnor Affects Versions: 5.0.0.M2 Reporter: Jaroslaw Kijanowski Assignee: Michael Neale >From the Administration panel I create a new status, select it and try to rename it. I would expect a dialog box where I could enter the name, however I end up with: "The call failed on the server; see server log for details" 2008-11-11 06:59:04,884 INFO [STDOUT] INFO 11-11 06:59:04,883 (ServiceImplementation.java:renameState:1044) USER:admin RENAMING state: [qwe] to [] 2008-11-11 06:59:04,886 INFO [STDOUT] ERROR 11-11 06:59:04,885 (RulesRepository.java:renameState:1153) javax.jcr.ItemExistsException: /drools:repository/drools:state_area 2008-11-11 06:59:04,886 ERROR [org.apache.catalina.core.ContainerBase] Exception while dispatching incoming RPC call com.google.gwt.user.server.rpc.UnexpectedException: Service method 'public abstract void org.drools.guvnor.client.rpc.RepositoryService.renameState(java.lang.String,java.lang.String) throws com.google.gwt.user.client.rpc.SerializableException' threw an unexpected exception: org.drools.repository.RulesRepositoryException: javax.jcr.ItemExistsException: /drools:repository/drools:state_area at com.google.gwt.user.server.rpc.RPC.encodeResponseForFailure(RPC.java:360) at com.google.gwt.user.server.rpc.RPC.invokeAndEncodeResponse(RPC.java:546) at com.google.gwt.user.server.rpc.RemoteServiceServlet.processCall(RemoteServiceServlet.java:164) at com.google.gwt.user.server.rpc.RemoteServiceServlet.doPost(RemoteServiceServlet.java:86) at javax.servlet.http.HttpServlet.service(HttpServlet.java:637) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.seam.web.ContextFilter$1.process(ContextFilter.java:42) at org.jboss.seam.servlet.ContextualHttpServletRequest.run(ContextualHttpServletRequest.java:53) at org.jboss.seam.web.ContextFilter.doFilter(ContextFilter.java:37) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:182) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:580) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:595) Caused by: org.drools.repository.RulesRepositoryException: javax.jcr.ItemExistsException: /drools:repository/drools:state_area at org.drools.repository.RulesRepository.renameState(RulesRepository.java:1154) at org.drools.guvnor.server.ServiceImplementation.renameState(ServiceImplementation.java:1045) 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:585) at org.jboss.seam.util.Reflections.invoke(Reflections.java:22) at org.jboss.seam.intercept.RootInvocationContext.proceed(RootInvocationContext.java:31) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:56) at org.jboss.seam.transaction.RollbackInterceptor.aroundInvoke(RollbackInterceptor.java:28) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) at org.jboss.seam.core.BijectionInterceptor.aroundInvoke(BijectionInterceptor.java:39) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) at org.jboss.seam.core.MethodContextInterceptor.aroundInvoke(MethodContextInterceptor.java:44) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) at org.jboss.seam.security.SecurityInterceptor.aroundInvoke(SecurityInterceptor.java:138) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) at org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:107) at org.jboss.seam.intercept.JavaBeanInterceptor.interceptInvocation(JavaBeanInterceptor.java:166) at org.jboss.seam.intercept.JavaBeanInterceptor.invoke(JavaBeanInterceptor.java:102) at org.drools.guvnor.server.ServiceImplementation_$$_javassist_7.renameState(ServiceImplementation_$$_javassist_7.java) at org.drools.guvnor.server.RepositoryServiceServlet.renameState(RepositoryServiceServlet.java:136) 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:585) at com.google.gwt.user.server.rpc.RPC.invokeAndEncodeResponse(RPC.java:527) ... 27 more Caused by: javax.jcr.ItemExistsException: /drools:repository/drools:state_area at org.apache.jackrabbit.core.SessionImpl.move(SessionImpl.java:1011) at org.drools.repository.RulesRepository.renameState(RulesRepository.java:1149) ... 53 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, 7 months

3
4
0 / 0

[JBoss JIRA] Created: (JGRP-861) GossipRouter: make backlog for server socket connections configurable

by Bela Ban (JIRA)

GossipRouter: make backlog for server socket connections configurable --------------------------------------------------------------------- Key: JGRP-861 URL: https://jira.jboss.org/jira/browse/JGRP-861 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Bela Ban Priority: Minor Fix For: 2.6.7, 2.7 The backlog for new ServerSocket(port, 50) is currently hard coded. Make it configurable via setter. -- 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, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-6181) cannot secure jmx invoker service

by Aleksandar Kostadinov (JIRA)

cannot secure jmx invoker service --------------------------------- Key: JBAS-6181 URL: https://jira.jboss.org/jira/browse/JBAS-6181 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Security Affects Versions: JBossAS-5.0.0.CR2 Environment: AS 5 trunk r80638 Reporter: Aleksandar Kostadinov Assignee: Anil Saldhana Fix For: JBossAS-5.0.0.GA When I edit deploy/jmx-invoker-service.xml and uncomment the AuthenticationInterceptor one can still access the server without a password. (tried with shutdown.sh) When I add AuthorizationInterceptor and try to shutdown server (no matter with or without a password) I get: Exception in thread "main" java.lang.SecurityException: No active Subject found, add th AuthenticationInterceptor ... (for full stack trace, see the forum thread) Seems that for some reason AuthenticationInterceptor is not working. Here is how I the interceptors look like: <interceptors>  <interceptor code="org.jboss.jmx.connector.invoker.AuthenticationInterceptor" securityDomain="java:/jaas/jmx-console"/> <interceptor code="org.jboss.jmx.connector.invoker.AuthorizationInterceptor" authorizingClass="org.jboss.jmx.connector.invoker.RolesAuthorization"></interceptor>  <interceptor code="org.jboss.jmx.connector.invoker.SerializableInterceptor" policyClass="StripModelMBeanInfoPolicy"/> </interceptors> -- 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, 7 months

3
7
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1581) Inherited EJB 2.1 beans don't get their init method called

by Carlo de Wolf (JIRA)

Inherited EJB 2.1 beans don't get their init method called ---------------------------------------------------------- Key: EJBTHREE-1581 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1581 Project: EJB 3.0 Issue Type: Bug Components: core Affects Versions: 1.0.0-Beta6 Reporter: Carlo de Wolf Assignee: Carlo de Wolf Priority: Critical Fix For: 1.0.0-Beta7 -- 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, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-6192) mail-ra call getNewMessages on pop3 folder, which always return false

by peter andersen (JIRA)

mail-ra call getNewMessages on pop3 folder, which always return false --------------------------------------------------------------------- Key: JBAS-6192 URL: https://jira.jboss.org/jira/browse/JBAS-6192 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JCA service Affects Versions: JBossAS-4.2.3.GA Environment: Mac os, java 1.5 Reporter: peter andersen Assignee: Jesper Pedersen The org.jboss.resource.adapter.mail.inflow.MailFolder calls javax.mail.Folder.hasNewMessages() to check for new messages. POP3Folder instances allways return false on this request, see: http://java.sun.com/products/javamail/javadocs/com/sun/mail/pop3/POP3Fold... A quick fix/work around: public Message[] getNewMessages() throws Exception { Message msgs[] = {}; /* This does not seem to be the most reliable new msg check. This should probably be unread msgs with the msgs marked as read on successful delivery. */ if( folder.hasNewMessages() ) { int newCount = folder.getNewMessageCount(); int msgCount = folder.getMessageCount(); msgs = folder.getMessages(msgCount - newCount + 1, msgCount); return msgs; } // Special handling of POP3, hasNewMessages() always returns false. if (protocol.equalsIgnoreCase("pop3")) { msgs = folder.getMessages(); return msgs; } return msgs; } -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-6190) repository based ProfileService hot deployment is not working

by Scott M Stark (JIRA)

repository based ProfileService hot deployment is not working ------------------------------------------------------------- Key: JBAS-6190 URL: https://jira.jboss.org/jira/browse/JBAS-6190 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: ProfileService, VFS Affects Versions: JBossAS-5.0.0.CR2 Reporter: Scott M Stark Assignee: Scott M Stark Fix For: JBossAS-5.0.0.GA If the repository profile service is made the default, hot deployment is seen to not work. The jbossas testsuite fails because the minimal configuration shutdown relies on deployment of the shutdown.sar. Steps: 1. Copy the server/src/etc/conf/default/profile-repository.xml to server/src/etc/conf/default 2. build the server 3. start the minimal configuration 4. Copy the testsuite output/lib/shutdown.sar to the minimal config deploy directory: [starksm@succubus testsuite]$ cp output/lib/shutdown.sar ../build/output/jboss-5.0.0.GA/server/minimal/deploy [starksm@succubus testsuite]$ ls -l ../build/output/jboss-5.0.0.GA/server/minimal/deploy total 8 -rw-rw-r-- 1 starksm starksm 3071 Nov 11 21:19 shutdown.sar the server should shutdown in the next hot deployment cycle. -- 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, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1205) EJB3 Plugin Installer X-Platform Support

by Andrew Lee Rubinger (JIRA)

EJB3 Plugin Installer X-Platform Support ---------------------------------------- Key: EJBTHREE-1205 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1205 Project: EJB 3.0 Issue Type: Task Reporter: Andrew Lee Rubinger Assigned To: Andrew Lee Rubinger Fix For: AS 5.0.0.CR1 Ensure EJB3 Plugin Installer works X-Platform -- 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, 7 months

2
12
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2008