July 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-2160) CLONE -Use of reserved word as bound variable in a pattern results as NPE

by Neil Wallace (JIRA)

CLONE -Use of reserved word as bound variable in a pattern results as NPE ------------------------------------------------------------------------- Key: JBRULES-2160 URL: https://jira.jboss.org/jira/browse/JBRULES-2160 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-compiler Affects Versions: 4.0.2 Environment: Eclipse 3.2, Windows XP Reporter: Neil Wallace Assignee: Edson Tirelli Fix For: 5.0.1.FINAL example: rule "This generates an NPE" when result : ReservedWordNPEFact(data < 15) then result.setData(new Integer(1)); end At least in the eclipse IDE, this generates an NPE. Change result to something like: rule "This generates an NPE" when f: ReservedWordNPEFact(data < 15) then f.setData(new Integer(1)); end and it goes away. -- 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

16 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-2159) CLONE -DSL Parser "eval"

by Neil Wallace (JIRA)

CLONE -DSL Parser "eval" ------------------------ Key: JBRULES-2159 URL: https://jira.jboss.org/jira/browse/JBRULES-2159 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-compiler-DSL Affects Versions: 4.0.1 Reporter: Neil Wallace Assignee: Edson Tirelli Priority: Minor Fix For: 5.0.1.FINAL rule "PatternTest" when $pli:Item( title matches "^Test\s*") then # end this one compiles but on Runtime it ends in an Exception when title looks for example like this "BlaBla (Test)". as workaround i thought about using the next part, but rule "PatternTest" when $pli:Item( eval(title.matches("^Test\s*")) ) then # end it resolves into, also it shouldn't (because title.matches() is Java Code a shouldn't be parsed by the DSL Parser itself): SyntaxfehlerRule Compilation error : [Rule name=OnlineStreaming Start, agendaGroup=MAIN, salience=100, no-loop=true] com/p7s1/swi/phoenix/n24/Rule_OnlineStreaming_Start_0.java (19:923) : Invalid escape sequence (valid ones are \b \t \n \f \r \" \' \\ ) -- 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

16 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-2158) CLONE -Outline problems in DRL editor

by Neil Wallace (JIRA)

CLONE -Outline problems in DRL editor ------------------------------------- Key: JBRULES-2158 URL: https://jira.jboss.org/jira/browse/JBRULES-2158 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-eclipse Affects Versions: 3.0.4 Reporter: Neil Wallace Assignee: Kris Verlaenen Priority: Minor Fix For: 5.0.1.FINAL Two (possibly related) problems with the outline view in the DRL editor: *) Rules that are commented out via a multi-line comment (/* ... */) still appear in the outline. *) Clicking on the name of a rule highlights some text near that rule. I assume it's supposed to highight the title of the rule, but it misses. Same thing affects the imports. -- 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

16 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-2157) Outline problems in DRL editor

by Neil Wallace (JIRA)

Outline problems in DRL editor ------------------------------ Key: JBRULES-2157 URL: https://jira.jboss.org/jira/browse/JBRULES-2157 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-eclipse Affects Versions: 3.0.4 Reporter: Neil Wallace Assignee: Kris Verlaenen Priority: Minor Fix For: 5.0.1.FINAL Two (possibly related) problems with the outline view in the DRL editor: *) Rules that are commented out via a multi-line comment (/* ... */) still appear in the outline. *) Clicking on the name of a rule highlights some text near that rule. I assume it's supposed to highight the title of the rule, but it misses. Same thing affects the imports. -- 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

16 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBJCA-105) SJC/RAdeployer: Add support for DTDs

by Jeff Zhang (JIRA)

SJC/RAdeployer: Add support for DTDs ------------------------------------ Key: JBJCA-105 URL: https://jira.jboss.org/jira/browse/JBJCA-105 Project: JBoss JCA Issue Type: Task Components: Deployer Affects Versions: 1.0.0.Alpha1 Reporter: Jeff Zhang Assignee: Jeff Zhang Fix For: 1.0.0.Alpha2 Add dtd deployment into sjc deployer create this task for tacking this function. code commit r90827 should belong this task -- 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

