Vector graphics in Flying Saucer / ERPDFWrapper

Discussion:

Ricardo Parada

2015-11-17 17:01:48 UTC

Hi all,

We use ERPDFWrapper to generate PDF from a WOComponent. It comes out beautiful.

One of our components includes a logo using the <img> html tag and the logo is usually a .gif or .jpg. However, I would like to use vector graphics. We took a .eps file and converted it to .pdf in Photoshop. The resulting image scales beautifully to any size. When I try to use the .pdf I get java.lang.ClassCastException: org.xhtmlrenderer.pdf.PDFAsImage cannot be cast to org.xhtmlrenderer.pdf.ITextFSImage.

Has anybody been able to use vector graphics in ERPDFWrapper?

Thanks

The stack trace is below:

java.lang.ClassCastException: org.xhtmlrenderer.pdf.PDFAsImage cannot be cast to org.xhtmlrenderer.pdf.ITextFSImage
at org.xhtmlrenderer.pdf.ITextUserAgent.getImageResource(ITextUserAgent.java:97)
at org.xhtmlrenderer.pdf.ITextReplacedElementFactory.createReplacedElement(ITextReplacedElementFactory.java:57)
at er.pdf.builder.ERPDFReplacedElementFactory.createReplacedElement(ERPDFReplacedElementFactory.java:50)
at org.xhtmlrenderer.render.BlockBox.calcMinMaxWidth(BlockBox.java:1439)
at org.xhtmlrenderer.render.BlockBox.calcMinMaxWidthInlineChildren(BlockBox.java:1584)
at org.xhtmlrenderer.render.BlockBox.calcMinMaxWidth(BlockBox.java:1481)
at org.xhtmlrenderer.newtable.TableBox$AutoTableLayout.recalcColumn(TableBox.java:1240)
at org.xhtmlrenderer.newtable.TableBox$AutoTableLayout.fullRecalc(TableBox.java:1214)
at org.xhtmlrenderer.newtable.TableBox$AutoTableLayout.calcMinMaxWidth(TableBox.java:1509)
at org.xhtmlrenderer.newtable.TableBox.calcMinMaxWidth(TableBox.java:158)
at org.xhtmlrenderer.newtable.TableBox.layout(TableBox.java:221)
at org.xhtmlrenderer.layout.BlockBoxing.layoutBlockChild0(BlockBoxing.java:321)
at org.xhtmlrenderer.layout.BlockBoxing.layoutBlockChild(BlockBoxing.java:299)
at org.xhtmlrenderer.layout.BlockBoxing.layoutContent(BlockBoxing.java:90)
at org.xhtmlrenderer.render.BlockBox.layoutChildren(BlockBox.java:926)
at org.xhtmlrenderer.render.BlockBox.layout(BlockBox.java:806)
at org.xhtmlrenderer.render.BlockBox.layout(BlockBox.java:735)
at org.xhtmlrenderer.layout.BlockBoxing.layoutBlockChild0(BlockBoxing.java:321)
at org.xhtmlrenderer.layout.BlockBoxing.layoutBlockChild(BlockBoxing.java:299)
at org.xhtmlrenderer.layout.BlockBoxing.layoutContent(BlockBoxing.java:90)
at org.xhtmlrenderer.render.BlockBox.layoutChildren(BlockBox.java:926)
at org.xhtmlrenderer.render.BlockBox.layout(BlockBox.java:806)
at org.xhtmlrenderer.render.BlockBox.layout(BlockBox.java:735)
at org.xhtmlrenderer.pdf.ITextRenderer.layout(ITextRenderer.java:216)
at er.pdf.builder.FlyingSaucerImpl.setSource(FlyingSaucerImpl.java:99)
at er.pdf.ERPDFUtilities.htmlAsPdf(ERPDFUtilities.java:123)
at er.pdf.ERPDFWrapper.responseAsPdf(ERPDFWrapper.java:75)
at er.pdf.ERPDFWrapper.appendToResponse(ERPDFWrapper.java:60)
at com.webobjects.appserver.WOComponent.appendToResponse(WOComponent.java:1122)
at er.extensions.components.ERXComponent.appendToResponse(ERXComponent.java:117)
at er.extensions.components.ERXNonSynchronizingComponent.appendToResponse(ERXNonSynchronizingComponent.java:73)
at com.mpv.webcomponents.MPVWOComponent.appendToResponse(MPVWOComponent.java:67)
at com.webobjects.appserver.WOSession.appendToResponse(WOSession.java:1385)
at er.extensions.appserver.ERXSession.appendToResponse(ERXSession.java:552)
...

