Re: 3.3 to 4.0 migration

Youngho Cho <[email protected]> Fri, 26 Sep 2014 17:06:39 +0900
Newsgroups gmane.comp.jakarta.turbine.torque.user
Message-ID <CAFD_z_-HdEjEoawRGMRDhB0o5fV4q9hk1HiArH7DCvasnhfTgw@mail.gmail.com>
Hello Thomas,

I got generator error for DECIMAL TYPE

<table name=3D"JETTIGER_COORDINATE" idMethod=3D"native"
javaName=3D"Coordinate" description=3D"Geometric data Information">
    <!--
        Unique identifier.
    -->
    <column name=3D"COORDINATE_ID" primaryKey=3D"true" required=3D"true"
type=3D"BIGINT"></column>
    <!--
        Longitude
    -->
    <column name=3D"LONGITUDE" required=3D"true" size=3D"8,5" type=3D"DECIM=
AL"></column>
    <!--
        Latitude
    -->
    <column name=3D"LATITUDE" required=3D"true" size=3D"7,5" type=3D"DECIMA=
L"></column>
    <!--
    Altitude
    -->
    <column name=3D"ALTITUDE" required=3D"false" type=3D"INTEGER"></column>
    <index name=3D"IX_COORDINATE">
        <index-column name=3D"LONGITUDE"/>
        <index-column name=3D"LATITUDE"/>
    </index>
</table>

the error stack trace is

INFO  org.apache.torque.generator.control.Controller -
readConfiguration() : Starting to read configuration files
INFO  org.apache.torque.generator.control.Controller -
readConfiguration() : Configuration read.
INFO  org.apache.torque.generator.control.Controller - Processing
output torque.om.dbObject
INFO  org.apache.torque.generator.control.Controller - Processing
source D:\projectSvn\MPROJECT_TORQUE_EXTERNAL_SCHEMA\core\src\main\torque\s=
chema\.\easydesk-schema.xml
[ERROR]
org.apache.torque.generator.source.SourceException: Error parsing XML
source file: cvc-datatype-valid.1.2.1: '8,5' is not a valid value for
'decimal'.
    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:147)
    at org.apache.torque.generator.source.SourceImpl.getRootElement(SourceI=
mpl.java:48)
    at org.apache.torque.generator.control.Controller.processSourceInOutput=
(Controller.java:326)
    at org.apache.torque.generator.control.Controller.processOutput(Control=
ler.java:297)
    at org.apache.torque.generator.control.Controller.processGenerationUnit=
(Controller.java:232)
    at org.apache.torque.generator.control.Controller.run(Controller.java:1=
43)
    at org.apache.torque.generator.maven.TorqueGeneratorMojo.execute(Torque=
GeneratorMojo.java:693)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(Defaul=
tBuildPluginManager.java:132)


How can I fix it ?


Thanks,

Youngho


2014-09-25 22:56 GMT+09:00 Thomas Fox <[email protected]>:
> I have personally never used the getRelatedObjects(Criteria) methods and =
do not like that they cache their results.
>
> However, since the results are cached and serialized, and it is unclear h=
ow the result was obtained except for the cached criteria,
> in my opinion the criteria which was used to obtain the result should als=
o be serialized.
>
> Personally, I'd prefer not to cache the result of getRelatedObjects(Crite=
ria), but I'm afraid there are users which rely on it.
>
>    Thomas
>
> Youngho Cho wrote:
>
> Hello Thomas,
>
> I read the torque-4.1 generator generated file.
> and I have one question
>
> When "torque.om.objectIsCaching" set true
> Than following Criteria object set.
>
>     /**
>      * The criteria used to select the current contents of $field
>      */
>     private Criteria $criteriaCacheField =3D null;
>
>
> During 3.3, I have always curious that Why we don't use transient keyword=
 likes
