But, which fields didn't appear in guvnor?
2010/3/16 Amit Kumar <amitkumar(a)gmail.com>
Probably because of OStype and OSversion. Let me fix that and convert
to
lower case and try. I remember facing this issue sometime back with 5.0
Thanks
Amit
On Tue, Mar 16, 2010 at 9:17 AM, Amit Kumar <amitkumar(a)gmail.com> wrote:
> Its coming from a JAR
> Thanks
> Amit
>
> Equipment entityId int partNumber String manufacturer
> String owningEntityId int Software entityId int OSType String
> OSVersion String imageName String EquipmentCA extends Equipment
> hostname String productName String productFamily String
> productId String
> 2010/3/16 Esteban Aliverti <esteban.aliverti(a)gmail.com>
>
> Are you importing your model from a .jar or using a Declarative Model?
>>
>>
>> On Tue, Mar 16, 2010 at 6:28 AM, Toni Rikkola <trikkola(a)redhat.com>wrote:
>>
>>> Hi,
>>>
>>> Its possible that there are some bugs in the snapshots. Can you tell me
>>> what your model looks like?
>>>
>>> Toni
>>>
>>> Amit Kumar wrote:
>>> > The latest builds seem to be no good for guvnor
>>> > They do seem rich in features .. especially support for
>>> > collect/accumulate in guvnor along with inbox and global packages.
>>> >
>>> > But But But.. on adding a fact in the when/then clause then all the
>>> > attributes of the facts are not coming .. some attributes come.. not
>>> > all of them.
>>> > I am picking it from here
>>> >
>>>
https://hudson.jboss.org/hudson/job/drools/lastSuccessfulBuild/artifact/t...
>>> > Any other place I can look :)
>>> >
>>> > Thanks
>>> > Amit
>>> >
>>> > On Mon, Feb 22, 2010 at 8:54 AM, Amit Kumar <amitkumar(a)gmail.com
>>> > <mailto:amitkumar@gmail.com>> wrote:
>>> >
>>> > Thanks Jervis!!
>>> >
>>> > On Sun, Feb 21, 2010 at 7:05 PM, Jervisliu <jliu(a)redhat.com
>>> > <mailto:jliu@redhat.com>> wrote:
>>> >
>>> > A new feature called "Sharable artifacts/Global
artifacts"
>>> will be
>>> > available in Drools 5.1. This feature allows you share an
>>> > asset among
>>> > different packages. It also creates a global area (you can
>>> > consider it
>>> > as a global package). Potentially you can promote an asset
>>> > that you
>>> > think is more appropriate to be defined in a global scope from
>>> > your
>>> > current package to the global area, so that this global asset
>>> > can be
>>> > reused by every package. This feature is already on trunk,
>>> > maybe you
>>> > want to give it a try. Any comments or feedbacks will be
>>> highly
>>> > appreciated.
>>> >
>>> > Cheers,
>>> > Jervis
>>> >
>>> >
>>> > Amit Kumar wrote:
>>> > > Hello All,
>>> > >
>>> > > I am looking to organize the rules in different
categories.
>>> > But for
>>> > > distribution purposes We are creating packages for
different
>>> > > roles/processing phases
>>> > >
>>> > > So a rule will reside in one pckage but for navigation it
>>> > can belong
>>> > > to multiple categories
>>> > >
>>> > > So packages are like Shirts, Pants, Shoes, Sweaters
>>> > > Categories are Color, Material, Size, Gender and those
have
>>> sub
>>> > > categories witin them
>>> > >
>>> > > We have rules which will device the category of the item
>>> > > Like "red rule", "blue rule",
"cloth rule", leather rule"
>>> > >
>>> > > Now the problem we are facing is for category rules is if
I
>>> > define the
>>> > > rule in Shirt package .. then I will not be able ot use it
>>> > in Pant
>>> > > package.. Will have to redefine it.
>>> > >
>>> > > The other problem in this scenario is If I have a price
rule
>>> > in Shirt
>>> > > package and the category is "Blue Color" and
"XL Size" then
>>> > I will
>>> > > have to put it in both categories
>>> > > When I put the "Blue Rule" on "Blue
Category" and "XL Rule"
>>> > on "XL
>>> > > Category" and I put the rule in both categories..
will it
>>> > be an "and"
>>> > > relationship or will be an "OR"
>>> > >
>>> > > Regards,
>>> > > Amit
>>> > >
>>> >
>>> ------------------------------------------------------------------------
>>> > >
>>> > > _______________________________________________
>>> > > rules-users mailing list
>>> > > rules-users(a)lists.jboss.org <mailto:
>>> rules-users(a)lists.jboss.org>
>>> > >
https://lists.jboss.org/mailman/listinfo/rules-users
>>> > >
>>> >
>>> > _______________________________________________
>>> > rules-users mailing list
>>> > rules-users(a)lists.jboss.org <mailto:
>>> rules-users(a)lists.jboss.org>
>>> >
https://lists.jboss.org/mailman/listinfo/rules-users
>>> >
>>> >
>>> >
>>> >
>>> ------------------------------------------------------------------------
>>> >
>>> > _______________________________________________
>>> > rules-users mailing list
>>> > rules-users(a)lists.jboss.org
>>> >
https://lists.jboss.org/mailman/listinfo/rules-users
>>> >
>>>
>>> _______________________________________________
>>> rules-users mailing list
>>> rules-users(a)lists.jboss.org
>>>
https://lists.jboss.org/mailman/listinfo/rules-users
>>>
>>
>>
>>
>> --
>> XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
>>
>> Esteban Aliverti
>>
>> _______________________________________________
>> rules-users mailing list
>> rules-users(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/rules-users
>>
>>
>
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users