I finally got back to trying this.  Unfortunately, it had no effect.  I
looked at the list of generated java files, and I can see that several
names have "By" in them, so I know it took effect, but my monstrously
long source file name is still there (no "By" in it). 

> -----Original Message-----
> From: Werner Guttmann [mailto:[EMAIL PROTECTED] 
> Sent: Friday, June 01, 2007 11:45 AM
> To: [email protected]
> Subject: Re: [castor-user] How to avoid too-long file names
> 
> David,
> 
> can you please read through
> 
> http://www.castor.org/srcgen-binding.html#Class-generation-conflicts
> 
> and try to switch to 'TYPE' strategy.
> 
> Regards
> Werner
> 
> Karr, David wrote:
> > I'm using automatic conflict resolution, and the name conflict 
> > strategy is "informViaLog".
> > 
> >> -----Original Message-----
> >> From: Werner Guttmann [mailto:[EMAIL PROTECTED]
> >> Sent: Friday, June 01, 2007 2:01 AM
> >> To: [email protected]
> >> Subject: Re: [castor-user] How to avoid too-long file names
> >>
> >> David,
> >>
> >> just to clear up a few assumptions, you are using automatic naming 
> >> resolution, right ? And you are using the default resolution 
> >> strategy, which happens to be XPATH based ?
> >>
> >> Werner
> >>
> >> Karr, David wrote:
> >>> Although the too-long file names create some annoyances, the big 
> >>> problem I have right now is that I get a bizarre compile
> >> error when I
> >>> try to compile it.  I see something like this (somewhat elided):
> >>>
> >>>     [javac]
> >>>
> >> 
> ...\RealECXMLTransactionProductListProductAppraisalInfoPriceOpinionIn
> >> f
> >>> oC
> >>>
> >> 
> omparisonPropertyListComparisonPropertyUnitBreakdownUnitList.java:57:
> >>> cannot access
> >>>
> >> 
> ...RealECXMLTransactionProductListProductAppraisalInfoPriceOpinionInf
> >> o
> >>> Co mparisonPropertyListComparisonPropertyUnitBreakdownUnitListUnit
> >>>     [javac] bad class file:
> >>>
> >> 
> ...\RealECXMLTransactionProductListProductAppraisalInfoPriceOpinionIn
> >> f
> >>> oC
> >>>
> >> 
> omparisonPropertyListComparisonPropertyUnitBreakdownUnitListUnit.clas
> >> s
> >>>     [javac] class file contains wrong class: java.util.Vector
> >>>     [javac] Please remove or make sure it appears in the correct 
> >>> subdirectory of the classpath.
> >>>     [javac]             final
> >>>
> >> 
> ...RealECXMLTransactionProductListProductAppraisalInfoPriceOpinionInf
> >> o
> >>> Co mparisonPropertyListComparisonPropertyUnitBreakdownUnitListUnit
> >>> vUnit)
> >>>     [javac]                                               
>         ^
> >>>     [javac] 1 error
> >>>
> >>>> -----Original Message-----
> >>>> From: Karr, David
> >>>> Sent: Thursday, May 31, 2007 12:32 PM
> >>>> To: [email protected]
> >>>> Subject: [castor-user] How to avoid too-long file names
> >>>>
> >>>> I have a schema provided by a vendor that I have to
> >> generate classes
> >>>> for.  Because of its structure, it tends to create source
> >> files that
> >>>> are too long for DOS, which creates all kinds of 
> annoyances.  It's 
> >>>> very deep in anonymous element-complexType components.  Is there 
> >>>> something I can do, without modifying the schema, and hopefully 
> >>>> without modifying the code that references the generated 
> code (in 
> >>>> decreasing order of
> >>>> importance) so that it creates reasonably-sized names?
> >>>>
> >>>>
> >> 
> ---------------------------------------------------------------------
> >>>> To unsubscribe from this list please visit:
> >>>>
> >>>>     http://xircles.codehaus.org/manage_email
> >>>>
> >>>>
> >>>
> >> 
> ---------------------------------------------------------------------
> >>> To unsubscribe from this list please visit:
> >>>
> >>>     http://xircles.codehaus.org/manage_email
> >>>
> >>
> >> 
> ---------------------------------------------------------------------
> >> To unsubscribe from this list please visit:
> >>
> >>     http://xircles.codehaus.org/manage_email
> >>
> >>
> > 
> > 
> ---------------------------------------------------------------------
> > To unsubscribe from this list please visit:
> > 
> >     http://xircles.codehaus.org/manage_email
> > 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe from this list please visit:
> 
>     http://xircles.codehaus.org/manage_email
> 
> 

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

Reply via email to