On Fri, Dec 12, 2008 at 1:53 PM, Tomáš Fecko <[email protected]> wrote:
> Well, it get's me pretty confused, when I tryied my 1.3.2 project under > 1.4RC1 yestarday, and it throws on me like 50 warnings... > funny is, that also examples are doing that, as I gues you are speaking > about here... :-) > > 2008/12/12 Simon Laws <[email protected]> > > >> >> On Fri, Dec 12, 2008 at 12:29 PM, Ramkumar R <[email protected]>wrote: >> >>> I am noticing the following error messages.... >>> >>> SEVERE: XMLSchema validation error occured in: null ,line = 1, column = >>> 776, Message = cvc-datatype-valid.1.2.1: >>> 'addService#AddServiceComponentB/AddService' is not a valid value for >>> 'QName'. >>> Dec 12, 2008 5:49:08 PM >>> org.apache.tuscany.sca.contribution.processor.ValidatingXMLStreamReader >>> SEVERE: XMLSchema validation error occured in: null ,line = 1, column = >>> 776, Message = cvc-attribute.3: The value >>> 'addService#AddServiceComponentB/AddService' of attribute 'name' on element >>> 'binding.sca' is not valid with respect to its typ >>> e, 'QName'. >>> Dec 12, 2008 5:49:08 PM >>> org.apache.tuscany.sca.contribution.processor.ValidatingXMLStreamReader >>> SEVERE: XMLSchema validation error occured in: null ,line = 1, column = >>> 1,002, Message = cvc-datatype-valid.1.2.1: >>> 'subtractService#SubtractServiceComponentC/SubtractService' is not a valid >>> value for 'QName'. >>> Dec 12, 2008 5:49:08 PM >>> org.apache.tuscany.sca.contribution.processor.ValidatingXMLStreamReader >>> SEVERE: XMLSchema validation error occured in: null ,line = 1, column = >>> 1,002, Message = cvc-attribute.3: The value >>> 'subtractService#SubtractServiceComponentC/SubtractService' of attribute >>> 'name' on element 'binding.sca' is not valid with r >>> espect to its type, 'QName'. >>> Dec 12, 2008 5:49:08 PM >>> org.apache.tuscany.sca.contribution.processor.ValidatingXMLStreamReader >>> SEVERE: XMLSchema validation error occured in: null ,line = 1, column = >>> 1,248, Message = cvc-datatype-valid.1.2.1: >>> 'multiplyService#MultiplyServiceComponentA/MultiplyServiceImpl' is not a >>> valid value for 'QName'. >>> Dec 12, 2008 5:49:08 PM >>> org.apache.tuscany.sca.contribution.processor.ValidatingXMLStreamReader >>> SEVERE: XMLSchema validation error occured in: null ,line = 1, column = >>> 1,248, Message = cvc-attribute.3: The value >>> 'multiplyService#MultiplyServiceComponentA/MultiplyServiceImpl' of attribute >>> 'name' on element 'binding.sca' is not valid wi >>> th respect to its type, 'QName'. >>> Dec 12, 2008 5:49:08 PM >>> org.apache.tuscany.sca.contribution.processor.ValidatingXMLStreamReader >>> SEVERE: XMLSchema validation error occured in: null ,line = 1, column = >>> 1,494, Message = cvc-datatype-valid.1.2.1: >>> 'divideService#DivideServiceComponentA/DivideServiceImpl' is not a valid >>> value for 'QName'. >>> Dec 12, 2008 5:49:08 PM >>> org.apache.tuscany.sca.contribution.processor.ValidatingXMLStreamReader >>> SEVERE: XMLSchema validation error occured in: null ,line = 1, column = >>> 1,494, Message = cvc-attribute.3: The value >>> 'divideService#DivideServiceComponentA/DivideServiceImpl' of attribute >>> 'name' on element 'binding.sca' is not valid with res >>> pect to its type, 'QName'. >>> >>> for the composite that looks like this..... >>> >>> <composite xmlns="http://www.osoa.org/xmlns/sca/1.0" >>> targetNamespace="http://sample" >>> xmlns:sample="http://sample" >>> name="CalculatorA"> >>> >>> <component name="CalculatorServiceComponentA"> >>> <implementation.java class="calculator.CalculatorServiceImpl"/> >>> <reference name="addService" target="AddServiceComponentB" /> >>> >>> <reference name="subtractService" >>> target="SubtractServiceComponentC" /> >>> <reference name="multiplyService" >>> target="MultiplyServiceComponentA"/> >>> <reference name="divideService" target="DivideServiceComponentA" >>> /> >>> </component> >>> >>> <component name="MultiplyServiceComponentA"> >>> <implementation.java class="calculator.MultiplyServiceImpl" /> >>> </component> >>> >>> <component name="DivideServiceComponentA"> >>> <implementation.java class="calculator.DivideServiceImpl" /> >>> </component> >>> >>> </composite> >>> >>> Looks like the name of the binding calculated automatically for a default >>> binding scenario, seems have issues. >>> >>> -- >>> Thanks & Regards, >>> Ramkumar Ramalingam >>> >> >> So this is calculator-distributed right? Has this just started or have you >> only just noticed it? What has changed around binding name generation or >> validation? >> >> Simon >> > > > > -- > Tomas Fecko > Yep, it seems that in the latest code we are throwing errors in cases that we didn't used to for some reason. Simon