Samuel Pelletier

2015-11-17 19:20:32 UTC

Permalink

Hi Ricardo,

I do not know if it possible using ERPDFWrapper but I suggest to try svg images (directly embedded and using object element). SVG is the only vector format that is almost universally supported on web browser.

I know my own solution works for vector images and do font embedding. If you deploy on a Mac or can access a Mac from your server, my PDF generator would works. This server app render HTML with Webkit and print it to PDF.

https://github.com/Kaviju/Html2PdfServer <https://github.com/Kaviju/Html2PdfServer>

Samuel

Post by Ricardo Parada
Hi all,
We use ERPDFWrapper to generate PDF from a WOComponent. It comes out beautiful.
One of our components includes a logo using the <img> html tag and the logo is usually a .gif or .jpg. However, I would like to use vector graphics. We took a .eps file and converted it to .pdf in Photoshop. The resulting image scales beautifully to any size. When I try to use the .pdf I get java.lang.ClassCastException: org.xhtmlrenderer.pdf.PDFAsImage cannot be cast to org.xhtmlrenderer.pdf.ITextFSImage.
Has anybody been able to use vector graphics in ERPDFWrapper?
Thanks
java.lang.ClassCastException: org.xhtmlrenderer.pdf.PDFAsImage cannot be cast to org.xhtmlrenderer.pdf.ITextFSImage
at org.xhtmlrenderer.pdf.ITextUserAgent.getImageResource(ITextUserAgent.java:97)
at org.xhtmlrenderer.pdf.ITextReplacedElementFactory.createReplacedElement(ITextReplacedElementFactory.java:57)
at er.pdf.builder.ERPDFReplacedElementFactory.createReplacedElement(ERPDFReplacedElementFactory.java:50)
at org.xhtmlrenderer.render.BlockBox.calcMinMaxWidth(BlockBox.java:1439)
at org.xhtmlrenderer.render.BlockBox.calcMinMaxWidthInlineChildren(BlockBox.java:1584)
at org.xhtmlrenderer.render.BlockBox.calcMinMaxWidth(BlockBox.java:1481)
at org.xhtmlrenderer.newtable.TableBox$AutoTableLayout.recalcColumn(TableBox.java:1240)
at org.xhtmlrenderer.newtable.TableBox$AutoTableLayout.fullRecalc(TableBox.java:1214)
at org.xhtmlrenderer.newtable.TableBox$AutoTableLayout.calcMinMaxWidth(TableBox.java:1509)
at org.xhtmlrenderer.newtable.TableBox.calcMinMaxWidth(TableBox.java:158)
at org.xhtmlrenderer.newtable.TableBox.layout(TableBox.java:221)
at org.xhtmlrenderer.layout.BlockBoxing.layoutBlockChild0(BlockBoxing.java:321)
at org.xhtmlrenderer.layout.BlockBoxing.layoutBlockChild(BlockBoxing.java:299)
at org.xhtmlrenderer.layout.BlockBoxing.layoutContent(BlockBoxing.java:90)
at org.xhtmlrenderer.render.BlockBox.layoutChildren(BlockBox.java:926)
at org.xhtmlrenderer.render.BlockBox.layout(BlockBox.java:806)
at org.xhtmlrenderer.render.BlockBox.layout(BlockBox.java:735)
at org.xhtmlrenderer.layout.BlockBoxing.layoutBlockChild0(BlockBoxing.java:321)
at org.xhtmlrenderer.layout.BlockBoxing.layoutBlockChild(BlockBoxing.java:299)
at org.xhtmlrenderer.layout.BlockBoxing.layoutContent(BlockBoxing.java:90)
at org.xhtmlrenderer.render.BlockBox.layoutChildren(BlockBox.java:926)
at org.xhtmlrenderer.render.BlockBox.layout(BlockBox.java:806)
at org.xhtmlrenderer.render.BlockBox.layout(BlockBox.java:735)
at org.xhtmlrenderer.pdf.ITextRenderer.layout(ITextRenderer.java:216)
at er.pdf.builder.FlyingSaucerImpl.setSource(FlyingSaucerImpl.java:99)
at er.pdf.ERPDFUtilities.htmlAsPdf(ERPDFUtilities.java:123)
at er.pdf.ERPDFWrapper.responseAsPdf(ERPDFWrapper.java:75)
at er.pdf.ERPDFWrapper.appendToResponse(ERPDFWrapper.java:60)
at com.webobjects.appserver.WOComponent.appendToResponse(WOComponent.java:1122)
at er.extensions.components.ERXComponent.appendToResponse(ERXComponent.java:117)
at er.extensions.components.ERXNonSynchronizingComponent.appendToResponse(ERXNonSynchronizingComponent.java:73)
at com.mpv.webcomponents.MPVWOComponent.appendToResponse(MPVWOComponent.java:67)
at com.webobjects.appserver.WOSession.appendToResponse(WOSession.java:1385)
at er.extensions.appserver.ERXSession.appendToResponse(ERXSession.java:552)
...
_______________________________________________
Do not post admin requests to the list. They will be ignored.
https://lists.apple.com/mailman/options/webobjects-dev/samuel%40samkar.com

