JBossDeveloper

and about A4J integration?

ok thanks,


security exemple (freshly updated from CVS) don't work for me for two reasons:

- first one:

I think seam.properties should be renamed into component.properties and the corresponding line inserted into build.xml (at line 42 for me) ... then it starts for me...

but when started..

- second one: it doesn't work (I have no more information yet):

I log in using demo demo then I have the menu but when I press ProtectedAction I'm redirected to the login page...

I'm using 4.0.4 patched with EJB3 RC9...

I'll try 4.0.5

Security Example:

It seems that Authenticator.instance().authenticate(user.getUsername(), user.getPassword()) in LoginAction always return true. It seems jboss-service.xml login-config.xml are not used any more. The sutentication configuration guide still apply to 1.1?

I've fixed the security example, there was a redundant entry left in components.xml. Both jboss-service.xml and login-config.xml have been removed, I'll update the wiki page to reflect this.

HUGE kudo's for the facelet support of parameters in action expressions!

Being able to do: "#{contact.addContact(c)}" has really simplified some the things I'm trying to do.


One thing, I don't know if this is a bug or I'm misunderstanding something but:

a4j namespace is the Ajax4Jsf function set.

the command:

<a4j:commandLink action="#{contactManager.deleteContact(c)}"/>

<h:dataTable var="c" value="#{contacts}">
 <h:column>
 ## above action here
</h:column>
</h:dataTable>

<c:forEach var="c" items="#{contacts}">
 ## command goes here
</c>

"gavin.king@jboss.com" wrote:
Right, the big caveat with this stuff is that the parameter value is evaluated when the form is *submitted*, not when the form is *rendered*. "c" must be a valid context variable available during the form submission.

<a4j:commandLink action="#{contactManager.deleteContact(c.ID)}"/>

<c:forEarch>

"gavin.king@jboss.com" wrote:
not going to make a difference.

Why aren't you using ui:repeat??

Gavin,

Without intending to be picky, I just noticed the Seam 1.1 Beta reference shows it's version as 1.0.1.GA; both for the HTML and PDF versions.

This might lead readers to think that it is unchanged from the 1.0.1 release, which almost happened to me.

Ian
(Sydney)

"bpatters" wrote:
HUGE kudo's for the facelet support of parameters in action expressions!

Being able to do: "#{contact.addContact(c)}" has really simplified some the things I'm trying to do.


One thing, I don't know if this is a bug or I'm misunderstanding something but:

a4j namespace is the Ajax4Jsf function set.

the command:

<a4j:commandLink action="#{contactManager.deleteContact(c)}"/>

Works inside a datatable like:

<h:dataTable var="c" value="#{contacts}">
 <h:column>
 ## above action here
</h:column>
</h:dataTable>

But when it's inside:

<c:forEach var="c" items="#{contacts}">
 ## command goes here
</c>

it doesn't work, the pareamter sent to the function always resolves to null.


The above is just a contrived example of what I saw last night with my real application, if you need the real code example that doesn't work I will have to do that tonight/this weekend.