August 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Commented: (JBRULES-1112) drools-jbrms.war does not work with JBoss4.0.5 bundled with Jetty6.1.1

by Fernando Meyer (JIRA)

[ http://jira.jboss.com/jira/browse/JBRULES-1112?page=comments#action_12373559 ] Fernando Meyer commented on JBRULES-1112: ----------------------------------------- Wailting for user feedback > drools-jbrms.war does not work with JBoss4.0.5 bundled with Jetty6.1.1 > ---------------------------------------------------------------------- > > Key: JBRULES-1112 > URL: http://jira.jboss.com/jira/browse/JBRULES-1112 > Project: JBoss Rules > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: drools-brms > Affects Versions: 4.0.0.GA > Environment: Windows XP Professional 2002 service pack 2, JDK1.6.0 > Reporter: Huishan Zhou > Assigned To: Fernando Meyer > Priority: Critical > Fix For: 4.0.1 > > > The bugs of the following test is based on running drools-jbrms.war > on JBoss4.0.5 bundled with Jetty6.1.1. (No bugs on running this war in > JBoss4.0.5 bundled with Tomcat5.5) > drools-jbrms.war is extracted from drools-4.0.0-brms.zip > which is downloaded from > http://labs.jboss.com/drools/downloads.html on 08/21/2007. > (I also tested drools-jbrms.war extracted from > jbossrules-4.0.0.12865MR3-brms.zip > downloaded from > http://labs.jboss.com/jbossrules/downloads > on 08/20/2007. Identical error message.) > (1) during starting of JBoss, it throws the > ClassNotFoundException, javax/faces/context/FacesContext, > and in web browser console, it showed that drools-jbrms deployment > failed. > We have fixed this exception by adding two jar files, jsf-impl.jar > and jsf-api.jar, to WEB-INF/lib > (2) After fixing errors in (1) we can start JBoss. And we can go > to > http://localhost:8080/drools-jbrms/drools-jbrms/org.drools.brms.JBRMS/ > welcome.jsp > and > http://localhost:8080/drools-jbrms/drools-jbrms/org.drools.brms.JBRMS/ > JBRMS.html with the showup of the code of JBRMS.html itself, not > the user name and password form that was showed up in the JBoss4.0.5 > bundled with Tomcat5.5 > and > we can also go to > http://localhost:8080/drools-jbrms/drools-jbrms/org.drools.brms.JBRMS/ > login.jsp (What is the purpose of this page?) > If we try to go to > http://localhost:8080/drools-jbrms/drools-jbrms/org.drools.brms.JBRMS/ > JBRMS.jsp > we got error. We opened JBRMS.jsp, we found that it missed one very > basic line (but this missing didn't cause any trouble while testing in > JBoss bundled with Tomcat ?) > <%@ page language="java" import="org.jboss.seam.security.Identity" > pageEncoding="ISO-8859-1"%> > After adding this line to the code. We still got errors: > = = = = errors message = = = = > org.apache.jasper.JasperException: Unable to compile class for JSP > Generated servlet error: > Only a type can be imported. org.jboss.seam.security.Identity > resolves to a package > An error occurred at line: 11 in the jsp file: > /drools-jbrms/org.drools.brms.JBRMS/JBRMS.jsp > Generated servlet error: > Identity cannot be resolved to a type > An error occurred at line: 10 in the jsp file: > /drools-jbrms/org.drools.brms.JBRMS/JBRMS.jsp > Generated servlet error: > org.jboss.seam.security.Identity cannot be resolved to a type > = = = = = = = = = = = = = = = = = = = > We have checked that the jar file for the class > org.jboss.seam.security.Identity is in the WEB-INF/lib of > drools-jbrms.war. -- 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

18 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-1117) DSL support for multiple mvel comparasions (like || ==) in several lines.

by Felipe Piccolini (JIRA)

DSL support for multiple mvel comparasions (like || ==) in several lines. ------------------------------------------------------------------------- Key: JBRULES-1117 URL: http://jira.jboss.com/jira/browse/JBRULES-1117 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Drl Parser/Builder, Eclipse IDE Affects Versions: 4.0.0.GA Environment: DSL editor and eclipse IDE. Reporter: Felipe Piccolini Assigned To: Mark Proctor Fix For: FUTURE It whould be nice if DSL supports multiple lines for multiple comparison (mvel expression) against the same attribute. Like this: DLS: A Person - having age equals to 10 - or equals to 15 - or greather than 20 DRL: p: Person( age == 10 || == 15 || > 20) Right now, the " - <expression>" put a 'comma' at the end of the line making this: p: Person( age == 10, || == 15, || > 20) What throws errors... Is it possible to do that? I love the || == <value> thing in each line... Thanks. -- 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

18 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-4625) Connection leak if failure to setup connection in jms inbound resource adapter

by Adrian Brock (JIRA)

