1) Well, I see that in index.html in registration exemple:
<head> <meta http-equiv="Refresh" content="0; URL=register.seam"> </head>
Co it seems quite clear to me, or I didn't understand your question.
2) You can do that simply with a rewrite rule.
Here's some doc about it:
Simply put a rule like
<!-- seam extension removal / --> <outbound-rule> <name>.seam removal out</name> <from>/([/a-zA-Z0-9]*)\.seam</from> <to>/$1</to> </outbound-rule>
About the URL (.seam) this is nothing specific, have a look in your web.xml and the Faces servlet and its servlet-mapping. You can easily change this to *.html.
About the mapping to .xhtml, this is configured via a context-param in your web.xml.
Have a look at the Facelets documentation for more information regarding this, http://facelets.dev.java.net check the developer documentation.
About the encryption, I've got no idea. How about using https (not sure how to configure this tough)?
>> 1) Well, I see that in index.html in registration exemple:
>> <meta http-equiv="Refresh" content="0; URL=register.seam">
>>Co it seems quite clear to me, or I didn't understand your question.
Yes, but how does it decide to go from a request like /register.seam to displaying the file register.xhtml. There is nothing in the RegisterAction EJB that tells it to do that. The EJB either adds a new user or displays that a user already exists.
There is some default processing going on here which I don't understand. I have looked at the config files under WEB-INF, again nowhere can I see how it decides to do that. The only thing I can imaging is that somehow if no parameters are passed to register.seam it is the default behaviour that a page of the same name but with a .xhtml extenion is displayed. But I haven't seen this mentioned anywhere in the documentation.
You're actually right about changing the extension, dunno why but I thought he wanted to remove it completely, not to change it.