Sorry if this isn't the right forum for this question, but I'm hoping Seam
provides a way to do this.
I've seen the form entry pointed to by this link:
http://www.jboss.org/?module=bbop=viewtopict=102272
and have tried the proposed solution a couple ways, but still cannot see how to
get the
Sorry, everyone - I found what looks to be a better forum post that may give me
what I want. In case you're having the same problem...
http://www.jboss.com/index.html?module=bbop=viewtopicp=3998636#3998636
- Joe
View the original post :
This may be more of a JSF question that a Seam one, and if so, I apologize. In
my past web apps, I've been able to get the http session id by asking the
HttpServletRequest for it, but that was in a servlet environment that I
managed. Does the Seam API allow me to easily get the http session
I found a solution on this forum that seems to work. Here's the code and
original forum link:
| FacesContext facesContext = FacesContext.getCurrentInstance();
| ExternalContext externalContext = facesContext.getExternalContext();
| HttpSession session =
Hi -
I've got an enum that I want to create a drop-down for, and use the ordinal
values for the value attribute in the option... tags.
But the selectItems component only has label attribute, and so I can't figure
out how to tell the selectItems to use the enum's ordinal values for the option
Thanks Shane -
I'll have to try the latest of course, but when you say there's no guarantee
how many times the authenticate method will be called, yet both issues have
been resolved, what does that mean for those of us who write their own login
method and configure it in components.xml using
Fantastic! I look forward to seeing the docs. Any idea when they'll be
updated?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4102257#4102257
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4102257
Pete -
After seeing the JIRA ticket on this, and rereading the prior posts, it
occurred to me that there may have been a little confusion about the login
method that I was referring to. I was referring to my own login method that
is configured in components.xml to serve as the authenticator
Troy -
Thanks for the info - looks like several of us are having this problem. Here's
a link to the JIRA ticket I mentioned:
http://jira.jboss.org/jira/browse/JBSEAM-2165
also, see Shane's previous post. Looks like another, more recent, ticket has
just been created.
Shane -
Does the
Thanks, Shane. That makes sense. Is it documented anywhere else, and is it
configurable? I'd like to consider using the Identity feature, but we need to
track failed logins and can't allow multiple login() executions with only one
user action.
View the original post :
Pete -
My login method was executing more than once because I put the following line
in my components.xml file:
security:identity authenticate-method=#{loginManager.login} /
Of course, at the time, I wasn't aware that the authenticate method executed
more than once.
I certainly trust you
My app uses Seam, JSF, oc4j, and JSPs. I'm using the Identity feature in Seam
to define my login authentication method. The funny problem I'm having is that
when authentication fails (due to invalid password, for example), the login
method actually executes twice. If I remove the line in
Shane -
Thanks for the reply. Sorry I didn't find anything on the forums - guess I
didn't use the right search string.
Please understand that I'm in my first Seam project, so don't know all the
nuances, so I have to ask - why is there no guarantee how many times the
authenticate method will
Hi -
I've read about Seam's support for an extended persistence context, and have
read about Seam conversations. I've got a Lazy Initialization problem that
doesn't seem to quite fit the solutions I've read about - maybe I just can't
quite see it.
I've got an entity object with a lazy loaded
Hello -
I'm having to convert a few facelets to jsps (don't ask), and we want to use
jsp instead of jspx. But when I change the xmlns definition at the top of the
page to %@ taglib uri=http://jboss.com/products/seam/taglib; prefix=s %,
eclipse says it can't find the tag library descriptor for
Sorry, silly mistake. I didn't realize jboss-seam-ui.jar was not in the
project.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4084255#4084255
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4084255
We're getting started on our first JSF application using Seam, so this may be a
pretty basic question. The web.xml file for my project right now uses
org.jboss.seam.jsf.SeamPhaseListener as the sole phase listener. However, I
need to integrate an ESRI map service into the app, and the sample
Thanks, Gavin. I've read, though, that using multiple phase listeners can
cause problems like data becoming corrupted (whatever that means) and slower
response since both phase listeners are executed. Are these things really an
issue? Also, if I do include both phase listeners in my xml file
Hello -
Maybe I've missed something, but is there a definitive solution yet to the
error mentioned in this thread subject? I've seen this posted before, but
still no solution. I've been running a simple Seam app at work using Tomcat,
and it has been running fine. I added a couple of database
Hello -
Is anyone aware if there is a well-defined solution to this problem yet? There
are a few threads on this forum, but it seems like no one knows for sure why
this happens. I've got a sample app that was working at work. I brought it
home, added a few database tables and a couple of
I've seen several examples for persisting entity objects, and even removing
them from databases, but I can't seem to find a good example of how to use the
EntityManager to update a database record for an entity. For example, if I
have an Account entity object called acct, and I've made a few
21 matches
Mail list logo
