If you were using scomp dirToXsds/* that would work, but I'm not sure
with the maven plugin
-jacobd

On Wed, Feb 4, 2009 at 11:57 AM, Mike Wallace <[email protected]> wrote:
> I'm assuming all I need to do is create a file, like uddi_api.xsdconfig, and 
> drop it into the same schemas directory that all of the other schemas are.
>
> No luck so far.  It might be that Maven needs information on it.  I'll dig 
> into it.
>
> Thanks for the suggestion and quick response!
>
> Mike
>
>
> --- On Wed, 2/4/09, Jacob Danner <[email protected]> wrote:
>
>> From: Jacob Danner <[email protected]>
>> Subject: Re: Issues with Maven and XMLBeans
>> To: [email protected], [email protected]
>> Date: Wednesday, February 4, 2009, 2:34 PM
>> Interesting, I don't know the maven plugin, so I
>> can't comment as to
>> the what and why this is happening. As a workaround, have
>> you tried
>> using an xsdconfig file.
>> Something like
>> <xb:config
>> xmlns:xb="http://xml.apache.org/xmlbeans/2004/02/xbean/config";>
>>
>>   <xb:namespace uri="urn:uddi-org:api_v3">
>>     <xb:package>api_v3.uddi_org</xb:package>
>>   </xb:namespace>
>>
>> </xb:config>
>>
>> HTH,
>> -jacobd
>>
>> On Wed, Feb 4, 2009 at 11:21 AM, Mike Wallace
>> <[email protected]> wrote:
>> > Hi.  I'm attempting to generate classes using
>> XMLBeans 2.2.0 within a Maven build.  The XMLBeans Maven
>> Plugin version is 2.3.2.
>> > The problem I'm running into is that for some of
>> the Namespaces in the schema files, the package names
>> aren't being generated as expected.
>> >
>> >
>> > The namespace in question is urn:uddi-org:api_v3.
>> > I expect the package name to be api_v3.uddi_org.
>> > However, what I'm getting is uddiOrgApiV3.
>> >
>> > Are there any settings that can be used to control the
>> naming scheme?
>> > This seems to work as expected within an Ant task.
>> Unfortunately, I don't know enough about it to determine
>> what the differences are.
>> >
>> > Thanks,
>> > Mike
>> >
>> >
>> >
>> >
>> >
>> ---------------------------------------------------------------------
>> > To unsubscribe, e-mail:
>> [email protected]
>> > For additional commands, e-mail:
>> [email protected]
>> >
>> >
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to