[pathogen]

Well, today at work I tried to reproduce the problem experienced on the Mac. Sure enough, when I took the slash out of <jsp:include page=”page2.jspf” /> and saved, the IDE locked up with the building workspace message… Nothing in log file.

[Scott Anderson]

We’ll investigate that specific case. In the mean time, “don’t do that”. 😉

[pathogen]

In the mean time, “don’t do that”. 😉

Heheh 😉

[pathogen]

So, have you guys been able to replicate it at all?

[pathogen]

Still hanging tight… 😉

[pathogen]

Any news yet? Thx

[Scott Anderson]

Well, I tried to reproduce the issue on a Mac Powerbook with 10.3.6 installed by adding the include directive before creating the jspf file, after creating it with the wrong URI, and with a valid URI. I saved each time and the workspace rebuilt without an issue. So basically, I could not reproduce the problem. However, since the workaround on your system is quite simple I’d suggest using it in the short term and then seeing if a new installation of 3.8.3 (in December) resolves the problem for you.

[pathogen]

Did you remove the slash in the include tag and then save? That’s when it barfed.

[Scott Anderson]

Ah, you mean the slash on the close portion of the tag, that is:

<jsp:include page="page2.jspf" >

NOT the correct version of:

<jsp:include page="page2.jspf" />

Yes, that does cause a compilation lockup, but it’s not unique to the Mac. I’ve entered a bug report for it. Thanks for hanging in there and helping us track it down. 🙂

[pathogen]

Ah, you mean the slash on the close portion of the tag

Yeah, I didn’t close the tag by mistake and that’s how I discovered this. Originally I thought it either had something to do with 10.3.6 or other issues. But if you look at my last postings, I got it to be reproduceable every time simply by omitting the slash and saving.

Yes, that does cause a compilation lockup, but it’s not unique to the Mac. I’ve entered a bug report for it.

Yeah, I can reproduce it on the windows box here at work as well. Must be an issue with tag parser. Sorry for reinventing the wheel since you had already entered a bug report for it… Do you think this issue will be fixed in the December release? *thumbs crossed*

[pathogen]

Also, is there a publicly accessible DB of known bugs?

[Scott Anderson]

Do you think this issue will be fixed in the December release? *thumbs crossed*

It’s currently targeted for 3.8.3. However, if we get short on resources we typically will drop fixes that have simple workarounds. With any luck it will get in though.

[pathogen]

fixes that have simple workarounds

Just so I get this straight, the workaround is basically don’t make a mistake and forget the slash? Is that correct? I just want to make sure.

[pathogen]

In addtion to the above quesiton, is there a list of known bugs I can reference? Thx.

[pathogen]

Can someone please answer these two questions? Thanks!

[Author]

Posts