Timo Hoepfner

2015-11-17 20:33:03 UTC

Permalink

Hi Ricardo,

not at my work machine currently, but I came across a similar problem recently. In my case I tried to use a PDF as background image and got the same error. Updating flying saucer to a more recent version solved the issue for me. The jars Iâm currently using are flying-saucer-core-9.0.8.jar and flying-saucer-pdf-9.0.8.jar. I think they replace the core-renderer-20101006.jar in ERPDFGeneration. The commit youâre after is probably this one:

https://github.com/flyingsaucerproject/flyingsaucer/commit/26bf700857252ac04ecadd98dc0f8a2209e3c7f8

HTH,

Timo

Ricardo Parada

2015-11-18 21:28:37 UTC

Permalink

Thank you Timo and Samuel for your responses.

The easiest for me was to just update the flying saucer library to 9.0.8 as Timo suggested. I can now use the .pdf logo with vector graphics. The logo now looks beautiful on the Retina display.

Post by Samuel Pelletier
Hi Ricardo,
https://github.com/flyingsaucerproject/flyingsaucer/commit/26bf700857252ac04ecadd98dc0f8a2209e3c7f8
HTH,
Timo

Ricardo Parada

2015-11-30 18:40:05 UTC

Permalink

Hi all,

I was trying to create a pull request to remove core-rederer-20101006.jar from ERPDFGeneration and add flying-saucer-core-9.0.8.jar and flying-saucer-pdf-9.0.8.jar.

However the fork I have of wonder on my github account is really old and Iâm confused how to go about doing this. Iâm not even sure what branch to put it on. My fork of wonder only has master, integration, and Wonder_5_0_0_Legacy. I was expecting to see master, wonder_5, wonder_6 and wonder_7.

Is there any documentation on how to go about submitting a pull request for wonder?

Thanks
Ricardo

Post by Ricardo Parada
Thank you Timo and Samuel for your responses.
The easiest for me was to just update the flying saucer library to 9.0.8 as Timo suggested. I can now use the .pdf logo with vector graphics. The logo now looks beautiful on the Retina display.

Post by Samuel Pelletier
Hi Ricardo,
https://github.com/flyingsaucerproject/flyingsaucer/commit/26bf700857252ac04ecadd98dc0f8a2209e3c7f8 <https://github.com/flyingsaucerproject/flyingsaucer/commit/26bf700857252ac04ecadd98dc0f8a2209e3c7f8>
HTH,
Timo

_______________________________________________
Do not post admin requests to the list. They will be ignored.
https://lists.apple.com/mailman/options/webobjects-dev/rparada%40mac.com

Ricardo Parada

2015-11-30 19:24:59 UTC

Permalink

Hi Paul,

These are the links to the pages with the jar files. Just click the Download jar button on each of those pages and you will get the corresponding jar files.

http://mvnrepository.com/artifact/org.xhtmlrenderer/flying-saucer-core/9.0.8 <http://mvnrepository.com/artifact/org.xhtmlrenderer/flying-saucer-core/9.0.8>
http://mvnrepository.com/artifact/org.xhtmlrenderer/flying-saucer-pdf/9.0.8 <http://mvnrepository.com/artifact/org.xhtmlrenderer/flying-saucer-pdf/9.0.8>

Ricardo

