[rules-users] POJO.jar Format for upload a fact model (basic question)

[Stephen Masters]

You need to be careful that none of the classes in your jar have dependencies that are not also in the jar or on the server classpath. They can be messed up through the use of a JPA or Spring annotation for instance.

I tend to create a separate Maven project for my fact model, purely to ensure that there are no such dependencies, since it won't compile if there are any.


On 18 Feb 2013, at 13:05, Michael Anstis <michael.anstis at gmail.com> wrote:

> The JAR must be a regular Java JAR file.
> 
> There were issues on older versions of Guvnor that meant that once a JAR had been uploaded you needed to restart the web-server, but I believe this has been resolved.
> 
> Building the package should give you all validation errors. The warning icon, I assume being that to which you refer, indicates there is a validation error.
> 
> On 18 February 2013 12:07, oresch <olaf.resch at t-online.de> wrote:
> Sorry to ask this basic question. What does the pojo.jar contain? Is there a
> required format for the class.  Is there an example? I tried  to pack the
> .java and the .class in various formats, but even though the upload is
> working there is a warning sign next to the asset and I can not use the
> content. By the way, how can I see what the warning sign acctually means?
> Best wishes
> Olaf
> 
> 
> 
> --
> View this message in context: http://drools.46999.n3.nabble.com/POJO-jar-Format-for-upload-a-fact-model-basic-question-tp4022393.html
> Sent from the Drools: User forum mailing list archive at Nabble.com.
> _______________________________________________
> rules-users mailing list
> rules-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/rules-users
> 
> _______________________________________________
> rules-users mailing list
> rules-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/rules-users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/rules-users/attachments/20130218/0ed64c90/attachment.html