[JBoss JIRA] Created: (JBRULES-373) Rules compiler fails on packages containing uppercase chars
by Karim Ratib (JIRA)
Rules compiler fails on packages containing uppercase chars
-----------------------------------------------------------
Key: JBRULES-373
URL: http://jira.jboss.com/jira/browse/JBRULES-373
Project: JBoss Rules
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Drl Parser/Builder
Affects Versions: 3.0.2
Environment: Ubuntu 6.06
NetBeans 5.0
Eclipse 3.2 JDT compiler
Reporter: Karim Ratib
Assigned To: Mark Proctor
Attachments: DroolsTest.zip
The following error is obtained:
Rule Compilation error The import drools.Test cannot be resolved drools.Test cannot be resolved to a type StockOffer cannot be resolved
when an imported package name contains uppercase chars (in this case "drools.Test"). The attached NetBeans project illustrates this behaviour. Renaming the package to all lowercase removes the error.
--
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
20 years
[JBoss JIRA] Commented: (JBAS-2695) LRUStatefulContextCachePolicy implementation of maxBeanLife removal is flawed
by Ben Wang (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-2695?page=comments#action_12339639 ]
Ben Wang commented on JBAS-2695:
--------------------------------
Scott, what do you think? Is it relevant anymore? I'd prefer not to spend time on this since I don't this is a big deal, per se. :-) But if it is, I can do it.
> LRUStatefulContextCachePolicy implementation of maxBeanLife removal is flawed
> -----------------------------------------------------------------------------
>
> Key: JBAS-2695
> URL: http://jira.jboss.com/jira/browse/JBAS-2695
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: EJB2
> Affects Versions: JBossAS-3.2.8RC1, JBossAS-4.0.3 SP1
> Reporter: Scott M Stark
> Assigned To: Ben Wang
> Priority: Critical
> Fix For: JBossAS-4.0.5.CR1
>
>
> The RemoverTask of the org.jboss.ejb.plugins.LRUStatefulContextCachePolicy performs removal of passivated beans based on a maxBeanLife - maxBeanAge diff. This is invalid for beans passivated due to size. The calculation should be maxBeanLife - (the per bean instance time of inactivity). The reason is a bean may be passivated very quickly due to cache size constraints and if the maxBeanLife - maxBeanAge == 0, just a quickly thrown away.
--
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
20 years
[JBoss JIRA] Created: (JBESB-76) Small refactoring issues break the current build
by Kurt Stam (JIRA)
Small refactoring issues break the current build
------------------------------------------------
Key: JBESB-76
URL: http://jira.jboss.com/jira/browse/JBESB-76
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: ESB Core
Environment: linux (FC4), java5
Reporter: Kurt Stam
Assigned To: Mark Little
1. There are 2 identical classes called BobjStore,
one in org.jboss.soa.esb.internal.core.objectstore and
one in org.jboss.soa.esb.services.dbtables.
2. The org.jboss.soa.esb.services.crypto package is now gone, but the is still a reference to it in org.jboss.soa.esb.services.dbtables.DaoSnapTable
3. The build process references the ESBCore/tests directory, while the directory is called Tests, with a capital T, which is a problem in *nix systems.
--
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
20 years
[JBoss JIRA] Updated: (JBREM-139) need automated test for servlet server invoker
by Tom Elrod (JIRA)
[ http://jira.jboss.com/jira/browse/JBREM-139?page=all ]
Tom Elrod updated JBREM-139:
-----------------------------
Fix Version/s: 2.2.0.Beta1 (Bluto)
(was: 2.0.0.CR1 (Boon))
Assigning to 2.2.0 release as won't have time to automate tests for 2.0.0 release (which have tested manually).
Only way I can see this can be done is to somehow bring down jbossas binary to copy servlet invoker war and servlet server invoker deployments to, then start it, run client test, then shut it down. Not going to be pretty. Really don't like the idea of having to now bundle jbossas in the remoting project for testing, but may be no other way.
> need automated test for servlet server invoker
> ----------------------------------------------
>
> Key: JBREM-139
> URL: http://jira.jboss.com/jira/browse/JBREM-139
> Project: JBoss Remoting
> Issue Type: Task
> Components: general
> Affects Versions: 1.2.0 final
> Reporter: Tom Elrod
> Assigned To: Tom Elrod
> Priority: Minor
> Fix For: 2.2.0.Beta1 (Bluto)
>
>
> Tests for servlet invoker is manual since have to deploy servlet-invoker.war to jboss in order for it to work. Need to figure out if there
> is an easy automated way to do this (since would currently require JBossAS, don't think realistic to run as unit test for JBossRemoting
> test run).
--
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
20 years