I also ran "jar tf" on the jar files to compare with Wonder. In general the flying saucer 9.0.8 jars add more classes but there are a subset of classes still in the wonder jar (core-renderer-20101006.jar) that I was not able to find in the flying saucer jar files and I'm not sure if they are needed.
Ricardo

Richards
Where did you find the new jars? Did you build them yourself?
Paul
Sent from my iPad

Post by Ricardo Parada
Hi all,
I was trying to create a pull request to remove core-rederer-20101006.jar from ERPDFGeneration and add flying-saucer-core-9.0.8.jar and flying-saucer-pdf-9.0.8.jar.
However the fork I have of wonder on my github account is really old and Iâm confused how to go about doing this. Iâm not even sure what branch to put it on. My fork of wonder only has master, integration, and Wonder_5_0_0_Legacy. I was expecting to see master, wonder_5, wonder_6 and wonder_7.
Is there any documentation on how to go about submitting a pull request for wonder?
Thanks
Ricardo

_______________________________________________
Do not post admin requests to the list. They will be ignored.
https://lists.apple.com/mailman/options/webobjects-dev/rparada%40mac.com <https://lists.apple.com/mailman/options/webobjects-dev/rparada%40mac.com>

_______________________________________________
Do not post admin requests to the list. They will be ignored.
https://lists.apple.com/mailman/options/webobjects-dev/pyu%40mac.com <https://lists.apple.com/mailman/options/webobjects-dev/pyu%40mac.com>

Johann Werner

2015-11-30 21:30:53 UTC

Permalink

Hi Ricardo,

you should create a branch off from the official master branch and make your changes on that one. How to do that depends on the way you interact with git (e.g. git command line, Tower, SourceTree, âŠ).

Then you can create your pull request against the master branch. If the flying saucer jars are compatible with Java 5 it will be possible to cherry pick your changes into wonder_6 afterwards otherwise it will be Wonder 7 only. Do not use the wonder_7 branch as it points to an old state of master. I think that branch should go away soon to not confuse users. Master is the current Wonder 7.

For more info you can check the corresponding wiki page: https://github.com/wocommunity/wonder/wiki/Creating-and-submitting-an-acceptable-patch

jw

Post by Samuel Pelletier
Hi Ricardo,
https://github.com/flyingsaucerproject/flyingsaucer/commit/26bf700857252ac04ecadd98dc0f8a2209e3c7f8
HTH,
Timo

_______________________________________________
Do not post admin requests to the list. They will be ignored.
https://lists.apple.com/mailman/options/webobjects-dev/rparada%40mac.com

Ricardo Parada

2015-12-01 18:41:27 UTC

Permalink

Thank you Johann, that should get me going. The MANIFEST in the jar files says that they were built with java 1.7.0_79. I am going to try to find out if they are compatible with java 5, but based on the manifest it would be safer to keep this only in master as it may require > java 5.

Thanks

Post by Samuel Pelletier
Hi Ricardo,
you should create a branch off from the official master branch and make your changes on that one. How to do that depends on the way you interact with git (e.g. git command line, Tower, SourceTree, …).
Then you can create your pull request against the master branch. If the flying saucer jars are compatible with Java 5 it will be possible to cherry pick your changes into wonder_6 afterwards otherwise it will be Wonder 7 only. Do not use the wonder_7 branch as it points to an old state of master. I think that branch should go away soon to not confuse users. Master is the current Wonder 7.
For more info you can check the corresponding wiki page: https://github.com/wocommunity/wonder/wiki/Creating-and-submitting-an-acceptable-patch
jw

Post by Ricardo Parada
Hi all,
I was trying to create a pull request to remove core-rederer-20101006.jar from ERPDFGeneration and add flying-saucer-core-9.0.8.jar and flying-saucer-pdf-9.0.8.jar.
However the fork I have of wonder on my github account is really old and I’m confused how to go about doing this. I’m not even sure what branch to put it on. My fork of wonder only has master, integration, and Wonder_5_0_0_Legacy. I was expecting to see master, wonder_5, wonder_6 and wonder_7.
Is there any documentation on how to go about submitting a pull request for wonder?
Thanks
Ricardo

Post by Samuel Pelletier
Hi Ricardo,
https://github.com/flyingsaucerproject/flyingsaucer/commit/26bf700857252ac04ecadd98dc0f8a2209e3c7f8
HTH,
Timo

