Skip to content
This repository has been archived by the owner on Mar 25, 2020. It is now read-only.

Trying to use droitText with i-jetty: "Helvetica not found as resource" etc. #109

Open
GoogleCodeExporter opened this issue Mar 14, 2015 · 3 comments

Comments

@GoogleCodeExporter
Copy link

(This is cross-posted from 
http://code.google.com/p/droidtext/issues/detail?id=4 since it is related to 
i-jetty)

What steps will reproduce the problem?
1. Create a project for a webapp packaged for i-jetty as per 
http://code.google.com/p/i-jetty/wiki/DownloadableWebapps
2. Add dependency to droidText http://code.google.com/p/droidtext/ in pom.xml 
(made available through our local maven repo)
3. Build and deploy the webapp to i-jetty as described (tried on emulator only 
so far)

What is the expected output? What do you see instead?
The project has a servlet that will produce a sample PDF, instead it fails with 
the following error in logcat:  
"Helvetica not found as resource. (The *.afm files must exist as resources in 
the package com.lowagie.text.pdf.fonts)"

What version of the product are you using? On what operating system?
i-jetty 3.1, droidText 0.2, Android 4.2 on emulator

Please provide any additional information below.
This seems to be a packaging issue. I noticed that the "dx" tool only packages 
classes, not resources. So, how do I make resources available at runtime ? 

Attached is a sample project that demonstrates this issue.

Original issue reported on code.google.com by [email protected] on 21 Nov 2012 at 8:19

Attachments:

@GoogleCodeExporter
Copy link
Author

Still stuck at the same point. 
Any idea about this ?

Original comment by [email protected] on 10 Dec 2012 at 10:36

@GoogleCodeExporter
Copy link
Author

I think the apk tool takes out all the resources out of the dependent jars and 
puts them into the apk. However, if you're making a standard weabpp, then you 
don't have an apk.

One solution would be to make an apk that contains jetty and your webapp code 
and static resources. So you would be using jetty embedded with your webapp, 
rather than making a webapp and deploying it to a standalone jetty.

Jan

Original comment by [email protected] on 2 Feb 2013 at 12:16

@GoogleCodeExporter
Copy link
Author

Thanks. Since this was a Proof-of-concept I have given up on this and moved to 
other solutions.

Original comment by [email protected] on 4 Feb 2013 at 3:02

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant