Latest version of Transfer Issue

[James Allen]

Hi guys,

 

I’m trying a site which is built using Transfer on the latest version of Railo so grabbed Brian’s Github latest as I read that’s compatible.

 

The problem is, I’m getting the following error when I try to start the site – it occurs in the init of TransferFactory.

 

Railo reports the error as:

 

Syntax Error, Invalid Construct:

 

CF8:

 

Missing argument name.:When using named parameters to a function, every parameter must have a name.<p>The CFML compiler was processing:<ul><li>An expression beginning with super.init, on line 35, column 17.This message is usually caused by a problem in the expressions structure.<li>A script statement beginning with super.init on line 35, column 17.<li>A cfscript tag beginning on line 34, column 10.<li>A cfscript tag beginning on line 34, column 10.</ul>

 

So it’s not a Railo issue.

 

I’ve tracked this down I think and it’s occurring in com/factory/AbstractBaseFactory.cfc in the getSingleton() method.

 

If I use cftry to trap the error it occurs when getSingleton() is sent a class name of:

 

transfer.com.util.JavaLoader

 

Any ideas on what might be causing this on the latest version of Transfer? The site works fine on an older version.

 

Many 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

 

[Brian G]

James,

If you dump the argument in the working version of Transfer, what do you see?

If you can dump the stack trace, we can look at the call before that and see if it's not passing in a named argument?   But generally I find that these errors are unrelated to what they claim to be.  I would put some logging/try/catch up a level in the stack trace to see if what you're getting is what you're expecting.

E.g., in this case, Transfer has its own version of Javaloader IIRC - is it conflicting with another one on your system so JavaLoader itself is blowing up on init which manifests itself as this error?  These errors inside frameworks I often find to be nearly useless so cflog/dump/try/catch becomes necessary.

I unfortunately don't have a Railo setup to help with. 

One other quick suggestion:

do a diff on the github transfer compare to the version you've been using.  In reality there aren't THAT many changes.  I made a couple of the ones I saw for Railo compatibility in the list but maybe I missed something that I need from your version?


Brian

[Tom McNeer]

Brian,

I haven't had a chance to do a diff yet, but I thought I'd let you know: after correcting my XML, I started an application on ACF 9, and got the same exact error as James.

--
--
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 transf...@googlegroups.com
To unsubscribe from this group, send email to transfer-dev...@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...@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

[James Allen]

Ah that’s good to know Tom. Good to rule out something on my system that could be causing it.

 

Looks like we’ll have to do some digging into the framework to establish what the issue is.

 

---

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

 

[James Allen]

Right I’ve made some progress on this.

 

The reason for this error is that com/util/javaloader/javaloader.cfc is corrupted.

 

It’s got some weird text in it like <<<<<<< HEAD and seems to repeat itself half way down with the comment intro block.

 

I have replaced it with Javaloader from an older release of transfer but now I’m getting this error:

 

… com\util\javaloader\support\cfcdynamicproxy\lib\cfcdynamicproxy.jar does not exist

 

Any ideas?

 

Cheers,

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: transf...@googlegroups.com [mailto:transf...@googlegroups.com] On Behalf Of Tom McNeer

Sent: 23 July 2014 20:56
To: transf...@googlegroups.com
Subject: Re: [transfer-dev] Re: Latest version of Transfer Issue

 

Brian,

[Sean Coyne]

<<<<<<< HEAD 

means there was a bad merge at some point either from SVN or Git.  Because I also see ">>>>>>> master" then I think its probably a bad Git merge since I imported it from SVN.

Brian may need to go back to the relevant commit that added that and figure out what is the correct code and fix it.

Sean

[Sean Coyne]

OK, looks like it was this commit

https://github.com/ghidinelli/transfer/commit/14d574eb8b9dc97d8a672564e79bdc7e43e5208c

It added some bad merge info into other files as well.

Looks like the merge conflicts were committed before they were resolved.

[Sean Coyne]

I have updated this in my fork.  I can't send a pull request since mine is actually the original (Brian if you want me to transfer the original to you let me know)

Brian, if you pull in this commit https://github.com/seancoyne/transfer/commit/c64a2c2eab3d38cc9f771ee22c259fd5a1080cf4

