Re: 3.3 to 4.0 migration

Hi Youngho,

that feature is already implemented in trunk.
If you wish you can checkout the trunk and then this error should disappear=
.

   Thomas=20

----- Urspr=C3=BCngliche Mail -----
Youngho Cho wrote:

Hello Thomas,

In order to learn how torque-4.0 generator works

I tried to build

Turbine/Fulcrum/Torque Security module in trunk.

But I got following build error.

[INFO] --------------------------------------------------------------------=
----
[INFO] Building Fulcrum Security Torque Impl 1.1.0-SNAPSHOT
[INFO] --------------------------------------------------------------------=
----
[INFO]
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @
fulcrum-security-torque ---
[INFO]
[INFO] --- torque-maven-plugin:4.0:generate (torque-om) @
fulcrum-security-torque ---
INFO  org.apache.torque.generator.control.Controller -
readConfiguration() : Starting to read configuration files
INFO  org.apache.torque.generator.configuration.controller.Log4jLoggingAdap=
ter
- apply() : Setting loglevel to ERROR
[ERROR]
org.apache.torque.generator.source.SourceException: Error parsing XML
source file: cvc-complex-type.3.2.2: Attribute 'peerInterface' is not
allowed to appear in element 'table'.
    at org.apache.torque.generator.source.stream.XmlSourceFormat.parse(XmlS=
ourceFormat.java:143)
    at org.apache.torque.generator.source.stream.FileSource.createRootEleme=
nt(FileSource.java:134)
    at org.apache.torque.generator.source.SourceImpl.getRootElement(SourceI=
mpl.java:48)
    at org.apache.torque.generator.control.Controller.processSourceInOutput=
(Controller.java:256)
    at org.apache.torque.generator.control.Controller.processOutput(Control=
ler.java:228)
    at org.apache.torque.generator.control.Controller.processGenerationUnit=
(Controller.java:181)
    at org.apache.torque.generator.control.Controller.run(Controller.java:1=
11)
    at org.apache.torque.generator.maven.TorqueGeneratorMojo.execute(Torque=
GeneratorMojo.java:678)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(Defaul=
tBuildPluginManager.java:101)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecuto=
r.java:209)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecuto=
r.java:153)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecuto=
r.java:145)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProj=
ect(LifecycleModuleBuilder.java:84)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProj=
ect(LifecycleModuleBuilder.java:59)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedB=
uild(LifecycleStarter.java:183)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(Lifecyc=
leStarter.java:161)
    at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
    at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
    at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
    at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
    at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl=
.java:57)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcce=
ssorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:606)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Lau=
ncher.java:290)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.ja=
va:230)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(L=
auncher.java:409)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java=
:352)
Caused by: org.xml.sax.SAXParseException; lineNumber: 37;
columnNumber: 94; cvc-complex-type.3.2.2: Attribute 'peerInterface' is
not allowed to appear in element 'table'.
    at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(U=
nknown
Source)
    at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)
    at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
    at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
    at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
    at org.apache.xerces.impl.xs.XMLSchemaValidator$XSIErrorReporter.report=
Error(Unknown
Source)
    at org.apache.xerces.impl.xs.XMLSchemaValidator.reportSchemaError(Unkno=
wn
Source)
    at org.apache.xerces.impl.xs.XMLSchemaValidator.processAttributes(Unkno=
wn
Source)
    at org.apache.xerces.impl.xs.XMLSchemaValidator.handleStartElement(Unkn=
own
Source)
    at org.apache.xerces.impl.xs.XMLSchemaValidator.startElement(Unknown So=
urce)
    at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unk=
nown
Source)
    at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentConten=
tDispatcher.dispatch(Unknown
Source)
    at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(U=
nknown
Source)
    at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
    at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
    at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
    at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
    at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Sou=
rce)
    at org.apache.xerces.jaxp.SAXParserImpl.parse(Unknown Source)
    at javax.xml.parsers.SAXParser.parse(SAXParser.java:195)
    at org.apache.torque.generator.source.stream.XmlSourceFormat.parse(XmlS=
ourceFormat.java:132)
    ... 28 more
