db-torque-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Thomas Fox <thomas....@seitenbau.com>
Subject Re: 3.3 to 4.0 migration
Date Thu, 25 Sep 2014 13:56:27 GMT
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 how the result was
obtained except for the cached criteria,
in my opinion the criteria which was used to obtain the result should also be serialized.

Personally, I'd prefer not to cache the result of getRelatedObjects(Criteria), 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 = null;


During 3.3, I have always curious that Why we don't use transient keyword likes

private transient Criteria $criteriaCacheField = null;

is there any merit to keep this object during serialization process ?


Thanks,

Youngho


2014-09-24 21:27 GMT+09:00 Youngho Cho <youngho1203@gmail.com>:
> Hello Thomas,
>
>
> Thanks for your kind consideration.
>
> Youngho
>
> 2014-09-24 21:07 GMT+09:00 Thomas Fox <thomas.fox@seitenbau.com>:
>>> 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üngliche Mail -----
>> Von: "Youngho Cho" <youngho1203@gmail.com>
>> An: "Thomas Fox" <thomas.fox@seitenbau.com>
>> 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/schema-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 <youngho1203@gmail.com>:
>>> 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.Log4jLoggingAdapter
>>> - 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.createRootElement(FileSource.java:134)
>>>     at org.apache.torque.generator.source.SourceImpl.getRootElement(SourceImpl.java:48)
>>>     at org.apache.torque.generator.control.Controller.processSourceInOutput(Controller.java:256)
>>>     at org.apache.torque.generator.control.Controller.processOutput(Controller.java:228)
>>>     at org.apache.torque.generator.control.Controller.processGenerationUnit(Controller.java:181)
>>>     at org.apache.torque.generator.control.Controller.run(Controller.java:111)
>>>     at org.apache.torque.generator.maven.TorqueGeneratorMojo.execute(TorqueGeneratorMojo.java:678)
>>>     at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
>>>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
>>>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>>>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>>>     at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
>>>     at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
>>>     at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
>>>     at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.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(DelegatingMethodAccessorImpl.java:43)
>>>     at java.lang.reflect.Method.invoke(Method.java:606)
>>>     at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
>>>     at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
>>>     at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(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.createSAXParseException(Unknown
>>> 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.reportError(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(Unknown Source)
>>>     at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown
>>> Source)
>>>     at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
>>> Source)
>>>     at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
>>> 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 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 <thomas.fox@seitenbau.com>:
>>>> Youngho Cho wrote:
>>>> ....
>>>>>
>>>>> For the 4.0 generator usage,
>>>>>
>>>>> In my 3.3 schema xml
>>>>>
>>>>> I use database/baseClass like
>>>>>
>>>>> <database name="@DATABASE_PROP_NAME@"
>>>>>   baseClass="com.nannet.jettiger.om.AbstractCache"
>>>>>  defaultJavaType="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 <thomas.fox@seitenbau.com>:
>>>>> 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 to 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 currently,
if you feel this would be an improvement please add a feature request to the torque issue
tracker.
>>>>>
>>>>>   Thanks,
>>>>>
>>>>>           Thomas
>>>>>
>>>>> ----- Ursprüngliche Mail -----
>>>>> Von: "Youngho Cho" <youngho1203@gmail.com>
>>>>> An: "Thomas Fox" <thomas.fox@seitenbau.com>
>>>>> CC: "Apache Torque Users List" <torque-user@db.apache.org>
>>>>> 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 <youngho1203@gmail.com>:
>>>>>> 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 <thomas.fox@seitenbau.com>:
>>>>>>> This is the only document i know in the official documentation.
>>>>>>> Do you have any specific questions?
>>>>>>>
>>>>>>>    Thomas
>>>>>>>
>>>>>>>
>>>>>>> ----- Ursprüngliche Mail -----
>>>>>>> Von: "Scott Eade" <scott@eade.id.au>
>>>>>>> An: "Youngho Cho" <youngho1203@gmail.com>
>>>>>>> CC: torque-user@db.apache.org
>>>>>>> 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 <youngho1203@gmail.com>
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: torque-user-unsubscribe@db.apache.org
>>>>>>> For additional commands, e-mail: torque-user-help@db.apache.org
>>>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org
>>>>> For additional commands, e-mail: torque-user-help@db.apache.org
>>>>>

---------------------------------------------------------------------
To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org
For additional commands, e-mail: torque-user-help@db.apache.org


Mime
View raw message