Connection leak if failure to setup connection in jms inbound resource adapter ------------------------------------------------------------------------------ Key: JBAS-4625 URL: http://jira.jboss.com/jira/browse/JBAS-4625 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JMS service Affects Versions: JBossAS-4.2.1.GA Reporter: Adrian Brock Assigned To: Adrian Brock Fix For: JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA The jms inbound resource adapter is leaking connections if there is an error setting up the connection. In pseudo code in setup[Queue|Topic]Connection { ... + try + { if (clientID != null) result.setClientID(clientID); result.setExceptionListener(this); log.debug("Using topic connection " + result); return result; + } + catch (Throwable t) + { + result.close(); + throw t; + } } -- 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

18 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-4624) Parse Role Name from Role DN

by Mike Millson (JIRA)

Parse Role Name from Role DN ---------------------------- Key: JBAS-4624 URL: http://jira.jboss.com/jira/browse/JBAS-4624 Project: JBoss Application Server Issue Type: Patch Security Level: Public (Everyone can see) Components: Security Affects Versions: JBossAS-4.0.5.GA Reporter: Mike Millson Assigned To: Anil Saldhana Improve the performance of the LdapExtLoginModule by adding a parseRoleNameFromDN option or check the returned DN to see if it already includes the roleNameAttributeID, and if it does, parse the roleNameAttributeID from the DN rather than querying LDAP for the roleNameAttributeID. -- 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

18 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBWEB-89) Getting exception org.apache.commons.httpclient.HttpRecoverableException

by Masao Kato (JIRA)

Getting exception org.apache.commons.httpclient.HttpRecoverableException ------------------------------------------------------------------------ Key: JBWEB-89 URL: http://jira.jboss.com/jira/browse/JBWEB-89 Project: JBoss Web Issue Type: Bug Security Level: Public (Everyone can see) Environment: Apache 2.0.52-32/mod_jk 1.2.22/JBoss 4.2.0.GA Reporter: Masao Kato Assigned To: Mladen Turk We are getting this exception . ERROR [org.apache.catalina.connector.CoyoteAdapter] java.lang.StringIndexOutOfBoundsException: String index out of range: 32 at java.lang.String.substring(String.java:1765) at org.jboss.web.tomcat.service.session.JvmRouteValve.handleJvmRoute(JvmRouteValve.java:128) at org.jboss.web.tomcat.service.session.JvmRouteValve.checkJvmRoute(JvmRouteValve.java:112) at org.jboss.web.tomcat.service.session.JvmRouteValve.invoke(JvmRouteValve.java:81) 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.valves.AccessLogValve.invoke(AccessLogValve.java:543) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241) at org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:437) at org.apache.coyote.ajp.AjpProtocol$AjpConnectionHandler.process(AjpProtocol.java:381) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:595) I watched a source file(JvmRouteValve.java). I think that substring of the session ID may be wrong. I made a patch. Is this right? --- src/main/org/jboss/web/tomcat/service/session/JvmRouteValve.java.orig 2007-08-10 18:59:45.000000000 +0900 +++ src/main/org/jboss/web/tomcat/service/session/JvmRouteValve.java 2007-08-10 19:01:11.000000000 +0900 @@ -125,7 +125,7 @@ int index = oldsessionId.lastIndexOf("."); if (index > 0) { - receivedJvmRoute = oldsessionId.substring(index + 1, sessionId.length()); + receivedJvmRoute = oldsessionId.substring(index + 1, oldsessionId.length()); } String requestedJvmRoute = null; -- 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

18 years, 11 months

2
4
0 / 0

[JBoss JIRA] Closed: (JBAOP-200) Make sure the batch and sh files work

by Stale Pedersen (JIRA)

[ http://jira.jboss.com/jira/browse/JBAOP-200?page=all ] Stale Pedersen closed JBAOP-200. -------------------------------- > Make sure the batch and sh files work > ------------------------------------- > > Key: JBAOP-200 > URL: http://jira.jboss.com/jira/browse/JBAOP-200 > Project: JBoss AOP > Issue Type: Bug > Reporter: Kabir Khan > Assigned To: Stale Pedersen > Fix For: 2.0.0.GA > > -- 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

18 years, 11 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBAOP-200) Make sure the batch and sh files work

by Stale Pedersen (JIRA)

[ http://jira.jboss.com/jira/browse/JBAOP-200?page=all ] Stale Pedersen resolved JBAOP-200. ---------------------------------- Resolution: Done confirmed that the fixes works on both linux and windows. > Make sure the batch and sh files work > ------------------------------------- > > Key: JBAOP-200 > URL: http://jira.jboss.com/jira/browse/JBAOP-200 > Project: JBoss AOP > Issue Type: Bug > Reporter: Kabir Khan > Assigned To: Stale Pedersen > Fix For: 2.0.0.GA > > -- 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

18 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-1020) BRMS Custom Rule Selector for Creating Deployable Packages

by Barry Knapp (JIRA)