[INFO] --------------------------------------------------------------------=
----
[INFO] Reactor Summary:
[INFO]
[INFO] Fulcrum Security Master Build ..................... SUCCESS [2.042s]
[INFO] Fulcrum Security API .............................. SUCCESS [6.811s]
[INFO] Fulcrum Security Hibernate Impl ................... SUCCESS [28.787s=
]
[INFO] Fulcrum Security Memory Impl ...................... SUCCESS [10.053s=
]
[INFO] Fulcrum Security Torque Impl ...................... FAILURE [0.935s]
[INFO] --------------------------------------------------------------------=
----
[INFO] BUILD FAILURE
[INFO] --------------------------------------------------------------------=
----
[INFO] Total time: 48.893s
[INFO] Finished at: Wed Sep 24 13:49:11 KST 2014
[INFO] Final Memory: 20M/49M
[INFO] --------------------------------------------------------------------=
----
[ERROR] Failed to execute goal
org.apache.torque:torque-maven-plugin:4.0:generate (torque-om) on
project fulcrum-security-torque: Error parsing XML source file:
cvc-complex-type.3.2.2: Attribute 'peerInterface' is not allowed to
appear in element 'table'. -> [Help 1]
[ERROR]


How can I fix it ?

Thanks,

Youngho

2014-09-17 4:56 GMT+09:00 Thomas Fox <[email protected]>:
> Youngho Cho wrote:
> ....
>>
>> For the 4.0 generator usage,
>>
>> In my 3.3 schema xml
>>
>> I use database/baseClass like
>>
>> <database name=3D"@DATABASE_PROP_NAME@"
>>   baseClass=3D"com.nannet.jettiger.om.AbstractCache"
>>  defaultJavaType=3D"object">
>>
>> and in the AbstractCache class, I put common function for all generated =
class.
>>
>> In order to migrate to torque4, how to be a change ?
>>
> Hi Youngho,
>
> As far as I found you have different options
> - set the torque.om.dbObjectDefaultBaseClass generator option
> - set the baseClass attribute on the database element in the schema
> - set the baseClass attribute on the table element in the schema
>
> So your old method should still work.
>
>    Hope that helps,
>
>           Thomas
>
> 2014-09-12 17:21 GMT+09:00 Thomas Fox <[email protected]>:
>> Hello Youngho
>>
>>> ...
>>> The Generator looks like different
>>
>> Yes it is new-written and now better extensible. But if you have not cha=
nged the templates this should not bother you. If you have changed the temp=
lates, you can now specifically overwrite specific templates, no need to co=
py the whole tree.
>>
>>> ...
>>> Is there any plan to migrate JCS from 1.3.x to 2.x for torque4 ?
>>
>> Currently there is no plan I am aware of.  But I am working on 4.1 curre=
ntly, if you feel this would be an improvement please add a feature request=
 to the torque issue tracker.
>>
>>   Thanks,
>>
>>           Thomas
>>
>> ----- Urspr=C3=BCngliche Mail -----
>> Von: "Youngho Cho" <[email protected]>
>> An: "Thomas Fox" <[email protected]>
>> CC: "Apache Torque Users List" <[email protected]>
>> Gesendet: Freitag, 12. September 2014 10:11:15
>> Betreff: Re: 3.3 to 4.0 migration
>>
>> Hello Tomas,
>>
>> Quicky read the torque4 document,
>> I think I need some learing period for migration from 3.3.x to 4.x,
>>>
>> The BaseObject removed,
>> The Generator looks like different
>> and many chaned
>> I need a better understanding about torque4 before my application's
>> migration start.
>>
>> At this moment, I have a question.
>>
>> Is there any plan to migrate JCS from 1.3.x to 2.x for torque4 ?
>>
>> Thanks,
>>
>> Youngho
>>
>>
>>
>>
>>
>>
>>
>> 2014-09-09 9:23 GMT+09:00 Youngho Cho <[email protected]>:
>>> Hello Thomas,
>>>
>>> I am gathering an information for the migration at this moment.
>>>
>>> When I start the migration and have some specific question I will ask.
>>>
>>>
>>> Thanks,
>>>
>>> Youngho
>>>
>>> 2014-09-08 16:21 GMT+09:00 Thomas Fox <[email protected]>:
>>>> This is the only document i know in the official documentation.
>>>> Do you have any specific questions?
>>>>
>>>>    Thomas
>>>>
>>>>
>>>> ----- Urspr=C3=BCngliche Mail -----
>>>> Von: "Scott Eade" <[email protected]>
>>>> An: "Youngho Cho" <[email protected]>
>>>> CC: [email protected]
>>>> Gesendet: Sonntag, 7. September 2014 06:26:59
>>>> Betreff: Re: 3.3 to 4.0 migration
>>>>
>>>>
>>>>
>>>>> On 7 Sep 2014, at 12:22 pm, Youngho Cho <[email protected]> wrote=
:
>>>>>
>>>>> Hello
>>>>>
>>>>> I am preparing torque 3.3 to 4.0 migration.
>>>>>
>>>>> I read torque-4.0/documentation/orm-reference/migration-from-torque-3=
.html.
>>>>> But I hope to know more detail information.
>>>>>
>>>>> Is there any more detail document / information for migration process=
 ?
>>>>>
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Youngho
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> 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]
>>