Skip to content
This repository has been archived by the owner on Feb 22, 2024. It is now read-only.

Registered transformer UI is not correct #8

Closed
ktk opened this issue Dec 3, 2015 · 10 comments
Closed

Registered transformer UI is not correct #8

ktk opened this issue Dec 3, 2015 · 10 comments
Assignees
@gaborremenyi

Comments

@ktk
Copy link

ktk commented Dec 3, 2015

The dashboard does not get the correct URI of a registered pipeline, all it sees is the base URI of the pipeline transformer. In the test-dialog of the pipeline UI the full URI is present and if I manually register a widget with this transformer URI it is fine.
@gaborremenyi
Copy link
Contributor

Fix with latest commit.

@ktk
Copy link
Author

ktk commented Jan 6, 2016

I just tried the latest version on Sandbox (timestamp 2015-12-30T08:33:20.242Z) as UI for playground by specifying a different platform URI. I created a new transformer, when I store it the URI it generates in the test is:

http://playground.fusepool.info:8300/?config=http%3A%2F%2Fplayground.fusepool.info%3A8181%2Fldp%2Ftr%2FL

No matter what I try this URI does not work. When I manually look it up in the LDP UI and execute it against

http://playground.fusepool.info:8300/?config=http://playground.fusepool.info:8181/ldp/tr/L

It works

@ktk ktk reopened this Jan 6, 2016
@ktk ktk mentioned this issue Jan 6, 2016
Closed
@ktk
Copy link
Author

ktk commented Jan 22, 2016

@gaborremenyi any updates to this? The issue is still not fixed and we have final review meeting in a few weeks.

@gaborremenyi
Copy link
Contributor

Sorry for the late response. However I think that the URI generated by the UI is correct. There was a problem a month ago where the pipeline transformer could not decode URL encoded config URIs. So my guess would be that playground is not using the latest the version of pipeline transformer, which would be this: https://github.com/fusepoolP3/p3-pipeline-transformer/releases/tag/v1.0.0-20151216

Can you update it on playground? Or should I ask Reto? I'll leave the issue open until then.

@ktk
Copy link
Author

ktk commented Jan 25, 2016

I didn't mention that but it doesn't seem to make a difference if I do it on sandbox, which is from this year.

@gaborremenyi
Copy link
Contributor

But it does make a difference, because the error messages are not the same.

On playground you get a MalformedURLException which was fixed in the latest pipeline. On sandbox the pipeline transformer simply just cannot establish a connection to http://playg
round.fusepool.info:8305/... which is the first transformer in the pipeline.

I still don't see any problem with the pipeline URI created by the UI.

$ curl -X GET "http://playground.fusepool.info:8300/?config=http%3A%2F%2Fplaygr
ound.fusepool.info%3A8181%2Fldp%2Ftr%2FL"
<html>
<head>
<meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1"/>
<title>Error 500 </title>
</head>
<body>
<h2>HTTP ERROR: 500</h2>
<p>Problem accessing /. Reason:
<pre>    java.lang.RuntimeException: java.net.MalformedURLException: no protocol
: http%3A%2F%2Fplayground.fusepool.info%3A8181%2Fldp%2Ftr%2FL</pre></p>
<hr /><i><small>Powered by Jetty://</small></i>
</body>
</html>

$ curl -X GET "http://sandbox.fusepool.info:8300/?config=http%3A%2F%2Fplaygroun
d.fusepool.info%3A8181%2Fldp%2Ftr%2FL"
<html>
<head>
<meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1"/>
<title>Error 500 </title>
</head>
<body>
<h2>HTTP ERROR: 500</h2>
<p>Problem accessing /. Reason:
<pre>    java.lang.RuntimeException: Cannot establish connection to http://playg
round.fusepool.info:8305/?transformer=http%3A%2F%2Fplayground.fusepool.info%3A83
04%2Ftransformers%2Fchain%2Falod-linking&amp;lit-pred=http%3A%2F%2Fpurl.org%2Fdc
%2Felements%2F1.1%2Ftitle&amp;lit-pred=http%3A%2F%2Fpurl.org%2Fdc%2Felements%2F1
.1%2Fdescription&amp;lit-pred=http%3A%2F%2Fdata.archiveshub.ac.uk%2Fdef%2Fnote !
</pre></p>
<hr /><i><small>Powered by Jetty://</small></i>
</body>
</html>

@ktk
Copy link
Author

ktk commented Jan 27, 2016

So I re-setup data.fusepool.info with latest versions of everything and indeed in here it seems to work! I close this as it looks fine so far, thanks!

@ktk ktk closed this as completed Jan 27, 2016
@retog
Copy link
Member

retog commented Jan 27, 2016

I'm confused, does it work on sandbox?

@ktk
Copy link
Author

ktk commented Jan 28, 2016

I need to try it on sandbox, never did a full pipeline there. What I did was using the sandbox UI with playground platform and that didn't work. I assume this was because playground was running an old version of the platform.

@gaborremenyi
Copy link
Contributor

I'm glad it's working now, let me know if you have any other issues with the UI.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@gaborremenyi gaborremenyi

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@retog @ktk @gaborremenyi