[ 
https://issues.apache.org/jira/browse/OFBIZ-5452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14213564#comment-14213564
 ] 

Pranay Pandey commented on OFBIZ-5452:
--------------------------------------

This issue is already fixed in ofbiz.13.07 release & trunk. The methods 
invoiceSequence-enforced and invoiceSequence-restart have been renamed to 
invoiceSequenceEnforced & invoiceSequenceRestart respectively in 
applications/accounting/script/org/ofbiz/accounting/invoice/InvoiceServices.xml 
file.

Exists in 12.04, will provide a patch for it.


> Illegal simple methods name
> ---------------------------
>
>                 Key: OFBIZ-5452
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-5452
>             Project: OFBiz
>          Issue Type: Bug
>          Components: accounting
>    Affects Versions: Release Branch 12.04
>            Reporter: Sergei Biletnikov
>            Priority: Minor
>
> /applications/accounting/script/org/ofbiz/accounting/invoice/InvoiceServices.xml
> script, has two methods wich do not follow the necessary method name pattern. 
> invoiceSequence-enforced
> invoiceSequence-restart
> As result, the log file contains the following errors:
> UtilXml.java:1060:ERROR] XmlFileLoader: File 
> file:/D:/Projects/OFBiz-12.04-AP/applications/accounting/script/org/ofbiz/accounting/invoice/InvoiceServices.xml
>  process error. Line: 77. Error message: cvc-pattern-valid: Value 
> 'invoiceSequence-enforced' is not facet-valid with respect to pattern 
> '[a-zA-Z_]{1}[a-zA-Z0-9_$.]+' for type 'javaClassName'.
> UtilXml.java:1060:ERROR] XmlFileLoader: File 
> file:/D:/Projects/OFBiz-12.04-AP/applications/accounting/script/org/ofbiz/accounting/invoice/InvoiceServices.xml
>  process error. Line: 77. Error message: cvc-attribute.3: The value 
> 'invoiceSequence-enforced' of attribute 'method-name' on element 
> 'simple-method' is not valid with respect to its type, 'javaClassName'.
> etc.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to