RE: [transfer-dev] Re: XML error on upgrade
Hi Brian, The only specific cache config I have on a site I’m trying to get to work with the latest Transfer version is: objectCache cache class=emc scope type=none / /cache /objectCache Is there any easy way to replace this? Thanks, James. --- James Allen E: ja...@jamesallen.name Blog: http://jamesallen.name Twitter: @CFJamesAllen Twitter: @JamesAllenVoice (Voiceover) Twitter: @80sRewindShow (My weekly 80s radio show) Tune in to the best in community radio – Codebass Radio: http://codebassradio.net From: transfer-dev@googlegroups.com [mailto:transfer-dev@googlegroups.com] On Behalf Of Brian G Sent: 23 July 2014 18:08 To: transfer-dev@googlegroups.com Subject: [transfer-dev] Re: XML error on upgrade On Tuesday, July 22, 2014 9:47:11 AM UTC-7, Tom McNeer wrote: Is there any documentation for the use of the new caching configuration? And are there other known areas where an old config might cause errors? Tom, My apologies, this was so long ago for me I forgot it all changed. Here's what you need to change your objectCache stanza in transfer.xml to: objectCache defaultcache provider=transfer.com.cache.provider.EHCacheProvider setting name=config value=transfer/ehcache.xml / /defaultcache /objectCache For an example, this is mine with some examples of objects for which I've specified no caching:: objectCache defaultcache provider=transfer.com.cache.provider.EHCacheProvider setting value=/path/to/ehcache.xml name=config/ /defaultcache cache provider=transfer.com.cache.provider.NoCacheProvider class=package.object/ cache provider=transfer.com.cache.provider.NoCacheProvider class=package2.object2/ cache provider=transfer.com.cache.provider.NoCacheProvider class=package2.object3/ /objectCache To get started, create an ehcache.xml file with one default cache: ?xml version=1.0 encoding=UTF-8? ehcache xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:noNamespaceSchemaLocation=http://ehcache.org/ehcache.xsd; defaultCache maxElementsInMemory=1000 eternal=false timeToIdleSeconds=120 timeToLiveSeconds=900 overflowToDisk=false / /ehcache Converting from transfer.xml, timeToIdleSeconds replaces accessedminutestimeout and timeToLiveSeconds replaces maxminutespersisted. If you specify eternal=true, then the timeouts are ignored and the only thing that will cause an object to be discarded from the cache is running into the maxElementsInMemory limit. If you want to get fancier, these are just a standard ehcache configuration file so you can use the docs here for more tunable options: http://ehcache.org/documentation/user-guide/configuration For an example, here is my ehcache.xml: ?xml version=1.0 encoding=UTF-8? ehcache xsi:noNamespaceSchemaLocation=http://ehcache.org/ehcache.xsd; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; defaultCache overflowToDisk=false eternal=true maxElementsInMemory=350/ !-- eternal for big objects -- cache overflowToDisk=false eternal=true maxElementsInMemory=750 name=event.event/ cache overflowToDisk=false eternal=true maxElementsInMemory=300 name=track.track/ !-- fine tune away from the defaults -- cache overflowToDisk=false eternal=true maxElementsInMemory=500 name=member.member/ cache overflowToDisk=false eternal=true maxElementsInMemory=1000 name=member.clubmember/ !-- short lived, eternal = false with ttl -- cache overflowToDisk=false eternal=false maxElementsInMemory=750 name=user.user timeToIdleSeconds=900/ cache overflowToDisk=false eternal=false maxElementsInMemory=1500 name=user.authrole timeToIdleSeconds=900/ /ehcache Don't forget to delete all of your *.transfer files when upgrading! (which, now based on the github repo, will actually be *.transfer.cfm files) -- -- Before posting questions to the group please read: http://groups.google.com/group/transfer-dev/web/how-to-ask-support-questions-on-transfer Try out the new Transfer ORM Custom Google Search: http://www.google.com/cse/home?cx=002375903941309441958:2s7wbd5ocb8 You received this message because you are subscribed to the Google Groups transfer-dev group. To post to this group, send email to transfer-dev@googlegroups.com To unsubscribe from this group, send email to transfer-dev+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/transfer-dev?hl=en --- You received this message because you are subscribed to the Google Groups transfer-dev group. To unsubscribe from this group and stop receiving emails from it, send an email to transfer-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- -- Before posting questions to the group please read: http://groups.google.com/group/transfer-dev/web/how-to-ask-support-questions-on-transfer Try out the new Transfer ORM Custom Google Search
Re: [transfer-dev] Re: XML error on upgrade
James, Does that just disable caching for the class emc? On Wednesday, July 23, 2014 10:18:58 AM UTC-7, James Allen wrote: objectCache cache class=emc scope type=none / /cache /objectCache -- -- Before posting questions to the group please read: http://groups.google.com/group/transfer-dev/web/how-to-ask-support-questions-on-transfer Try out the new Transfer ORM Custom Google Search: http://www.google.com/cse/home?cx=002375903941309441958:2s7wbd5ocb8 You received this message because you are subscribed to the Google Groups transfer-dev group. To post to this group, send email to transfer-dev@googlegroups.com To unsubscribe from this group, send email to transfer-dev+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/transfer-dev?hl=en --- You received this message because you are subscribed to the Google Groups transfer-dev group. To unsubscribe from this group and stop receiving emails from it, send an email to transfer-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [transfer-dev] Re: XML error on upgrade
On Wednesday, July 23, 2014 10:36:43 AM UTC-7, Brian G wrote: Does that just disable caching for the class emc? If that is the case, you can replace it with: objectCache cache class=emc provider=transfer.com.cache.provider.NoCacheProvider/ /objectCache I think that's a valid config - you don't have to have an external config file. -- -- Before posting questions to the group please read: http://groups.google.com/group/transfer-dev/web/how-to-ask-support-questions-on-transfer Try out the new Transfer ORM Custom Google Search: http://www.google.com/cse/home?cx=002375903941309441958:2s7wbd5ocb8 You received this message because you are subscribed to the Google Groups transfer-dev group. To post to this group, send email to transfer-dev@googlegroups.com To unsubscribe from this group, send email to transfer-dev+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/transfer-dev?hl=en --- You received this message because you are subscribed to the Google Groups transfer-dev group. To unsubscribe from this group and stop receiving emails from it, send an email to transfer-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [transfer-dev] Re: XML error on upgrade
Hi Brian and Mark, Thanks for your help, as always. While I haven't done any testing yet, the two blog entries Mark cites are very clear, and Brian's explanation here is even more complete. That's what I needed: just some documentation on what should go into the XML. Brian, I hope you can place Mark's old wiki content in GitHub. Like you, even though I no longer use Transfer for new development, I've built some rather large applications using it. And every now and then, there needs to be an update to those applications -- and I find myself saying I think I remember the syntax for that, but Thanks again to both of you. On Tue, Jul 22, 2014 at 8:08 PM, Mark Mandel mark.man...@gmail.com wrote: Tom, I just fired off to Brian the static copy of the wiki that was up on transfer-docs. I can't remember what in that in regards to the ehCache version. The XSD is the definitive reference, but you may also want to check out these blog posts from 2009: http://www.ghidinelli.com/2009/11/18/using-transfer-ehcache http://www.compoundtheory.com/sneak-peak-transfers-new-plug-able-cache/ Mark -- -- Before posting questions to the group please read: http://groups.google.com/group/transfer-dev/web/how-to-ask-support-questions-on-transfer Try out the new Transfer ORM Custom Google Search: http://www.google.com/cse/home?cx=002375903941309441958:2s7wbd5ocb8 You received this message because you are subscribed to the Google Groups transfer-dev group. To post to this group, send email to transfer-dev@googlegroups.com To unsubscribe from this group, send email to transfer-dev+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/transfer-dev?hl=en --- You received this message because you are subscribed to the Google Groups transfer-dev group. To unsubscribe from this group and stop receiving emails from it, send an email to transfer-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- Thanks, Tom Tom McNeer MediumCool http://www.mediumcool.com 1735 Johnson Road NE Atlanta, GA 30306 404.589.0560 On Wed, Jul 23, 2014 at 1:07 PM, Brian G brian-goo...@vfive.com wrote: On Tuesday, July 22, 2014 9:47:11 AM UTC-7, Tom McNeer wrote: Is there any documentation for the use of the new caching configuration? And are there other known areas where an old config might cause errors? Tom, My apologies, this was so long ago for me I forgot it all changed. Here's what you need to change your objectCache stanza in transfer.xml to: objectCache defaultcache provider=transfer.com.cache.provider.EHCacheProvider setting name=config value=transfer/ehcache.xml / /defaultcache /objectCache For an example, this is mine with some examples of objects for which I've specified no caching:: objectCache defaultcache provider=transfer.com.cache.provider.EHCacheProvider setting value=/path/to/ehcache.xml name=config/ /defaultcache cache provider=transfer.com.cache.provider.NoCacheProvider class=package.object/ cache provider=transfer.com.cache.provider.NoCacheProvider class=package2.object2/ cache provider=transfer.com.cache.provider.NoCacheProvider class=package2.object3/ /objectCache To get started, create an ehcache.xml file with one default cache: ?xml version=1.0 encoding=UTF-8? ehcache xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:noNamespaceSchemaLocation=http://ehcache.org/ehcache.xsd; defaultCache maxElementsInMemory=1000 eternal=false timeToIdleSeconds=120 timeToLiveSeconds=900 overflowToDisk=false / /ehcache Converting from transfer.xml, timeToIdleSeconds replaces accessedminutestimeout and timeToLiveSeconds replaces maxminutespersisted. If you specify eternal=true, then the timeouts are ignored and the only thing that will cause an object to be discarded from the cache is running into the maxElementsInMemory limit. If you want to get fancier, these are just a standard ehcache configuration file so you can use the docs here for more tunable options: http://ehcache.org/documentation/user-guide/configuration For an example, here is my ehcache.xml: ?xml version=1.0 encoding=UTF-8? ehcache xsi:noNamespaceSchemaLocation=http://ehcache.org/ehcache.xsd; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; defaultCache overflowToDisk=false eternal=true maxElementsInMemory=350/ !-- eternal for big objects -- cache overflowToDisk=false eternal=true maxElementsInMemory=750 name=event.event/ cache overflowToDisk=false eternal=true maxElementsInMemory=300 name=track.track/ !-- fine tune away from the defaults -- cache overflowToDisk=false eternal=true maxElementsInMemory=500 name=member.member/ cache overflowToDisk=false eternal=true maxElementsInMemory=1000 name=member.clubmember/ !-- short lived, eternal = false with ttl -- cache
