fatty- / daisy-pipeline

Automatically exported from code.google.com/p/daisy-pipeline
0 stars 0 forks source link

IllegalArgumentException: URI is not absolute #327

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
This is either an issue with output ports, or an issue with DTBook Validator. I 
suspect the former.

What steps will reproduce the problem?
1. Try validating a DTBook in Pipeline 2 v1.5

I'm using Ubuntu; have not tested on other OSs.

What is the expected output? What do you see instead?

#logback.classic pattern: %date [%-5level] %logger{36} - %msg%n
2013-06-19 12:36:25,111 [DEBUG] org.daisy.pipeline.push.Poster - Status changed 
23f520ef-87c2-4fa4-9dd2-ab235427f11d->RUNNING
2013-06-19 12:36:25,113 [INFO ] o.d.p.persistence.jobs.PersistentJob - Changing 
Status:RUNNING
2013-06-19 12:36:25,113 [DEBUG] o.d.p.persistence.jobs.PersistentJob - Updating 
object
2013-06-19 12:36:25,115 [DEBUG] o.d.p.p.jobs.PersistentJobContext - Post 
loading jobcontext
2013-06-19 12:36:25,116 [DEBUG] o.d.p.p.jobs.PersistentJobContext - load script 
XProcScript[name=DTBook Validator]
2013-06-19 12:36:25,116 [DEBUG] o.d.pipeline.job.JobContextFactory - 
configuring object 
org.daisy.pipeline.persistence.jobs.PersistentJobContext@825e33
2013-06-19 12:36:25,272 [DEBUG] o.d.c.x.c.DynamicXProcConfigurationFactory - 
Reading Calabash configuration from 
/home/jostein/Skrivebord/pipeline2-webui-1.5-desktop/etc/config-calabash.xml
2013-06-19 12:36:26,158 [DEBUG] o.d.c.x.c.DynamicXProcConfigurationFactory - 
Reading Calabash configuration from 
/home/jostein/Skrivebord/pipeline2-webui-1.5-desktop/etc/config-calabash.xml
2013-06-19 12:36:28,159 [ERROR] org.daisy.pipeline.job.Job - job finished with 
error state
java.lang.IllegalArgumentException: URI is not absolute
    at java.net.URI.toURL(URI.java:1095) ~[na:1.7.0_21]
    at org.daisy.common.xproc.calabash.CalabashXProcResult.writeTo(CalabashXProcResult.java:94) ~[na:na]
    at org.daisy.pipeline.job.AbstractJobContext.writeResult(AbstractJobContext.java:179) ~[na:na]
    at org.daisy.pipeline.persistence.jobs.PersistentJobContext.writeResult(PersistentJobContext.java:217) ~[na:na]
    at org.daisy.pipeline.job.Job.run(Job.java:154) ~[na:na]
    at org.daisy.pipeline.job.DefaultJobExecutionService$1.run(DefaultJobExecutionService.java:65) ~[na:na]
    at java.lang.Thread.run(Thread.java:722) ~[na:1.7.0_21]
2013-06-19 12:36:28,160 [DEBUG] org.daisy.pipeline.push.Poster - Status changed 
23f520ef-87c2-4fa4-9dd2-ab235427f11d->ERROR
2013-06-19 12:36:28,160 [INFO ] o.d.p.persistence.jobs.PersistentJob - Changing 
Status:ERROR
2013-06-19 12:36:28,160 [DEBUG] o.d.p.persistence.jobs.PersistentJob - Updating 
object
2013-06-19 12:36:28,161 [DEBUG] o.d.p.p.jobs.PersistentJobContext - Post 
loading jobcontext
2013-06-19 12:36:28,162 [DEBUG] o.d.p.p.jobs.PersistentJobContext - load script 
XProcScript[name=DTBook Validator]
2013-06-19 12:36:28,162 [DEBUG] o.d.pipeline.job.JobContextFactory - 
configuring object 
org.daisy.pipeline.persistence.jobs.PersistentJobContext@30346b90

Original issue reported on code.google.com by josteinaj@gmail.com on 19 Jun 2013 at 10:40

GoogleCodeExporter commented 9 years ago
was it in local mode?

Original comment by capitan....@gmail.com on 19 Jun 2013 at 10:49

GoogleCodeExporter commented 9 years ago
The error is in the framework not in the validator ( 90% sure of it)

Original comment by capitan....@gmail.com on 19 Jun 2013 at 10:50

GoogleCodeExporter commented 9 years ago
Yeah it was local mode. I rarely use remote mode so I haven't tested that.
Den 19. juni 2013 12:50 skrev <daisy-pipeline@googlecode.com> følgende:

Original comment by josteinaj@gmail.com on 19 Jun 2013 at 10:52

GoogleCodeExporter commented 9 years ago
I'll have a look into it,have you tried to pass absolute paths in the
output ports? as temporal work around it may work

Original comment by capitan....@gmail.com on 19 Jun 2013 at 11:11

GoogleCodeExporter commented 9 years ago
I've just been using the Web UI and haven't really checked what URIs it is 
passing. I assume it is absolute URIs, but I'll have a look.

Original comment by josteinaj@gmail.com on 19 Jun 2013 at 11:30

GoogleCodeExporter commented 9 years ago
(tested in remote mode; that works)

Original comment by josteinaj@gmail.com on 19 Jun 2013 at 11:56

GoogleCodeExporter commented 9 years ago
For what I understand, the uri that you're sending is relative, or the scheme 
is different from "file:/". Have a look, I could do something clever to 
overcome it the output part is going to change completely in the next weeks... 
so ;). Let me know if the issue is about the uri. 

Original comment by capitan....@gmail.com on 19 Jun 2013 at 2:48

GoogleCodeExporter commented 9 years ago
Thanks. I'll check when I get back to work tomorrow.
Den 19. juni 2013 16:48 skrev <daisy-pipeline@googlecode.com> følgende:

Original comment by josteinaj@gmail.com on 19 Jun 2013 at 3:07

GoogleCodeExporter commented 9 years ago
pipeline-clientlib-java didn't support output ports in jobRequests. (They were 
serialized as input ports instead).

fixed in 
https://github.com/daisy-consortium/pipeline-clientlib-java/commit/effb82292dd99
4b9d7765c1318deb7dcadbd9c81

Original comment by josteinaj@gmail.com on 24 Jun 2013 at 11:11