Exception with XPath in Oxygen 6.1.1 and Eclipse 3.1

Post by **jokester01au** » Fri Aug 05, 2005 9:13 am

There appears to be a problem with the rendering of XPath results using Oxygen 6.1.1 in Eclipse 3.1 (release build I20050627-1435) on WinXP.

Whenever an XPath expression is entered which returns results, the following message is displayed

"1 XPath results is located outside the Eclipse's workspace and therefore, cannot be displayed."

If the XPath expression returns no results, the expected message appears.

This does not appear to be related to the file used, and can, for example, be reproduced using the samples/docbook/sample.xml file and the xpath "/book".

Regards,
Joe.

Post by **george** » Fri Aug 05, 2005 11:27 am

Hi Joe,

The XPath results are set as markers, therefore we need to have the files inside an Eclipse project, that is not as external files. In fact, most of the oXygen funtionality will be disabled in this case. Just create a project that contains your files and all the funstionality should be available.

Best Regards,
George

Post by **jokester01au** » Sun Aug 07, 2005 8:47 am

Hi George,

All files with which I have tried to access XPath expressions were indeed inside an Eclipse project.

You should be able to reproduce the bug (using the release build of eclipse 3.1) with the following steps:

1. Create a new eclipse project of type "Sample XML Project". Call it "Oxygen".
2. Open /Oxygen/samples/docbook/sample.xml.
3. Click the XPath toolbar icon.
4. Enter the XPath "/book".
5. The error message "XPath results is located outside the Eclipse's workspace and therefore, cannot be displayed." will appear.

Regards,
Joe.

Post by **george** » Mon Aug 08, 2005 9:22 am

Hi Joe,

Sorry if my reply was not clear enough. That message is displayed by oXygen, it is intended, it is not an unexpected error. It tells that the file you execute XPath on should be inside an Eclipse project otherwise the XPath results cannot be presented.

Best Regards,
George

Post by **jokester01au** » Wed Aug 10, 2005 4:31 am

Hi George,

What I am trying to say is that the files I unsuccessfully try to execute XPath on ARE inside an Eclipse project!

I cannot get Eclipse 3.1 with Oxygen 6.1.1 to execute an XPath on any files at all.

You should be able to recreate this issue yourself by creating an eclipse project using your samples and trying to run XPath on one of them (as shown in my previous post).

Regards,
Joe.

Post by **george** » Wed Aug 10, 2005 10:57 am

Hi Joe,

That is strange, we are not able to reproduce that.
Is there anything particular with your installation?

Best Regards,
George

Post by **jokester01au** » Tue Aug 16, 2005 2:32 am

Hi George,

I have isolated this problem to some degree. Previously, my various workspaces have resided within the directory

c:\JavaProjects

It appears that all of the workspaces within this directory display the same XPath problem.

I have now tried numerous workspaces outside this directory and all work fine.

Can you suggest any properties of this directory that might be causing this issue?

Regards,
Joe.

Post by **jokester01au** » Mon Sep 12, 2005 8:33 am

Hi George,

Further to my previous post, the bug temporarily disappeared when I moved my workspace to

C:\MyWorkspace

However, it has now reappeared within this workspace.

Can you suggest what I can do to identify what is raising this bug?

If it helps to diagnose the issue, I can send you my workspace metadata directory if you give me an email address.

Regards,
Joe.

Post by **sorin_ristache** » Mon Sep 12, 2005 12:09 pm

Hello,

jokester01au wrote:Can you suggest what I can do to identify what is raising this bug?

The target file for the XPath query is not included in the current workspace. Did you open the file with File - Open File and browsed to a directory outside the current workspace ?

Regards,
Sorin

Post by **jokester01au** » Tue Sep 13, 2005 1:48 am

Hi Sorin,

The target file for the XPath query is not included in the current workspace

Yes, it is. As I explained in previous posts, this bug occurs when trying to run XPath queries on XML documents INSIDE the workspace.

I believe it must have something to do with the workspace metadata, since changing workspaces makes it go away temporarily but it soon returns.

Regards,
Joe.

Post by **sorin_ristache** » Tue Sep 13, 2005 10:42 am

Hi,

jokester01au wrote:As I explained in previous posts, this bug occurs when trying to run XPath queries on XML documents INSIDE the workspace.

Can you provide a screenshot displaying both the current workspace with the queried file selected in the Navigator or Package Explorer and the error message dialog for the queried file opened with the <oXygen/> plugin ? Maybe we can see something wrong if we look at your Eclipse window.

Regards,
Sorin

Post by **sorin_ristache** » Tue Sep 13, 2005 11:10 am

Hi,

jokester01au wrote:If it helps to diagnose the issue, I can send you my workspace metadata directory if you give me an email address.

Please send the metadata directory and the screenshot that I requested in the previous post at support at oxygenxml dot com.

Regards,
Sorin