_______________________________________________
Do not post admin requests to the list. They will be ignored.
https://lists.apple.com/mailman/options/webobjects-dev/rparada%40mac.com

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-***@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/uoh8%40ml-in.narkive.net

This email sent to ***@m

Chuck Hill

2015-12-01 18:46:07 UTC

Permalink

If they were compiled with Java 1.7, they won’t run in a Java 5 JVM unless that was specifically targeted. And that seems unlikely given how old Java 1.5 is.

Chuck

Post by Ricardo Parada
Thank you Johann, that should get me going. The MANIFEST in the jar files says that they were built with java 1.7.0_79. I am going to try to find out if they are compatible with java 5, but based on the manifest it would be safer to keep this only in master as it may require > java 5.
Thanks

Post by Ricardo Parada
Hi all,
I was trying to create a pull request to remove core-rederer-20101006.jar from ERPDFGeneration and add flying-saucer-core-9.0.8.jar and flying-saucer-pdf-9.0.8.jar.
However the fork I have of wonder on my github account is really old and I’m confused how to go about doing this. I’m not even sure what branch to put it on. My fork of wonder only has master, integration, and Wonder_5_0_0_Legacy. I was expecting to see master, wonder_5, wonder_6 and wonder_7.
Is there any documentation on how to go about submitting a pull request for wonder?
Thanks
Ricardo

Post by Samuel Pelletier
Hi Ricardo,
https://github.com/flyingsaucerproject/flyingsaucer/commit/26bf700857252ac04ecadd98dc0f8a2209e3c7f8
HTH,
Timo

_______________________________________________
Do not post admin requests to the list. They will be ignored.
https://lists.apple.com/mailman/options/webobjects-dev/rparada%40mac.com

_______________________________________________
Do not post admin requests to the list. They will be ignored.
https://lists.apple.com/mailman/options/webobjects-dev/chill%40gevityinc.com

Timo Hoepfner

2015-12-02 08:30:58 UTC

Permalink

Hi Ricardo,

the 0.9.8 version needs Java 6, for Java 5 you can use 0.9.7. That version also contains the fix that enables using PDFs. I had to revert to that version on an old XServe that only supports Java 5.

Hereâs a handy script that checks the Java class version of files in a jar:
https://github.com/beardedN5rd/java-helper/blob/master/scripts/checkJavaVersion.sh <https://github.com/beardedN5rd/java-helper/blob/master/scripts/checkJavaVersion.sh>

mbp:Downloads th$ checkJavaVersion.sh flying-saucer-core-9.0.8.jar
flying-saucer-core-9.0.8.jar
Found 0 Java 1.1 files
Found 0 Java 1.2 files
Found 0 Java 1.3 files
Found 0 Java 1.4 files
Found 0 Java 5 files
Found 581 Java 6 files
Found 0 Java 7 files
Found 0 Java 8 files

mbp:Downloads th$ checkJavaVersion.sh flying-saucer-core-9.0.7.jar
flying-saucer-core-9.0.7.jar
Found 0 Java 1.1 files
Found 0 Java 1.2 files
Found 0 Java 1.3 files
Found 573 Java 1.4 files
Found 0 Java 5 files
Found 0 Java 6 files
Found 0 Java 7 files
Found 0 Java 8 files

Timo

Post by Samuel Pelletier
Hi Ricardo,
you should create a branch off from the official master branch and make your changes on that one. How to do that depends on the way you interact with git (e.g. git command line, Tower, SourceTree, âŠ).
Then you can create your pull request against the master branch. If the flying saucer jars are compatible with Java 5 it will be possible to cherry pick your changes into wonder_6 afterwards otherwise it will be Wonder 7 only. Do not use the wonder_7 branch as it points to an old state of master. I think that branch should go away soon to not confuse users. Master is the current Wonder 7.
For more info you can check the corresponding wiki page: https://github.com/wocommunity/wonder/wiki/Creating-and-submitting-an-acceptable-patch
jw

Post by Samuel Pelletier
Hi Ricardo,
https://github.com/flyingsaucerproject/flyingsaucer/commit/26bf700857252ac04ecadd98dc0f8a2209e3c7f8
HTH,
Timo

Ricardo Parada

2015-12-02 13:58:38 UTC

Permalink

Thank you Timo, that is very helpful.

Sent from my iPhone

