- This topic has 5 replies, 2 voices, and was last updated 21 years, 4 months ago by
.
-
Posts
-
I either renamed or created from scratch a couple of .jspf files. I expected that they would cause re-deploy. That did not happen. Also, when I create .jsp and .jspf files I would like their team characteristic to be ASCII and they are coming out binary. This occurs even though I have set Window->preferences->Team->File Content to ASCII for .jsp .jspf .JSP and .JSPF. Help.
Wayne
Wayne,
I either renamed or created from scratch a couple of .jspf files. I expected that they would cause re-deploy.
For all servers to which the project is deployed in exploded format, the new/renamed jsp and jspf files should be copied to the appropriate deployment directory. Would you please check the setting of Window > Preferences > Workbench > Perform build automatically on resource modification. It has been know to “turn itself off”. Since the deployer hooks into the builder framework, this setting must be checked to enable automatic deployment sync.
I would like their team characteristic to be ASCII and they are coming out binary. This occurs even though I have set Window->preferences->Team->File Content to ASCII for .jsp .jspf .JSP and .JSPF.
It sounds like you’ve done what is necessary to configure this properly. However, this won’t change the settings on existing jsp and jspf files. For that you must convert them using the tools on the Team menu. New files should respect the setting, but I’m not sure if this is project specific or not. What I mean is, if you have a project that already has existing ‘binary’ jsp files, I’m not sure if Eclipse will respect the new ASCII setting for the project. It seems it should. You will still have to manually convert any existing ones though. If the setting still isn’t respected after that, as a test you can create a new web project using the wizard, generate a test jsp using the wizard, and add it to CVS and see if it gets added as ASCII or binary. I’ll also point out that this particular capability isn’t anything that MyEclipse modifies in any way; it’s just base Eclipse CVS functionality. Naturally, we’ll still try to help however we can.
–Scott
MyEclipse SupportThe team thing is my fault. I am ok now. The jspf files seem to be transferred to Autodeploy ok, but I guess I expected them to be re-compiled. I also did not expect that the jsp wizard would refuse to create jspf pages.
Wayne
Wayne,
The team thing is my fault. I am ok now.
Good deal.
The jspf files seem to be transferred to Autodeploy ok, but I guess I expected them to be re-compiled.
Our deployer moves the files and keeps them insync, but the behavior to recompile and reload them on modification is server-specific and usually server configurable. For example, most servers in “debug” mode will automatically recompile and reload JSP pages on modification, but in “production” mode they don’t. You’ll have to check the doc for the server you’re using as to how to enable the reloading behavior you expect.
I also did not expect that the jsp wizard would refuse to create jspf pages.
That’s because it’s a JSP wizard, not a JSP fragment wizard. 😉 Seriously though, I’ve entered a defect report for disallowing .jspf and this will be addressed in the next service release.
–Scott
MyEclipse SupportWhat I meant by recompiled is the compile that I observe on the eclipse side. This is the only way that the preview can see the page with its translated markup. I am building page parts independently (they can also be tested independently) Then, later I can combine the parts (using the tiles package). Some members of the team are working on headers and some are working on bodies and some are working on footers. There is little excitement in footer work, but gratification is quick.
Wayne
Wayne,
Oh, I see what you’re after. The problem with compiling fragments independently is that since they’re a fragment they’re typically not a valid top-level JSP page, which means they’d have a ton of compilation errors. So, the JSP compiler doesn’t try to compile them independently, but rather simply “inlines” them with their top-level JSP when it is compiled. This is basically just what the webservers do.
If you want to force a compilation to ensure that it’s correct for development, how about creating a “driver” top-level JSP page that just includes the .jspf.
For a quick look, just the plain preview pane in the JSP editor is available whether or not the file is a .jsp or a .jspf.
–Scott
MyEclipse Support
