What I'd like to get from seam-gen is the run jboss in eclipse scenario
described by the OP. When I create a project with seam-gen I can use ant to
deploy an .ear or deploy exploded, but that's all done outside of eclipse so I
don't get the breakpoints and there are no instant updates without
Check this out: http://tuckey.org/urlrewrite/
URL rewriting through a filter. This doesn't solve the problem by itself, but
it brings the filtering closer to seam.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4000852#4000852
Reply to the post :
I just took a look at Seam in the CVS and after going through the seamspace
example I can't say anything else than:
I love you guys! :-)
I've been putting off this project for a long time in lack of a good security
implementation and now you've solved a lot of my problems.
I know you've
Did anyone find a solution for this?
Doing this...
| EJB3StandaloneBootstrap.boot(null);
| EJB3StandaloneBootstrap.scanClasspath();
|
...gets me this far
DEBUG 08-10 17:36:02,421 (KernelFactory.java:assembleNewKernel:86) -Starting
JBoss Kernel construction...
| DEBUG 08-10
It doesn't work, but something like this would be nicer:
| navigation-rule
| navigation-case
| from-outcomeregister/from-outcome
| to-view-id/register_#{locale}.xhtml/to-view-id
| redirect /
|
Oh, whith object and connections etc. I was thinking of a database.
Your solution works well with content that is really static. But I'd prefer
some sort of wiki/CMS functionality so that users can edit the content without
access to the .xhtml files (which they shouldn't even have to know or
To quote myself from an other thread
anonymous wrote : Url Rewrite Filter, mod_rewrite for the Java world:
|
| http://tuckey.org/urlrewrite/
I really think you should have a good look at it.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3967619#3967619
I was thinking that it should be possible to use AJAX to validate forms on the
server side using the hibernate validation annotations that are already there
in the entities. So that it looks just like client side validation (happens
while the user is working with the form) but you don't have to