16 years, 10 months

1
3
0 / 0

[JBoss JIRA] Commented: (JBAS-7032) Getting invalid deployment on what appears to be valid, a webbeans ear file.

by John Ament (JIRA)

[ https://jira.jboss.org/jira/browse/JBAS-7032?page=com.atlassian.jira.plug... ] John Ament commented on JBAS-7032: ---------------------------------- It's funny that this got brought back up, I was about to update this as well. After some playing with it, if I configure the server to enter a clustered environment, I can get it (admin-console.war) to deploy correctly but attempting to access it results in a no active conversation exception. I've only been able to reproduce this with a webbeans deployment, I'm not sure about you. From what I can tell, the fact that it's deploying is apparently a bug w/ the current webbeans ri which doesn't seem to work correctly in a clustered environment. The no active conversation is a result of the webbeans deployer and filter taking higher precedence over the seam deployment (I verified by looking at the stack trace and seeing that the seam request was running through the webbeans filter, rather than the seam filter). If you believe it's relevant, I'll post that stacktrace tomorrow. > Getting invalid deployment on what appears to be valid, a webbeans ear file. > ---------------------------------------------------------------------------- > > Key: JBAS-7032 > URL: https://jira.jboss.org/jira/browse/JBAS-7032 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Deployers > Environment: JBoss AS 5.1 > JDK 1.6 u 13 > OpenSuSe 11.1 / SLES 10.2 > Reporter: John Ament > Assignee: Shelly McGowan > Priority: Blocker > Fix For: JBossAS-5.2.0.Beta1 > > Attachments: WhatUpDawg.ear > > > The best description I can give is from the forum. > Basically, I have an EAR that appears to be completely valid, it's 2 war's and 1 ejb module. It's built using web beans. I get the described stack trace when either deploying via the UI or just dropping the EAR file in deploy. However, I get different results. When I drop the ear in and restart, it loads perfectly (my app) but embedded jopr 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

16 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-7032) Getting invalid deployment on what appears to be valid, a webbeans ear file.

by Shelly McGowan (JIRA)

[ https://jira.jboss.org/jira/browse/JBAS-7032?page=com.atlassian.jira.plug... ] Shelly McGowan updated JBAS-7032: --------------------------------- John, I am able to reproduce the issue. Let me continue to investigate the root cause. > Getting invalid deployment on what appears to be valid, a webbeans ear file. > ---------------------------------------------------------------------------- > > Key: JBAS-7032 > URL: https://jira.jboss.org/jira/browse/JBAS-7032 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Deployers > Environment: JBoss AS 5.1 > JDK 1.6 u 13 > OpenSuSe 11.1 / SLES 10.2 > Reporter: John Ament > Assignee: Shelly McGowan > Priority: Blocker > Fix For: JBossAS-5.2.0.Beta1 > > Attachments: WhatUpDawg.ear > > > The best description I can give is from the forum. > Basically, I have an EAR that appears to be completely valid, it's 2 war's and 1 ejb module. It's built using web beans. I get the described stack trace when either deploying via the UI or just dropping the EAR file in deploy. However, I get different results. When I drop the ear in and restart, it loads perfectly (my app) but embedded jopr 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

16 years, 10 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBAS-3248) JBoss xercesImpl.jar conflicts with xerces.jar within Ears/wars

by denny Valliant (JIRA)