Post by Samuel Pelletier
Hi Ricardo,
the 0.9.8 version needs Java 6, for Java 5 you can use 0.9.7. That version also contains the fix that enables using PDFs. I had to revert to that version on an old XServe that only supports Java 5.
https://github.com/beardedN5rd/java-helper/blob/master/scripts/checkJavaVersion.sh
mbp:Downloads th$ checkJavaVersion.sh flying-saucer-core-9.0.8.jar
flying-saucer-core-9.0.8.jar
Found 0 Java 1.1 files
Found 0 Java 1.2 files
Found 0 Java 1.3 files
Found 0 Java 1.4 files
Found 0 Java 5 files
Found 581 Java 6 files
Found 0 Java 7 files
Found 0 Java 8 files
mbp:Downloads th$ checkJavaVersion.sh flying-saucer-core-9.0.7.jar
flying-saucer-core-9.0.7.jar
Found 0 Java 1.1 files
Found 0 Java 1.2 files
Found 0 Java 1.3 files
Found 573 Java 1.4 files
Found 0 Java 5 files
Found 0 Java 6 files
Found 0 Java 7 files
Found 0 Java 8 files
Timo

Post by Samuel Pelletier
Hi Ricardo,
you should create a branch off from the official master branch and make your changes on that one. How to do that depends on the way you interact with git (e.g. git command line, Tower, SourceTree, âŠ).
Then you can create your pull request against the master branch. If the flying saucer jars are compatible with Java 5 it will be possible to cherry pick your changes into wonder_6 afterwards otherwise it will be Wonder 7 only. Do not use the wonder_7 branch as it points to an old state of master. I think that branch should go away soon to not confuse users. Master is the current Wonder 7.
For more info you can check the corresponding wiki page: https://github.com/wocommunity/wonder/wiki/Creating-and-submitting-an-acceptable-patch
jw

Post by Samuel Pelletier
Hi Ricardo,
https://github.com/flyingsaucerproject/flyingsaucer/commit/26bf700857252ac04ecadd98dc0f8a2209e3c7f8
HTH,
Timo

Ricardo Parada

2015-12-08 22:39:30 UTC

Permalink

I created pull request #710 for this.

Post by Ricardo Parada
Thank you Timo, that is very helpful.
Sent from my iPhone

Post by Samuel Pelletier
Hi Ricardo,
the 0.9.8 version needs Java 6, for Java 5 you can use 0.9.7. That version also contains the fix that enables using PDFs. I had to revert to that version on an old XServe that only supports Java 5.
https://github.com/beardedN5rd/java-helper/blob/master/scripts/checkJavaVersion.sh <https://github.com/beardedN5rd/java-helper/blob/master/scripts/checkJavaVersion.sh>
mbp:Downloads th$ checkJavaVersion.sh flying-saucer-core-9.0.8.jar
flying-saucer-core-9.0.8.jar
Found 0 Java 1.1 files
Found 0 Java 1.2 files
Found 0 Java 1.3 files
Found 0 Java 1.4 files
Found 0 Java 5 files
Found 581 Java 6 files
Found 0 Java 7 files
Found 0 Java 8 files
mbp:Downloads th$ checkJavaVersion.sh flying-saucer-core-9.0.7.jar
flying-saucer-core-9.0.7.jar
Found 0 Java 1.1 files
Found 0 Java 1.2 files
Found 0 Java 1.3 files
Found 573 Java 1.4 files
Found 0 Java 5 files
Found 0 Java 6 files
Found 0 Java 7 files
Found 0 Java 8 files
Timo

Post by Samuel Pelletier
Hi Ricardo,
you should create a branch off from the official master branch and make your changes on that one. How to do that depends on the way you interact with git (e.g. git command line, Tower, SourceTree, âŠ).
Then you can create your pull request against the master branch. If the flying saucer jars are compatible with Java 5 it will be possible to cherry pick your changes into wonder_6 afterwards otherwise it will be Wonder 7 only. Do not use the wonder_7 branch as it points to an old state of master. I think that branch should go away soon to not confuse users. Master is the current Wonder 7.
For more info you can check the corresponding wiki page: https://github.com/wocommunity/wonder/wiki/Creating-and-submitting-an-acceptable-patch <https://github.com/wocommunity/wonder/wiki/Creating-and-submitting-an-acceptable-patch>
jw

_______________________________________________
Do not post admin requests to the list. They will be ignored.
https://lists.apple.com/mailman/options/webobjects-dev/rparada%40mac.com