From my understanding declarative navigation is when you declare in the config files where you will go if you click a particular button. For instance, on your actual jsf page you might have a button that looks like this:
Then in your config.xml files you'll have something like this:
So in your button you're not actually hard-coding the location of a file, but rather a string. Your config files know that whenever that particular string gets returned, it should send you to whatever place you have set up in your xml files.
That's my understanding anyway, somebody please let me know if I'm wrong.
"Declarative" anything in programming terms means that instead of Java code (or whatever language), you're defining something in a simpler, less flexible way. Declarative notation normally has no conditional constructs[*] and the overall syntax is simpler, making it easier to validate the declarations than it would be to debug Java code.
I put the asterisk [*] next to "no conditional constructs" because you can make a navigational rule conditional (contingent on an EL expression result), but what I mean is that the individual navigational rules themselves support nothing like an if/then/else or do/while structure.
Customer surveys are for companies who didn't pay proper attention to begin with.
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com