[ https://jira.jboss.org/jira/browse/JBAS-3248?page=com.atlassian.jira.plug... ] denny Valliant commented on JBAS-3248: -------------------------------------- You can just delete the xercesImpl jar in the jasperserver/WEB-INF/lib folder and it will start fine. Haven't done extensive testing with XML stuff to make sure there isn't something broken deep inside, but everything seems to work just dandy. > JBoss xercesImpl.jar conflicts with xerces.jar within Ears/wars > --------------------------------------------------------------- > > Key: JBAS-3248 > URL: https://jira.jboss.org/jira/browse/JBAS-3248 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: ClassLoading, Clustering > Affects Versions: JBossAS-4.0.3 SP1 > Environment: Red Hat Enterprise Linux ES release 4; > java version 1.5.0_06; > JBoss in cluster mode > Reporter: Alan > Assignee: Scott M Stark > > I have an application (.war file) that uses a lib called xerces.jar located at .war /WEB-INF/lib directory. I run JBoss in cluster mode. So, after deploy, when I run my application, I got an exception with the xml libs. I guess it's a classloader problem. MY application tries to use the JBoss xml classes intead of it's own. I discovered the problem was with the xerces.jar and xercesImpl.jar because I deleted the line below from the <JBOSS_HOME>/bin/run.sh: > -Djava.endorsed.dirs=... > I searched for a solution and discovered jdk versions before 1.5 have a bug with xml, so I tried the solution above and all worked fine. Now my application use it's own xerces instead of JBoss xerces. > I think my solution is a workaround. I would like to know if there is a better way to solve this problem. Is there ? > The exception is below. > Than you. > Alan > The exception: > java.lang.reflect.InvocationTargetException > 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.apache.struts.actions.DispatchAction.perform(DispatchAction.java :236) > at org.apache.struts.action.ActionServlet.processActionPerform(ActionServlet.java:1787) > at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1586) > at org.apache.struts.action.ActionServlet.doPost (ActionServlet.java:510) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter (ApplicationFilterChain.java:252) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) > at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java :81) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) > at org.jboss.web.tomcat.security.CustomPrincipalValve.invoke (CustomPrincipalValve.java:39) > at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:159) > at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java :407) > at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:59) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) > at org.apache.catalina.valves.ErrorReportValve.invoke (ErrorReportValve.java:105) > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:744) > at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket (PoolTcpEndpoint.java:527) > at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112) > at java.lang.Thread.run(Thread.java:595) > Caused by: java.lang.VerifyError: (class: org/apache/soap/util/xml/XercesParserLiaison, method: read signature: (Ljava/lang/String;Ljava/io/Reader;)Lorg/w3c/dom/Document;) Incompatible object argument > for function call > at org.apache.soap.rpc.Call.<init>(Call.java) > at org.apache.soap.rpc.Call.<init>(Call.java) > at com.attachmate.mcs.agent.impl.SOAPPackager.a(SOAPPackager.java ) > ... -- 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

16 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-7080) Add options to set providers and algorithms in the JaasSecurityDomain

by Marcus Moyses (JIRA)

Add options to set providers and algorithms in the JaasSecurityDomain --------------------------------------------------------------------- Key: JBAS-7080 URL: https://jira.jboss.org/jira/browse/JBAS-7080 Project: JBoss Application Server Issue Type: Feature Request 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 Need to add options to set the provider for the KeyStore, TrustStore, KeyManagerFactory and TrustManagerFactory. Need to add options to set the algorithm for the KeyManagerFactory and TrustManagerFactory. -- 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

16 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (SECURITY-422) Allow LdapExtLoginModule to read the bind credential with an external command

by Marcus Moyses (JIRA)

Allow LdapExtLoginModule to read the bind credential with an external command ----------------------------------------------------------------------------- Key: SECURITY-422 URL: https://jira.jboss.org/jira/browse/SECURITY-422 Project: JBoss Security and Identity Management Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JBossSX Affects Versions: JBossSecurity_2.0.3.SP2 Reporter: Marcus Moyses Assignee: Marcus Moyses Fix For: JBossSecurity_2.0.3.SP2 The LdapExtLoginModule bust be able to read the bind credential password with an external command. -- 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

16 years, 10 months

1
1
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