Is your User Class annotated so that its a Seam Component ? i.e. does it have
the @Name(user) in it?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3987141#3987141
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3987141
jazir1979 wrote :
| ie- the pattern really should be all pages except login.xhtml rather than
*
I dont think there is a way to do this currently except mentioning the pages
individually. But there is an enhancement request for this
http://jira.jboss.com/jira/browse/JBSEAM-341
View the
Looks like the bean has been passivated but the persisted file is removed.
Can you check if your JBOSS_HOME/server/default/tmp/sessions/ exists and is not
getting deleted by any of your code ? This is a remote chance but just in case.
Also turn up your log level to DEBUG and you should see more
Well, its just behaving as a WebServer. Can you locate your xhtml files within
the WEB-INF so they cant be rendered directly and have your navigation rules
point to the locations within WEB-INF?
Also look at the dvdstore example for some snippets that are loaded from the
WEB-INF directory.
Can you use the jems installer as indicated in
http://labs.jboss.com/portal/jbossseam/gettingstarted for getting jboss-4.0.4.
I believe you dont have the latest EJB3 jars as the method call from
InvocationContext.getTarget() was introduced only later( in EJB3-RC8)
8 wrote :
| However, when I do this, I don't seem to be getting the DataModel, but
rather the actual List itself. This is evidenced by the fact that a method in
the class that uses the DataModelSelection is always stuck at pointing to the
first item in the List list...
|
Can you
I think browsers behave differently for this. if there is only one form field
on a page, then hitting enter will do the same as a submit but Ive seen posts
where IE takes any enter on text field as a submit.
You could use the onkeypress attribute on JSF's inputtext to have a javascript
that
1. Web Services maybe a good way to do this, you dont have to use Seam for
that, but just generally have an endpoint that can receive your WS calls and
act on it. Why do you have to use Seam for this?
2. Use JMX. If you have an JMX enabled bean, you could use the twiddle script
(look up in
This seems to be happening in AbstractPhaseListener and looks like a bug. The
code in question is
|public boolean callPageActions(PhaseEvent event)
|{
| Lifecycle.setPhaseId( PhaseId.INVOKE_APPLICATION );
| boolean actionsWereCalled = false;
| try
|
Do you have a @Name(somethinghere) or just @Name ?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3969617#3969617
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3969617
___
When a conversation is created, the ConversationEntry object has the starttime
equal to the current time and the lastRequesttime set to 0. Should the
lastRequestTime be also initialized to the current time stamp? Here is why Im
asking this.
In my application, I start a conversation on a
I got this working after a lot of reverse engineering. Anyway, the secret was
that the method starting the conversation had to somehow call the
responseComplete method(by having an outcome) and then the conversation was
carried between screens. In my case, since it was a factory and nothing was
I have a simple Seam app that displays the list of categories as a datatable
and selecting a category from that. All works fine till that point. In the next
request(i.e. after a category has been selected), Im trying to get the books
that are associated with the category . The relation between
I modified the registration app not to work with EJBs but as Simple beans. The
other changes are to make the REgisterAction bean as a Application scope bean
and be available at Startup. I did those modifications just to make sure that
your original problem description was happening for me too.
I do have a seam managed EPC.
I am debugging the code to see how Conversation managed components are kept so
the LIE can be avoided.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3969080#3969080
Reply to the post :
bfo81 wrote :
| But when you create a new person all its properties are null. And when you
fill in the fields in a form and click save, then the persons properties are
still null during validation (phase 3). They get their concrete values later,
in phase 4 (update model values). And, alas,
I would like to request a feature to have support for Regex in pages.xml. That
would help in a lot of cases, for e.g. when you want to have a Login
Interceptor for all pages but the login.seam. It may look like bloated
functionality but its similar to the Rails' before_filter with the :except
Since you store the loggedIn in the session scope, you can use the rendered
to be something like
rendered=#{loggedIn != null} /
Seam automatically would look for the loggedIn attribute in all the scopes and
you could render the components accordingly.
View the original post :
I dont think you need to do build level changes. If you have a
ValidatorMessages.properties (and ValidatorMessages in other locales) available
in the Current ClassLoader, Hibernate should be able to use that instead of the
default validator messages that come bundled with it. Atleast thats how
Sorry, I dint understand the request clearly.
Anyway, you can configure Seam to use the same ValidatorMessages.properties by
configurng the components.xml for the resourceBundle component and specifying
the bundleName with ValidatorMessages. That way, youd only have one bundle
file for both
Sorry, the last answer dint come up quite well in the instant reply. Heres a
sample config of components.xml
| component name=resourceBundle
| property name=bundleNameValidatorMessages/property
| /component
|
View the original post :
Facelets are a good approach of doing these sorts of things, but all the
fragments will be redrawn for every screen. Its worked well for some simple
things I have tried, if you indicate your problems here or in facelets mailing
list, someone might be able to help.
View the original post :
Yeah, it throws a OOME -- PermGen Space Filled errors after some 10 - 15
redeployments. I had a read at the Resin site that it could be due to Debuggers
if any , and I use a fair amount of debugging with IDE, so I thought that could
lead to this, but yeah I get this error too.
View the
RobJellinghaus wrote :
| Why does @PersistenceContext work here but @In doesn't? I think I'm good
to go now (modulo the possibility that I'm still arranging my components the
wrong way, but some more code iteration will clue me in there). But I'm still
curious why the first way didn't
The @Log is only a easier way of using Apache Commons Logging. So just put a
log4j.properties with your appenders configured to write to disk and drop that
in the same jar file where your EJBs are present and it should work
View the original post :
Ah okay, I dint know that you had the EntityManager defined in the
components.xml. Ill give that a try(with this setup) and see what comes up.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3967611#3967611
Reply to the post :
I just tried this -- with both the application and session scopes and they
worked fine. I just modified the registration app that comes with the Seam
distro to do this. Ill be interested to take a look at your app though.
Raja
rajasaur at gmail dot com
View the original post :
sjmenden wrote :
| I want for the user to register a group, and be redirected to a page which
displays that group, and allows the user to modify that group ect., which is
why I am outjecting the Group.
|
This should work with your current code and which I thought was the problem you
This is standard JSF behaviour. Check out JSF Spec Section 7.4.2 under how the
default NavigationHandler should behave.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3967046#3967046
Reply to the post :
Thanks Petemuir, that was helpful information.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3965180#3965180
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3965180
___
jboss-user
You cannot use a Extended Persistence Context with Stateless beans. stateless
beans have no state and hence nothing to retain between requests. The
Entitymanager field is one such field where you would need to store it between
requests and having stateless architecture will not allow it.
View
Create a file called import.sql containing all the SQL that will load up your
data and put it in the top level of the jar file. Refer to the booking
example's jboss-seam-booking.jar file if you need more information(about where
to put the import.sql)
View the original post :
Create a file called import.sql containing all the SQL that will load up your
data and put it in the top level of the jar file. Refer to the booking
example's jboss-seam-booking.jar file if you need more information(about where
to put the import.sql)
View the original post :
Turn on the DEBUG log level and see what SQL i s getting generated and trace
from there. I havent tries this in EJB3 but Hibernate does throw the SQL
statements that get executed.
That might give u an idea where the problem is. ORA-0900 is invalid sql
statement (as is shown in ur original
Kurt,
In your ejb jar, do you have a ejb-jar.xml that has the information about
intercepting all calls to the SeamInterceptor? In the case of a JavaBean, the
SeamInterceptor is setup for you by Seam , so you dont do any extra plumbing,
but for EJBs, you would need to indicate to Seam to pass
The persistence.xml needs to be in META-INF of a *jar* file that is included in
the EAR archive. You cant put the file directly in META-INF of the ear.
To achieve what you need, you could tokenize the persistence.xml and feed the
token values when you build the persistence.xml that will be a
None, you can use a FacesMessage to send a message (Refer to the registration
example that comes with Seam). The org.jboss.seam.core.FacesContext is a
wrapper over the javax.faces.FacesContext and returns the current
implementation of javax.faces.FacesContext(which is ServletFacesContextImpl if
SmokingAPipe wrote :
| Solution 1: Use a Filter that keeps an EntityManager hanging around for the
duration of the request. Seems like an ugly way to do it, but I guess that
would be PHP-style, where it automatically frees DB connections when the
request is finished.
|
This is how the
Welcome to frustration while searching code. Ive tried this before and am still
not very comfortable at locating branches and source codes to attach to Idea.
Anyway , here are some answers that might help.
gcomnz wrote :
| 1. The EJB 3.0 releases don't contain source, making it difficult to
From the EJB Spec,
anonymous wrote :
| A persistence unit must have a name. Only one persistence unit of any given
name may be defined within a single EJB-JAR file, within a single WAR file,
within a single application client jar, or within an EAR (in the EAR root or
lib directory).
|
And
That said, the above dint work for a trivial example for me. Can you verify
this as well? (Or am i reading the spec wrong ?)
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3964830#3964830
Reply to the post :
Sorry scratch my previous comment, it does work well if you put the
persistence.xml in a jar file and make it a part of your archive. Note that you
would have to enter the jar file containing the managed classes in the
persistence.xml file.
View the original post :
Your Interface(Query) should contain getJon, setJon and the destroy methods.
You are calling methods on the interface from your view pages and they havent
been defined there.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3964873#3964873
Reply to the post :
I think thats a seam bug. Seam tries to interpolate any expressions in the
message bundle values and since it found a # in there, it seems to be looking
for characters next to it, which wont be there in your case. Here is the
snippet from Interpolator.interpolate thats causing the bug
|
Tomcat port is definitely one thing to change, which you can modify in
server/default/deploy/jbossweb-tomcat.sar/server.xml
For the rest of the ports that might conflict, run a nmap to see what ports are
exposed and change them accordingly in jboss's jboss-service.xml in
server/default/conf.
Excellent post. I think you should add it to the wiki. I had some doubts on
the managed Persistence Context but its clear now.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3964329#3964329
Reply to the post :
Does your Register Interface define the register() method ?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3964337#3964337
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3964337
___
Is your bean annotated with a @Name ? Also have you configured ur bean so
that it shouldnt be intercepted?
Can you post the annotations for your bean?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3964401#3964401
Reply to the post :
raja05 wrote : IAlso have you configured ur bean so that it shouldnt be
intercepted?
|
That should read Have you configured your bean so that it should be
intercepted. Not having any interceptor tags should be enough though.
View the original post :
http://www.jboss.com/index.html?module
The rest have been answered in the other post. Ill try and answer the one that
isnt answered there.
dpocock wrote :
| b) for the register.seam URL, does JSF/Seam simply look for a JSP file with
the same name, e.g. does it look for register.jsp, or if I put the URL
help.seam, does it look
50 matches
Mail list logo
