what do u mean by "invalid column". need to see the decision table. attach a snapshot of it. On Wed, Nov 7, 2012 at 5:17 PM, Mahadevappa, Shobha < Shobha.Mahadevappa(a)nttdata.com&gt; wrote: -- Thanks & Regards Himansu Nayak 9886006105 "Your Attempt May Fail, But Never Fail To Make An Attempt"

Thanks. I am aware of the error. But I am not aware of the significance of the line and column number in the error message. They are for sure not the row number in the excel. Regards, Shobha M From: rules-users-bounces(a)lists.jboss.org [mailto:rules-users-bounces@lists.jboss.org] On Behalf Of Welsh, Armand Sent: 07 November 2012 PM 10:27 To: rules-users(a)lists.jboss.org Subject: Re: [rules-users] Decision table errors It looks like you SHOLOG class does not have an import in your Drools Package, or you have an import, but the drools compiler cannot find the class specified with a type that is compatible with the "2101" string argument. As such, the compiler is unable to determine the data type of the lotType property, for which it assumes there should be either a public variabl logType within the SHOLOG class, or a getLogType() function. I suspect the issue if the former, as the latter typically produces a different error. From: rules-users-bounces(a)lists.jboss.org [mailto:rules-users-bounces@lists.jboss.org] On Behalf Of Mahadevappa, Shobha Sent: Wednesday, November 07, 2012 3:48 AM To: rules-users(a)lists.jboss.org Subject: [rules-users] Decision table errors Hi, I have a decision table which has an invalid column. Drools gives the below compilation error but I am not sure about what is the line number (highlighted in red below) it is referring to in the error message. Any pointers towards this is greatly appreciated. Unable to Analyse Expression logType_41 == "2101": Error: unable to resolve method using strict-mode: com.keane.nREAP.util.generatedclasses.SHOLOG.logType_41()] Near : {... logType_41 == "2101" ....}] ^ [Line: 8, Column: 19] : [Rule name='VerificationAgain_12'] Regards, Shobha M | Senior Program Manager, A&AD | NTT DATA Global Delivery Services Limited| w. +91-80-26659482 (Ext 3679) | v. 8814.3679 | m. +91.9972522743 | shobha.mahadevappa@nttdata.com<mailto:shobha.mahadevappa@nttdata.com> ______________________________________________________________________ Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding ______________________________________________________________________ Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding

Thanks. That really answers my question. Can you please let me know if there is an option to view the generated DRL source ? Regards, Shobha M shobha.mahadevappa@nttdata.com<mailto:shobha.mahadevappa@nttdata.com> From: rules-users-bounces(a)lists.jboss.org [mailto:rules-users-bounces@lists.jboss.org] On Behalf Of Welsh, Armand Sent: 08 November 2012 AM 12:00 To: Rules Users List Subject: Re: [rules-users] Decision table errors They are the location in the DRL source where there error occurs. Since each row is translated into a rule, the row number is the number in the rule name. And the line is the line in that' rule. From: rules-users-bounces(a)lists.jboss.org [mailto:rules-users-bounces@lists.jboss.org] On Behalf Of Mahadevappa, Shobha Sent: Wednesday, November 07, 2012 9:24 AM To: Rules Users List Subject: Re: [rules-users] Decision table errors Thanks. I am aware of the error. But I am not aware of the significance of the line and column number in the error message. They are for sure not the row number in the excel. Regards, Shobha M From: rules-users-bounces@lists.jboss.org<mailto:rules-users-bounces@lists.jboss.org> [mailto:rules-users-bounces@lists.jboss.org] On Behalf Of Welsh, Armand Sent: 07 November 2012 PM 10:27 To: rules-users@lists.jboss.org<mailto:rules-users@lists.jboss.org> Subject: Re: [rules-users] Decision table errors It looks like you SHOLOG class does not have an import in your Drools Package, or you have an import, but the drools compiler cannot find the class specified with a type that is compatible with the "2101" string argument. As such, the compiler is unable to determine the data type of the lotType property, for which it assumes there should be either a public variabl logType within the SHOLOG class, or a getLogType() function. I suspect the issue if the former, as the latter typically produces a different error. From: rules-users-bounces@lists.jboss.org<mailto:rules-users-bounces@lists.jboss.org> [mailto:rules-users-bounces@lists.jboss.org] On Behalf Of Mahadevappa, Shobha Sent: Wednesday, November 07, 2012 3:48 AM To: rules-users@lists.jboss.org<mailto:rules-users@lists.jboss.org> Subject: [rules-users] Decision table errors Hi, I have a decision table which has an invalid column. Drools gives the below compilation error but I am not sure about what is the line number (highlighted in red below) it is referring to in the error message. Any pointers towards this is greatly appreciated. Unable to Analyse Expression logType_41 == "2101": Error: unable to resolve method using strict-mode: com.keane.nREAP.util.generatedclasses.SHOLOG.logType_41()] Near : {... logType_41 == "2101" ....}] ^ [Line: 8, Column: 19] : [Rule name='VerificationAgain_12'] Regards, Shobha M | Senior Program Manager, A&AD | NTT DATA Global Delivery Services Limited| w. +91-80-26659482 (Ext 3679) | v. 8814.3679 | m. +91.9972522743 | shobha.mahadevappa@nttdata.com<mailto:shobha.mahadevappa@nttdata.com> ______________________________________________________________________ Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding ______________________________________________________________________ Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding ______________________________________________________________________ Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding

