1.2.1 doesn't compile against Java 1.5_03

[Mitch Christensen]

I have opened a bug report (#1222734), but I'm concerned that there may not be any future releases.

Is this a dead project?  I just don't see much action here anymore.

-Mitch

[Sherman Wood]

From the mailing list:

I had to do the following modifications to have Babeldoc compiled with Java=
1.5:

1) changed Enum to myEnum in=20
gui/src/com/babeldoc/gui/journal/browser/JournalTree.java:240:
Enumeration myEnum =3D node.children();

gui/src/com/babeldoc/gui/journal/browser/JournalTree.java:241:
while (myEnum.hasMoreElements()) {

gui/src/com/babeldoc/gui/journal/browser/JournalTree.java:242:
DefaultMutableTreeNode elem =3D (DefaultMutableTreeNode)myEnum.nextElement(=
);

soap/src/com/babeldoc/soap/pipeline/servlet/SoapPipelineFeeder.java:203:
Enumeration myEnum =3D req.getHeaderNames();

soap/src/com/babeldoc/soap/pipeline/servlet/SoapPipelineFeeder.java:206:
while (myEnum.hasMoreElements()) {

soap/src/com/babeldoc/soap/pipeline/servlet/SoapPipelineFeeder.java:207:
String headerName =3D (String) myEnum.nextElement();

soap/src/com/babeldoc/soap/pipeline/servlet/SoapPipelineFeeder.java:280:
for (Enumeration myEnum =3D request.getHeaderNames(); myEnum.hasMoreElement=
s();) {

soap/src/com/babeldoc/soap/pipeline/servlet/SoapPipelineFeeder.java:281:
String header =3D (String) myEnum.nextElement();

web/src/com/babeldoc/web/pipeline/servlet/HttpPostPipelineFeeder.java:222:
for (Enumeration myEnum =3D request.getHeaderNames(); myEnum.hasMoreElement=
s();) {

web/src/com/babeldoc/web/pipeline/servlet/HttpPostPipelineFeeder.java:223:
String header =3D (String) myEnum.nextElement();

2) removed ambiguity by specifying javax.jms.Queue instead of Queue

j2ee/src/com/babeldoc/j2ee/scanner/worker/JmsScanner.java:95:
private javax.jms.Queue queue;

j2ee/src/com/babeldoc/j2ee/scanner/worker/JmsScanner.java:141:
queue =3D (javax.jms.Queue) context.lookup(Queue);

Sherman

[Sherman Wood]

I think that folks are just using Babeldoc as is. There was some idea that there would be refactoring to use Spring, but there has been no activity.

Sherman