[rules-dev] Guided Editor in BRMS / Guvnor Version 5 (Snapshot of 26 June)
Paul Browne
paulb at firstpartners.net
Thu Jun 26 16:45:27 EDT 2008
Ravi,
Thanks for your quick response and good suggestions
1) I tried the xml you suggested, but on my JBoss this causes a chain of
errors.
2) Removing the edit from 1, I searched around the issue and tried the
fix on this webpage
http://www.nabble.com/Drools-4.0.4-and-Jboss-4.2.2-GA-td16113554.html#a16113554
Paul
Thalupula Ravi wrote:
> Hi,
>
> I fixed same kind of bug using below solution.
>
> add <transaction:no-transaction/> tag, components.xml file, you can find
> this file in war/ web-inf folder.
>
> complete xml file should be like below
>
> <?xml version="1.0" encoding="UTF-8"?>
> <components xmlns="http://jboss.com/products/seam/components"
> xmlns:core="http://jboss.com/products/seam/core"
> xmlns:transaction="http://jboss.com/products/seam/transaction"
> xmlns:security="http://jboss.com/products/seam/security"
> xmlns:web="http://jboss.com/products/seam/web"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation=
> "http://jboss.com/products/seam/core
> http://jboss.com/products/seam/core-2.0.xsd
> http://jboss.com/products/seam/security
> http://jboss.com/products/seam/security-2.0.xsd
> http://jboss.com/products/seam/components
> http://jboss.com/products/seam/components-2.0.xsd
> http://jboss.com/products/seam/web
> http://jboss.com/products/seam/web-2.0.xsd">
>
>
> <core:init transaction-management-enabled="false"/>
> <transaction:no-transaction/> <!-- to fix transaction context flush bug
> -->
>
> <component name="repositoryConfiguration">
> <!--
> *** This is for configuring the "home" directory for the repo
> storage. the directory must exist. ***
> <property
> name="homeDirectory">/home/michael/RulesRepository_001</property>
> -->
>
> <!--
> Optional: this is for creating a configurator for a seperate
> repository type.
> <property
> name="configurator">org.drools.repository.JackrabbitRepositoryConfigurator</property>
> -->
> </component>
>
> <!-- SECURITY CONFIGURATION -->
>
> <!-- default (will take any username, useful if you want to keep track
> of users but not authenticate -->
> <security:identity
> authenticate-method="#{defaultAuthenticator.authenticate}"/>
>
> <!-- NO authentication. This will bypass the login screen when you hit
> the app. Everyone is "guest" -->
> <!-- <security:identity
> authenticate-method="#{nilAuthenticator.authenticate}"/> -->
>
> <!-- as JAAS is used you can use container specific ones to link up to
> your login services, eg LDAP -->
>
>
>
> </components>
>
> Regards,
> Ravi Thalupula
>
More information about the rules-dev
mailing list