[JBoss JIRA] Created: (JBRULES-1270) Tool friendly MVEL features for MVEl 2.0
by Philippe Ombredanne (JIRA)
Tool friendly MVEL features for MVEl 2.0
----------------------------------------
Key: JBRULES-1270
URL: http://jira.jboss.com/jira/browse/JBRULES-1270
Project: JBoss Drools
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Eclipse IDE
Reporter: Philippe Ombredanne
Assigned To: Mark Proctor
Fix For: FUTURE
Here are a couple request for MVEl 2.0:
- keeping something like an ast (may be with a compile flag) that is close to the actual expression text
- producing compiled expression even of there were some errors (ie keep on trucking) (optional flag for that too)
- being able to extend the ast with completion information (ie attach completion stuffs directly as a decoration of node in the parse tree
--
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, 7 months
[JBoss JIRA] Created: (JBAOP-478) ClassCastException on AnnotatedParameterAdviceInfo
by Flavia Rainone (JIRA)
ClassCastException on AnnotatedParameterAdviceInfo
--------------------------------------------------
Key: JBAOP-478
URL: http://jira.jboss.com/jira/browse/JBAOP-478
Project: JBoss AOP
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Flavia Rainone
Assigned To: Flavia Rainone
This is what happens when line 464 of AnnotatedAdviceInfo is executed with a method that returns a parameterized type:
java.lang.ClassCastException: sun.reflect.generics.reflectiveObjects.ParameterizedTypeImpl
at org.jboss.aop.advice.annotation.AnnotatedParameterAdviceInfo$SingleParameterType.internalValidate(AnnotatedParameterAdviceInfo.java:464)
at org.jboss.aop.advice.annotation.AnnotatedParameterAdviceInfo$ParameterAnnotationType.validate(AnnotatedParameterAdviceInfo.java:374)
at org.jboss.aop.advice.annotation.AnnotatedParameterAdviceInfo.matches(AnnotatedParameterAdviceInfo.java:124)
at org.jboss.aop.advice.annotation.AdviceMethodFactory.bestValidAdvice(AdviceMethodFactory.java:412)
at org.jboss.aop.advice.annotation.AdviceMethodFactory.findAdviceMethod(AdviceMethodFactory.java:291)
at org.jboss.aop.instrument.JoinPointGenerator$AdviceSetups.<init>(JoinPointGenerator.java:1532)
at org.jboss.aop.instrument.JoinPointGenerator.initialiseAdviceInfosAndAddFields(JoinPointGenerator.java:550)
at org.jboss.aop.instrument.JoinPointGenerator.generateJoinpointClass(JoinPointGenerator.java:399)
at org.jboss.aop.instrument.JoinPointGenerator.doGenerateJoinPointClass(JoinPointGenerator.java:276)
at org.jboss.aop.instrument.JoinPointGenerator.access$100(JoinPointGenerator.java:75)
at org.jboss.aop.instrument.JoinPointGenerator$GenerateJoinPointClassAction$1$1.run(JoinPointGenerator.java:1630)
at java.security.AccessController.doPrivileged(Native Method)
at org.jboss.aop.instrument.JoinPointGenerator$GenerateJoinPointClassAction$1.generateJoinPointClass(JoinPointGenerator.java:1626)
at org.jboss.aop.instrument.JoinPointGenerator.generateJoinPointClass(JoinPointGenerator.java:244)
at org.jboss.aop.GeneratedClassAdvisor.generateJoinPointClass(GeneratedClassAdvisor.java:1017)
at org.jboss.test.aop.annotatedAdviceParams.ReturnInvalidPOJO$ReturnInvalidPOJOAdvisor.methodGenericsAfter54841465230530634828(ReturnInvalidPOJO$Retu
rnInvalidPOJOAdvisor.java)
This task includes a check on the code to see if the error is repeated in other code lines.
--
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, 7 months
[JBoss JIRA] Updated: (JBMESSAGING-381) Add param on destination to disable persistence
by Jeff Mesnil (JIRA)
[ http://jira.jboss.com/jira/browse/JBMESSAGING-381?page=all ]
Jeff Mesnil updated JBMESSAGING-381:
------------------------------------
Attachment: patch-JBMESSAGING-381.txt
tentative patch.
corresponding test case is:
export TARGET_CLASS=org.jboss.test.messaging.jms.PersistenceTest
export TARGET_TEST=testQueueWithDisabledPersistence
test case is:
* deploy a queue with disabled persistence
* send a few messages with DeliveryMode.PERSISTENT
* restart the server
* redeploy the same queue
* check that the queue is empty
(the opposing test is PersistenceTest.testQueuePersistence() which checks
that the messages are still in the queue after restart)
- Persistent is true by default for destinations.
- It can be set only before the destination is started (at deployment time)
- a "not persistent" destination corresponds to a MessagingQueue w/o a
PersistenceManager and flagged as non recoverable
I did not check passing null as a PersistenceManager in ChannelSupport is acceptable... it may generate unexpected NPE...
> Add param on destination to disable persistence
> -----------------------------------------------
>
> Key: JBMESSAGING-381
> URL: http://jira.jboss.com/jira/browse/JBMESSAGING-381
> Project: JBoss Messaging
> Issue Type: Feature Request
> Reporter: Tim Fox
> Assigned To: Tim Fox
> Fix For: 2.0.0 Beta 1
>
> Attachments: patch-JBMESSAGING-381.txt
>
> Original Estimate: 1 day
> Remaining Estimate: 1 day
>
> We should add a configuration param on destinations which id true prevents messages being persisted even if they are persistent.
> This should give equivalent functionality to the JBossMQ NullPersistenceManager.
> in some circumstances uses want to override persistence for messages but have no access to change the delivery mode at the sender.
--
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, 7 months
[JBoss JIRA] Created: (JBAS-4609) Original SevletResponse or wrapped original ServletResponse not passed to RequestDispatcher in violation of SRV.8.2 and SRV.14.2.5.1
by stefan lotties (JIRA)
Original SevletResponse or wrapped original ServletResponse not passed to RequestDispatcher in violation of SRV.8.2 and SRV.14.2.5.1
------------------------------------------------------------------------------------------------------------------------------------
Key: JBAS-4609
URL: http://jira.jboss.com/jira/browse/JBAS-4609
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: JBossAS-4.2.0.GA
Environment: RHeL
Reporter: stefan lotties
Sometimes in the log the following stacktrace appears while someone is surfing in an application:
2007-08-09 12:10:01,834 [http-0.0.0.0-8080-1] ERROR org.apache.catalina.core.ContainerBase.[jboss.we
b].[localhost].[/webadmin].[action] - Servlet.service() for servlet action threw exception
javax.servlet.ServletException: Original SevletResponse or wrapped original ServletResponse not pass
ed to RequestDispatcher in violation of SRV.8.2 and SRV.14.2.5.1
at org.apache.catalina.core.ApplicationDispatcher.checkSameObjects(ApplicationDispatcher.jav
a:1018)
at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:329)
at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:301)
at org.apache.struts.action.RequestProcessor.doForward(RequestProcessor.java:1056)
at org.apache.struts.tiles.TilesRequestProcessor.doForward(TilesRequestProcessor.java:261)
at org.apache.struts.tiles.TilesRequestProcessor.processTilesDefinition(TilesRequestProcesso
r.java:237)
at org.apache.struts.tiles.TilesRequestProcessor.processForwardConfig(TilesRequestProcessor.
java:300)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:231)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1164)
at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:397)
at javax.servlet.http.HttpServlet.doHead(HttpServlet.java:271)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.j
ava:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:687)
at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:
469)
at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:403)
at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:301)
at org.apache.catalina.authenticator.FormAuthenticator.forwardToLoginPage(FormAuthenticator.
java:316)
at org.apache.catalina.authenticator.FormAuthenticator.authenticate(FormAuthenticator.java:2
44)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:491)
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:
156)
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.ja
va:580)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:595)
I debugged as far as I could and noticed that the http-request returns the host the jboss runs on when calling HttpServletRequest.getRemoteHost() and has "HEAD" as method. It can't be reproduced since it seems to be kinda random (doing the same action twice or more often does not end in this exception). Also the requested-URIs are different.
--
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, 7 months