BRMS Custom Rule Selector for Creating Deployable Packages ---------------------------------------------------------- Key: JBRULES-1020 URL: http://jira.jboss.com/jira/browse/JBRULES-1020 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-brms Environment: general Reporter: Barry Knapp Assigned To: Mark Proctor Priority: Optional Use Case : Ability to include or exclude rules in a deployable package based on rule meta data or custom rule attributes. Add an extension point to the BRMS for deciding which rules should be included in a deployable package. A CustomSelector interface with an boolean accepts(Rule) method would allow implementors to create a class and implement the accepts method. The custom method could then analyze the rule to determine if the rule should be included in the package being generated by return true for inclusion. A property file with CustomExtractor=com...implementing class would allow the implementor to inject their CustomSelector 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

18 years, 11 months

3
15
0 / 0

[JBoss JIRA] Created: (JBRULES-1113) renaming a package messes up the assets in it

by Michael Neale (JIRA)

renaming a package messes up the assets in it ---------------------------------------------- Key: JBRULES-1113 URL: http://jira.jboss.com/jira/browse/JBRULES-1113 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-brms Affects Versions: 4.0.0.GA Reporter: Michael Neale Assigned To: Michael Neale Priority: Critical Fix For: 4.0.1 -- 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

18 years, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1037) fix RunAs principal propagation

by William DeCoste (JIRA)

fix RunAs principal propagation ------------------------------- Key: EJBTHREE-1037 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1037 Project: EJB 3.0 Issue Type: Bug Affects Versions: AS 4.2.1.GA Reporter: William DeCoste Assigned To: William DeCoste We decided it would the principal associated with the run-as identity. In this case its anonymous unless overridden in the run-as config. This is what the cts14 tests required. We used to return the original caller principal, but with the need to assign multiple roles to the run-as principal for the cts14 tests, we switched this to a separate run-as principal. The ejb3-spec is a little more clear about there being a run-as principal: 17.1: The security principal under which a method invocation is performed is typically that of the component's caller. By specifying a run-as identity, however, it is possible to specify that a different principal be substituted for the execution of the methods of the bean's business interface, home interface, component interface, and/or web service endpoint and any methods of other enterprise beans that the bean may call. This determines whether the caller principal is propagated from the caller to the callee—that is, whether the called enterprise bean will see the same returned value of the EJBContext.getCallerPrincipal as the calling enterprise bean—or whether a security principal that has been assigned to the specified security role will be used for the execution of the bean's methods and will be visible as the caller principal in the bean's callee. 17.3.4 Specification of Security Identities in the Deployment Descriptor ... Because the Bean Provider and Application Assembler do not, in general, know the security environment of the operational environment, the run-as identity is designated by a logical role-name, which corresponds to one of the security roles defined by the Bean Provider or Application Assembler in the metadata annotations or deployment descriptor. The Deployer then assigns a security principal defined in the operational environment to be used as the principal for the run-as identity. The security principal assigned by the Deployer should be a principal that has been assigned to the security role specified by RunAs annotation or by the role-name element of the run-as deployment descriptor element. The Bean Provider and/or Application Assembler is responsible for the following in the specification of run-as identities: • Use the RunAs metadata annotation or role-name element of the run-as deployment descriptor element to define the name of the security role. • Optionally, use the description element to provide a description of the principal that is expected to be bound to the run-as identity in terms of its security role. 17.4.3 Principal Delegation The Deployer is responsible for configuring the principal delegation for inter-component calls. The Deployer must follow any instructions supplied by the Bean Provider and/or Application Assembler (for example, provided in the RunAs metadata annotations, the run-as elements of the deployment descriptor, in the description elements of the annotations or deployment descriptor, or in a deployment manual). If the security identity is defaulted, or it is explicitly specified that the caller identity be used (e.g., use-caller-identity deployment descriptor element is specified), the caller principal is propagated from one component to another (i.e., the caller principal of the first enterprise bean in a call-chain is passed to the enterprise beans down the chain). If the Bean Provider or Application Assembler specifies that a run-as identity be used on behalf of a particular enterprise bean, the Deployer must configure the enterprise beans such that the run-as principal is used as the caller principal on any calls that the enterprise bean makes to other beans, and that the run-as principal is propagated along the call-chain of those other beans (in the absence of the specification of any further run-as elements). Anil Saldhana wrote: > > Scott, > > Bill Decoste and I have a simple difference in understanding of > > RunAsIdentity in relation to getCallerPrincipal > > > > BeanA -> BeanB > > > > BeanA defines a RunAs annotation with a role. No principal is attached > > to this annotation (so we will take anonymous as the principal). > > > > If a Principal "anil" invoked BeanA. Then a method in BeanA called a > > method in BeanB. > > > > If BeanB does a getCallerPrincipal, does it return "anonymous" that is > > attached to run-as or it will return "Somebody"? I am saying > > "anonymous" and BillD says it is "anil". > > > > My understanding is that RunAs does a security context switch and a > > security-identity in ejb-jar.xml with <use-caller-identity> would > > propogate. > > > > Can you clarify, please? > > > > Regards, > > Anil > > -- 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

18 years, 11 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 August 2007