Asynchronous seam mail can not get the base URL dynamically

[milli]

Hi,

While creating a user account, I'm trying to invoke an asynchronous method in my SLSB to send the activation mail. In my activation mail template, I'm trying to resolve the activation URL dynamically instead of having a static one.

I tried the following methods and none of them gets the correct URL:

<s:link> - resolves to /project/activation.seam - I don't know where the project is coming from 'cause that is not my application context path

#{facesContext.externalContext.requestContextPath} - resolves to null

defined a factory variable and try to use #{basePath} - resolves to null

<factory name="basePath" scope="APPLICATION" value="#{facesContext.externalContext.request.scheme}://#{facesContext.externalContext.request.serverName}:#{facesContext.externalContext.request.serverPort}#{facesContext.externalContext.request.contextPath}/"/>

finally tried to inject facesContext in the SLSB that renders the mail template, and it fails to inject.

Finally concluded that it is 'cause of asynchronous method. I think it looses all the contexts when it is run. If I make it synchronous, everything works fine.

Has anyone come across this problem? Is there a way to set contexts for asynchronous methods?

Thanks

[pmuir]

Look at the urlBase attribute on m:message

file:///media/disk2/pmuir/workspace/jboss-seam-2.0.0.BETA1/doc/reference/en/html/mail.html#mail.tags

I just made a fix that should actually make this work in async methods :)

[milli]

Look at the urlBase attribute on m:message

file:///media/disk2/pmuir/workspace/jboss-seam-2.0.0.BETA1/doc/reference/en/html/mail.html#mail.tags

I just made a fix that should actually make this work in async methods :)

Thanks for your quick response. I'm using 1.2.1GA so probably I will have to wait for the next release then.

I'm trying a workaround of passing the baseURL as a parameter to the asynchronous method and if that works I'm good for now.

Thanks again.

[gavin.king]

Yep, an async method does not have access to any web context.

[milli]

Yep, an async method does not have access to any web context.

That explains it. Thanks. would it be supported in 2.0? I think the urlBase that Pete mentioned is kind of workaround and not really getting any web context in asyn methods. Please correct me if I am wrong.