[rules-users] Some doubts on Guvnor

[Tihomir Surdilovic]

On 1/20/11 9:44 PM, Diego Martins wrote:
> Hello!
>
> So, let'me explain what is happening first...
>
> I'm developing a project based on seam 2.2.0, and we used to have guvnor
> (5.0.1) working perfectly. So, suddenly I decided it was time to move on and
> start using the newest version (5.1.1, i guess). Made a backup of the older
> version, configured the newer guvnor and deployed it. But I didn't know
> Guvnor 5.1.1 had this need to authenticate in order to retrieve the binary
> packages, which causes some trouble with seam 2.2.0, since I can't configure
> username and password on my rules.properties, making it impossible to
> integrate them.
>
Seam 2.2.x includes the Drools 5.0.1 libs so using it with Guvnor 5.1.1  
is currently not possible. AFAIK there was a recent Jira to upgrade the 
libs to 5.1.1. Once this is done, the integration should be possible. 
Still the Seam2 integration code uses the Drools 4 API (RuleAgent) and 
not the Drools5 API (KnowledgeAgent/ChangeSet), changing this is 
something I am working on to get fixed for users that don't want or 
cannot upgrade to Seam3 when it becomes available.

If you must upgrade to Guvnor 5.1.1 now, one option is to switch out the 
Drools libs in your Seam project to 5.1.1 and use the Drools5 API 
directly in your Seam components (bypass the integration in components.xml).

> Then I decided to move back to my good old guvnor 5.0.1, but as I tried to
> deploy, malign forces started acting and, what worked perfectly before, no
> longer works. This is the exception: http://pastebin.com/VUWxJyLD
>
> (BTW, I'm using tomcat 6)
>
> So, nothing changed, but suddenly Guvnor 5.0.1 no longer deploys.
>
> I tried to find this version on Jboss Drools website, without success. Looks
> like the only version available is the newest.
>
> So, I came to you kindly asking for urgent help... It could be on how to fix
> this exception and make my backup deployable again, or on how to get older
> versions of Guvnor (preferably 5.0.1).
As Esteban already mentioned, when you upgraded to Guvnor 5.1.1 you also 
upgraded your Jackrabbit jars, which are not backwards compatible to the 
older version used in 5.0.1. Hope you have a backup of your repo 
(export), then you can delete the repository.xml and the repository/ 
directory that Jackrabbit created (if you are using the default setup, 
or if you are connecting to a DB, blow up the entire schema, not just 
tables as afaik Jackrabbit also creates some triggers etc) before 
starting 5.0.1 again, then re-import your repo export xml.

Hope this helps.

Tihomir
> Thanks already!
>
> Diego Martins