It should remove the bad merge info from the two affected files.

Sean

[Sean Coyne]

it turns out I can create a pull request.  I submitted one so it should be easier to pull in the fix if desired.

[Brian G]

I merged Sean's changes in - sorry about that, I somehow missed the conflict in that file.  I hadn't switched to this version yet because I had a lot of debug logging still in mine in case the xmlSearch() thing didn't solve the problem but now that I feel confident that's all good (production has been 100% on startups under load for the last two weeks), I'll dogfood this rev too.

[Brian G]

Apparently my git-fu is teh suck.  There are a number of changes from my repo that aren't in Github yet so I obviously did something wrong.  I also see the error now so I'll get it running and report back when I have it working.

[Brian G]

Ok, I have it running.  Somehow Sean's import from SVN did not include JavaLoader:

https://github.com/seancoyne/transfer/tree/master/com/util/javaloader

The directory is empty and was missing the lib.  I took the opportunity to upgrade to JavaLoader 1.1 from 2012 and now have Transfer 1.3 from Github working in my environment (ACF10).   I believe you guys can pull down from Github now and run as-is. 



Brian

[Tom McNeer]

Brian,

Cool. Thanks very much. I'll check it out later today.

Thanks again for all the hard work.

--

--
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 transf...@googlegroups.com
To unsubscribe from this group, send email to transfer-dev...@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...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Brian G]

James reported that it's working on ACF now but he's getting the following error on Railo 4.2.1.  I don't have a Railo install handy to debug; can anyone find a patch and I'll merge it in?  Or you can send me a pull request on Github?

Error while attempting to autowire object of type transfer.com.cache.CacheManager:<br/>[Line: 30 :: /transfer/com/exception/Exception.cfc :: Error while attempting to autowire object of type transfer.com.cache.provider.ProviderManager :: <br/>[Line: 88 :: /transfer/com/cache/provider/EHCacheProvider.cfc :: coldfusion/runtime/NeoPageContext :: ]]

This is line 88 in EHCacheProvider.cfc:

            proxy = getJavaLoader().create("com.compoundtheory.coldfusion.cfc.CFCDynamicProxy").createInstance(this, interfaces);
 

It's not the first use of JavaLoader, so that's not the problem.   However, Mark seems to say that EHCacheProvider won't work on Railo in this 2010 thread:

https://groups.google.com/d/msg/transfer-dev/9x3i6aaBGlI/DDihZGuSMxkJ

Is that still true?  I thought we had people here running the pluggable_cache variant on Railo?

Brian

On Wednesday, July 23, 2014 10:17:49 AM UTC-7, James Allen wrote:

[Sean Coyne]

Is there a test case I can run on Railo?

[Mark Mandel]

Oh yeah, the ehcache branch uses the JL DynamicProxy, which uses internal CF classes... which would have an issue on Railo.

I *think* Railo ships with it's own implementation, so in theory, you should be able to switch them out at runtime.

Sean: Just check the tests folder, Transfer is well unit tested.

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 transf...@googlegroups.com
To unsubscribe from this group, send email to transfer-dev...@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...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
E: mark....@gmail.com
T: http://www.twitter.com/neurotic
W: www.compoundtheory.com

2 Devs from Down Under Podcast

http://www.2ddu.com/

[Sean Coyne]

Hmmm no tests dir in the git repo.  Looks like they were separate from the main SVN repo? Are these them?  http://svn.riaforge.org/transfer/cfunittest/trunk/

I'll see if I can integrate them into the main repo as well.

Sean

[Mark Mandel]

I think you'll want these ones:

http://svn.riaforge.org/transfer/cfunittest/branches/pluggable_cache/

Since you are working off the pluggable cache branch.

Mark

[Sean Coyne]

From what I can tell that branch is the same as trunk... at least there are no changes to the ones I tried yesterday.

[Mark Mandel]

Comparing:

http://transfer.riaforge.org/index.cfm?event=page.svnbrowse&path=%2Fcfunittest/trunk

to

http://transfer.riaforge.org/index.cfm?event=page.svnbrowse&path=%2Fcfunittest%2Fbranches/pluggable_cache

Looks like you may well be right. 

Mark