I take it you are not using Drools Guvnor. If you are, you can do a View Source on the tab where you upload the decision table. With native java, it's a bit more complex, as you need to extract the source. Wolfgang responded with the package used for that, so I will bow out. From: rules-users-bounces(a)lists.jboss.org [mailto:rules-users-bounces@lists.jboss.org] On Behalf Of Mahadevappa, Shobha Sent: Wednesday, November 07, 2012 9:37 PM To: Rules Users List Subject: Re: [rules-users] Decision table errors Thanks. That really answers my question. Can you please let me know if there is an option to view the generated DRL source ? Regards, Shobha M shobha.mahadevappa@nttdata.com<mailto:shobha.mahadevappa@nttdata.com> From: rules-users-bounces(a)lists.jboss.org [mailto:rules-users-bounces@lists.jboss.org] On Behalf Of Welsh, Armand Sent: 08 November 2012 AM 12:00 To: Rules Users List Subject: Re: [rules-users] Decision table errors They are the location in the DRL source where there error occurs. Since each row is translated into a rule, the row number is the number in the rule name. And the line is the line in that' rule. From: rules-users-bounces(a)lists.jboss.org [mailto:rules-users-bounces@lists.jboss.org] On Behalf Of Mahadevappa, Shobha Sent: Wednesday, November 07, 2012 9:24 AM To: Rules Users List Subject: Re: [rules-users] Decision table errors Thanks. I am aware of the error. But I am not aware of the significance of the line and column number in the error message. They are for sure not the row number in the excel. Regards, Shobha M From: rules-users-bounces@lists.jboss.org<mailto:rules-users-bounces@lists.jboss.org> [mailto:rules-users-bounces@lists.jboss.org] On Behalf Of Welsh, Armand Sent: 07 November 2012 PM 10:27 To: rules-users@lists.jboss.org<mailto:rules-users@lists.jboss.org> Subject: Re: [rules-users] Decision table errors It looks like you SHOLOG class does not have an import in your Drools Package, or you have an import, but the drools compiler cannot find the class specified with a type that is compatible with the "2101" string argument. As such, the compiler is unable to determine the data type of the lotType property, for which it assumes there should be either a public variabl logType within the SHOLOG class, or a getLogType() function. I suspect the issue if the former, as the latter typically produces a different error. From: rules-users-bounces@lists.jboss.org<mailto:rules-users-bounces@lists.jboss.org> [mailto:rules-users-bounces@lists.jboss.org] On Behalf Of Mahadevappa, Shobha Sent: Wednesday, November 07, 2012 3:48 AM To: rules-users@lists.jboss.org<mailto:rules-users@lists.jboss.org> Subject: [rules-users] Decision table errors Hi, I have a decision table which has an invalid column. Drools gives the below compilation error but I am not sure about what is the line number (highlighted in red below) it is referring to in the error message. Any pointers towards this is greatly appreciated. Unable to Analyse Expression logType_41 == "2101": Error: unable to resolve method using strict-mode: com.keane.nREAP.util.generatedclasses.SHOLOG.logType_41()] Near : {... logType_41 == "2101" ....}] ^ [Line: 8, Column: 19] : [Rule name='VerificationAgain_12'] Regards, Shobha M | Senior Program Manager, A&AD | NTT DATA Global Delivery Services Limited| w. +91-80-26659482 (Ext 3679) | v. 8814.3679 | m. +91.9972522743 | shobha.mahadevappa@nttdata.com<mailto:shobha.mahadevappa@nttdata.com> ______________________________________________________________________ Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding ______________________________________________________________________ Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding ______________________________________________________________________ Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding