Meeting 17: Unterschied zwischen den Versionen

Aus Java Student User Group Austria - Java + JVM in Wien Österreich / Vienna Austria
Wechseln zu: Navigation, Suche
(zajmQxBttAVOCCO)
(urOGCqapQIeaP)
Zeile 1: Zeile 1:
−
Basically, XML is to store data but not to store business logic. Data is coelmptely irrelevant to the business logic. Say, the java code may disappear one day, but the data handled by the code will still be there. So, it doesn't make much sense to combine xml and java code to implement business logic.To be an extremist, I don't store the business logic in the database to define the way java objects work.It's true that xml files in spring is supposed to be configurations. However, xml files are actually more than configurations because they defines run-time interactions of java objects. (IMHO, a configuration file defines the initial settings for a program.)I might be wrong, but please save those F words because they don't help debate
+
The jspc-maven-plugin from codehaus mojo uses only tcmaot 5.5.15, whereas this one will use either 5.5.15 or glassfish.Also, the jspc-maven-plugin uses the java compiler that maven uses, whereas this plugin uses the same compiler that you use in dev mode for on-the-fly compilation, which is the Eclipse java compiler.Some other differences are:  + you don't have to specify a marker in the web.xml for where to insert the generated servlet-mappings. For servlet2.4 and above, the order of elements in web.xml is not significant, so the plugin can just automatically append it to the end of the existing web.xml.+ you can generate the smap stuff for jsr45 compliant debugging+ supports some other glassfish-only compilation options+ this plugin is bound to the process-classes phase whereas the other one is bound to the compile phase. As maven 2.0.4 and below doesn't guarantee the order of execution of plugins, binding to the compile phase doesn't guarantee that the java classes in the webapp will have already been compiled by the time the jspc-maven-plugin runs. This way guarantees that the jsp compilation slots in nicely between the compile and package phases.

Version vom 16. Dezember 2012, 06:52 Uhr

The jspc-maven-plugin from codehaus mojo uses only tcmaot 5.5.15, whereas this one will use either 5.5.15 or glassfish.Also, the jspc-maven-plugin uses the java compiler that maven uses, whereas this plugin uses the same compiler that you use in dev mode for on-the-fly compilation, which is the Eclipse java compiler.Some other differences are: + you don't have to specify a marker in the web.xml for where to insert the generated servlet-mappings. For servlet2.4 and above, the order of elements in web.xml is not significant, so the plugin can just automatically append it to the end of the existing web.xml.+ you can generate the smap stuff for jsr45 compliant debugging+ supports some other glassfish-only compilation options+ this plugin is bound to the process-classes phase whereas the other one is bound to the compile phase. As maven 2.0.4 and below doesn't guarantee the order of execution of plugins, binding to the compile phase doesn't guarantee that the java classes in the webapp will have already been compiled by the time the jspc-maven-plugin runs. This way guarantees that the jsp compilation slots in nicely between the compile and package phases.

Abgerufen von „https://jsug.at/w/index.php?title=Meeting_17&oldid=3274“