JBossDeveloper

We were finding some use out of this in a custom navigationhandler when it was public in 1.0.1:

Manager.encodeConversationId

Any reason that can't be public? I guess to use 1.1 for now, I'll just rip the code out of there and inline it in our app.

I should have provided more info. We've built our own lightweight restful URL framework on top of Seam + JSF.

getActionURL (used by Manager.redirect) can't be relied upon to return the actual restful URL we want to redirect the user to.

Maybe I can change our URL going into Manager.redirect to be prefixed by "custom:". Then, our own getActionURL() impl can look for this prefix, and pop it off, and then return what comes after it (which can be a URL fully qualified by https/http/etc).

That might work.

that ajax integration :) great :)

I can't find the new reference documentation for Seam 1.1 in my downloaded bundle. Thank you in advance.

/jboss-seam-1.1.0.BETA1/doc/reference/en/

Gavin probably forgot to change the version number in the document, but if you read it you will see it is changed :)

Thank you.

I have a problem using Seam 1.1 with JBoss 4.0.5. My action-method in my Login-Bean throws an ApplicationException. I have NOT annotated this applicationException with a seam-annotation. Nevertheless, Seam always catches this exception with its ExceptionInterceptor (or especially the ClientSideInterceptor). Due to this, the exception is now eaten by seam and is not forewarded to my own catch-clause. When I switch off the debug mode, my ApplicationException will not been thrown.

How can I stop seam catching ApplicationExceptions which are not anotated with a seam-annotation ?

Sorry, but we are not in Debug-Mode of Seam and our application exception is still eaten by seam-interceptor.

In our calling method we run some hibernate-statements, which run into an NoSuchResultException, which we catches an re-throw as an ApplicationException(rollback=true).
This ApplicationException is now eaten by seam, although the applicationException is not seam-annotated.


See following output:

17:25:04,575 INFO [STDOUT] Hibernate: select userentity0_.ID as ID2_ from USER userentity0_ where lower(userentity0_.USER_NAME)=lower(?)
17:25:04,778 INFO [ExceptionInterceptor] no exceptions.xml file found

Any Idea ?

I have just tryed it!!!

I have one bug report yet:

it seems the ActionParamMethodBinding returned by SeamApplication11.createMethodBinding doesn't take care of methods parameters:

I use sandbox autocomplete component and the backbean method signature is List getSuggestion(String)... when I launch it I got a NotSuchMethodException getSuggestion() ...

The parameter "Class[] params" in SeamApplication11.createMethodBinding is lost...do you want me to post the bug on an other channel?

I also have a question about A4J integration: what is it about : I used A4J with seam successfully with seam 1.0.. what does this integration provide? is it just about the bookinjg exemple or A4J is integrated into seam core??

THANKS!!!

Personaly I changed directly seam sources into:


SeamApplication11{...

public MethodBinding createMethodBinding(String ref, Class[] params)
throws ReferenceSyntaxException
{
//return new ActionParamMethodBinding(application, ref);
return getDelegate().createMethodBinding(ref, params);
}

}

and it works!!