[ http://issues.apache.org/jira/browse/TUSCANY-178?page=comments#action_12376767 ]
Frank Budinsky commented on TUSCANY-178: ---------------------------------------- There are actually two ways to control the package name for SDO codegen. 1) the sdoJava:package attribute and 2) by passing a package name to the code generator (e.g., -javaPackage net..webserivce). Would it be possible that the correct/matching name be passed to the SDO generator this way? Trying to just rely on the SDO mangling to be what we want seems bad. There are discussions going on in the SDO spec group about whether or not SDO should specify a default algorithm for this - if they do, there's no guarantee it will be exactly the matching one we want. > Diffrent algorithms used to map uri to java package name. > --------------------------------------------------------- > > Key: TUSCANY-178 > URL: http://issues.apache.org/jira/browse/TUSCANY-178 > Project: Tuscany > Type: Bug > Components: Java SCA Model, Java SDO Implementation, Java SDO Tools > Environment: Current SVN, all > Reporter: Rick Rineholt > Priority: Blocker > > If you have wsdl that has no sdojava:package attribute and there are no > javaPackage specified in the POM for sdo generation different algorithms are > used to convert URI targetnamespace for the package names of: the generated > interface package name, the interface packagename at load time if > dynamically generated and the SDO types that are generated to define the > types used in the interface methods. There are scenarios where these only > differ by case (http://www.bigbank.com/Account maps to com.bigbank.Account > and com.bigbank.account) Note on windows based environment these can't be > co-located. > I believe the sca-plugin and the loadtime are using: > org.apache.tuscany.model.util.XMLNameUtil methods. > Have not located where mangling of SDO types are generated is. > Tuscany needs one central place where this is done. For both packagenames and > class names from uri and types to be consistent. I think if SDO is doing this > it is the common denominator. > This will continue to be a place of contention and methods/(class) used to do > this mangling should be configurable (ie.by factory or registering with SDO > ). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
