Re: [jexl] ETA for Jexl version 3.2?

[Gary Gregory]

I'm not close to the JEXL component but the best way to get the ball
rolling is a JIRA ticket and PR on GitHub with at least a failing unit test
and a fix if you are up for it.

Gary

On Wed, Oct 30, 2019 at 2:16 PM Lukas Schmitt 
wrote:

> henrib wrote
> > If you can, please check the snapshot does not introduce regressions on
> > your
> > end .
>
> We are indeed seeing a regression in the 3.2-SNAPSHOT version. Evaluating
> the following expression with chained method calls results in an
> unresolvable property exception for methodA:
>
> 'x.methodA().methodB()'
>
> This works in version 3.0 and 3.1.
>
> Let me know if you need more details to reproduce this issue or if I should
> rather raise an issue in Jira.
>
>
>
> --
> Sent from:
> http://apache-commons.680414.n4.nabble.com/Commons-User-f735979.html
>
> -
> To unsubscribe, e-mail: user-unsubscr...@commons.apache.org
> For additional commands, e-mail: user-h...@commons.apache.org
>
>

Re: [jexl] ETA for Jexl version 3.2?

[Lukas Schmitt]

henrib wrote
> If you can, please check the snapshot does not introduce regressions on
> your
> end .

We are indeed seeing a regression in the 3.2-SNAPSHOT version. Evaluating
the following expression with chained method calls results in an
unresolvable property exception for methodA:

'x.methodA().methodB()'

This works in version 3.0 and 3.1. 

Let me know if you need more details to reproduce this issue or if I should
rather raise an issue in Jira.



--
Sent from: http://apache-commons.680414.n4.nabble.com/Commons-User-f735979.html

-
To unsubscribe, e-mail: user-unsubscr...@commons.apache.org
For additional commands, e-mail: user-h...@commons.apache.org

Re: commons-vfs-2.4.1 - Question re. usage of VFS.getManager() - SOLVED

[Erwin Hogeweg]

Hi Bernd,

Thanks for your reply. When I tried this again today 

VFS.getManager().getSchemes()

returns the following (impressive) list of schemes:

[zip, par, ftps, res, ftp, sar, war, file, gz, tmp, http4s, ear, ejb3, 
jar, sftp, http4, ram]

and 

VFS.getManager().resolveFile("ftp://ftp.gnu.org/README;, opts);

works as expected. So I don’t know what happened but it looks like I spent a 
lot of time chasing a ghost. Oh well, at least I learned a thing or two.

Thanks for your help anyway.


Erwin




> 
> I think the problem in your case is that the default filesystem manager does 
> not know about the ftp: scheme. The error message is a bit missleading (since 
> a fix done, probably we should file a bug for this).
> 
> The default manager does try to load the FtpProvider and tries to register it 
> with ftp: so I assume loading of the provider failed. Maybe you are missing 
> dependencies like commons-net (see the website for the dependencies per 
> provider).
> 
> For debugging you can print manager.getSchemes() to see the available schemes 
> (providers).
> Gruss
> Bernd
> 
> 
> --
> http://bernd.eckenfels.net
> 
> 
> Von: Erwin Hogeweg 
> Gesendet: Mittwoch, Oktober 30, 2019 3:29 AM
> An: Commons Users List
> Betreff: commons-vfs-2.4.1 - Question re. usage of VFS.getManager()
> 
> All -
> 
> I am trying to set up a VFS but I struggled a while to get past a 
> FileSystemException. After looking at the VFS source code I understood what 
> was going on, and I was able to create a work-around. However, I am not sure 
> that what I hacked together is the right approach so I am looking for some 
> guidance from the experts here…
> 
> This is what I was trying to do:
> 
> FileObject path = VFS.getManager().resolveFile("ftp://ftp.gnu.org/README;, 
> new FileSystemOptions());
> 
> The issue is, or at least appears to be, that the FileSystemManager doesn’t 
> have a baseFile so the resolveFile blows up with this exception:
> 
> org.apache.commons.vfs2.FileSystemException: Could not find file with URI 
> "ftp://ftp.gnu.org/README; because it is a relative path, and no base URI was 
> provided.
> at 
> org.apache.commons.vfs2.FileSystemException.requireNonNull(FileSystemException.java:87)
> 
> I could not find how/where to define that baseFile so I eventually settled on 
> this work-around:
> 
> StandardFileSystemManager fsManager = (StandardFileSystemManager) 
> VFS.getManager(); // YUCK!
> fsManager.setBaseFile(new File("")); // Another YUCK.
> FileObject path = fsManager.resolveFile("ftp://ftp.gnu.org/README;, opts);
> 
> That works, and now I end up with the correct (expected) path. It doesn’t 
> feel right though so any advice would be greatly appreciated.
> 
> 
> Cheers,
> 
> Erwin
> 
>