>
> private transient Criteria $criteriaCacheField =3D null;
>
> is there any merit to keep this object during serialization process ?
>
>
> Thanks,
>
> Youngho
>
>
> 2014-09-24 21:27 GMT+09:00 Youngho Cho <[email protected]>:
>> Hello Thomas,
>>
>>
>> Thanks for your kind consideration.
>>
>> Youngho
>>
>> 2014-09-24 21:07 GMT+09:00 Thomas Fox <[email protected]>:
>>>> It will be great if schema-reference document exists like torque-3.3
>>>> https://db.apache.org/torque/torque-3.3/releases/torque-3.3/generator/=
schema-reference.html
>>>
>>>
>>> I created a jira issue for it.
>>>
>>>    Thomas
>>>
>>>
>>> ----- Urspr=FCngliche Mail -----
>>> Von: "Youngho Cho" <[email protected]>
>>> An: "Thomas Fox" <[email protected]>
>>> Gesendet: Mittwoch, 24. September 2014 07:11:02
>>> Betreff: Re: 3.3 to 4.0 migration
>>>
>>> Hello Thomas,
>>>
>>> Ah
>>> I read
>>> https://issues.apache.org/jira/browse/TORQUE-309
>>>
>>> I understand Why my previous email error happened.
>>>
>>> It will be great if schema-reference document exists like torque-3.3
>>> https://db.apache.org/torque/torque-3.3/releases/torque-3.3/generator/s=
chema-reference.html
>>>
>>> than the toque 4.0 user can understand much more it.
>>>
>>>
>>> Thanks,
>>>
>>> Youngho
>>>
>>>
>>> 2014-09-24 13:53 GMT+09:00 Youngho Cho <[email protected]>:
>>>> 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.Log4jLoggin=
gAdapter
>>>> - 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=
(XmlSourceFormat.java:143)
>>>>     at org.apache.torque.generator.source.stream.FileSource.createRoot=
Element(FileSource.java:134)
>>>>     at org.apache.torque.generator.source.SourceImpl.getRootElement(So=
urceImpl.java:48)
>>>>     at org.apache.torque.generator.control.Controller.processSourceInO=
utput(Controller.java:256)
>>>>     at org.apache.torque.generator.control.Controller.processOutput(Co=
ntroller.java:228)
>>>>     at org.apache.torque.generator.control.Controller.processGeneratio=
nUnit(Controller.java:181)
>>>>     at org.apache.torque.generator.control.Controller.run(Controller.j=
ava:111)
>>>>     at org.apache.torque.generator.maven.TorqueGeneratorMojo.execute(T=
orqueGeneratorMojo.java:678)
>>>>     at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(D=
efaultBuildPluginManager.java:101)
>>>>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoEx=
ecutor.java:209)
>>>>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoEx=
ecutor.java:153)
>>>>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoEx=
ecutor.java:145)
>>>>     at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buil=
dProject(LifecycleModuleBuilder.java:84)
>>>>     at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buil=
dProject(LifecycleModuleBuilder.java:59)
>>>>     at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThre=
adedBuild(LifecycleStarter.java:183)
>>>>     at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(Li=
fecycleStarter.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(NativeMethodAccesso=
rImpl.java:57)
>>>>     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMetho=
dAccessorImpl.java:43)
>>>>     at java.lang.reflect.Method.invoke(Method.java:606)
>>>>     at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhance=
d(Launcher.java:290)
>>>>     at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launch=
er.java:230)
>>>>     at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitC=
ode(Launcher.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.createSAXParseExcept=
ion(Unknown
>>>> Source)
>>>>     at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source=
)
>>>>     at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Sou=
rce)
>>>>     at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Sou=
rce)
>>>>     at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Sou=
rce)
>>>>     at org.apache.xerces.impl.xs.XMLSchemaValidator$XSIErrorReporter.r=
eportError(Unknown
>>>> Source)
>>>>     at org.apache.xerces.impl.xs.XMLSchemaValidator.reportSchemaError(=
Unknown
>>>> Source)
>>>>     at org.apache.xerces.impl.xs.XMLSchemaValidator.processAttributes(=
Unknown
>>>> Source)
>>>>     at org.apache.xerces.impl.xs.XMLSchemaValidator.handleStartElement=
(Unknown
>>>> Source)
>>>>     at org.apache.xerces.impl.xs.XMLSchemaValidator.startElement(Unkno=
wn Source)
>>>>     at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElemen=
t(Unknown
>>>> Source)
>>>>     at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentC=
ontentDispatcher.dispatch(Unknown
>>>> Source)
>>>>     at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocum=
ent(Unknown
>>>> Source)
>>>>     at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Sour=
ce)
>>>>     at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Sour=
ce)
>>>>     at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
>>>>     at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Sourc=
e)
>>>>     at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknow=
n Source)
>>>>     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=
(XmlSourceFormat.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 genera=
ted 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=
 changed the templates this should not bother you. If you have changed the =
templates, you can now specifically overwrite specific templates, no need t=
o copy 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 c=
urrently, if you feel this would be an improvement please add a feature req=
uest to the torque issue tracker.
>>>>>>
>>>>>>   Thanks,
>>>>>>
>>>>>>           Thomas
>>>>>>
>>>>>> ----- Urspr=FCngliche 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 a=
sk.
>>>>>>>
>>>>>>>
>>>>>>> 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=FCngliche 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]> w=
rote:
>>>>>>>>>
>>>>>>>>> Hello
>>>>>>>>>
>>>>>>>>> I am preparing torque 3.3 to 4.0 migration.
>>>>>>>>>
>>>>>>>>> I read torque-4.0/documentation/orm-reference/migration-from-torq=
ue-3.html.
>>>>>>>>> But I hope to know more detail information.
>>>>>>>>>
>>>>>>>>> Is there any more detail document / information for migration pro=
cess ?
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> 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]
>>>>>>