I'm, trying to get Seam to run with myfaces-1.1.3 (jboss-GA, seam from CVS) but
I just get:
| Class org.jboss.seam.jsf.SeamNavigationHandler is no
javax.faces.application.NavigationHandler
when deploying. Doesn't Seam work with 1.1.3 or am I missing something?
/Magnus
View the original pos
Cheers!
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3937188#3937188
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3937188
---
This SF.Net email is sponsored by xP
Seam ships with the same jars as in jboss RC1 (not the latest) so I belive that
Seam is not currently compatible with the latest ejb3/hibernate.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3937177#3937177
Reply to the post :
http://www.jboss.com/index.html
Sorry, but CR2 does include the latest versions of the hibernate jars. Do you
mean that you use the latest jars on an earlier version of jboss?
If you copied the jars from Seam then you actually downgraded hibernate ...
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewt
(cont ...)
I guess there're some changes in the ejb3/hibernate (?) is there any way to get
Seam to run on the never versions of jboss-as? (I actually do need a fix in
hibernate-annotations beta9 included in CR2)
/Magnus
View the original post :
http://www.jboss.com/index.html?module=bb&op=vie
I cannot get seam to run on jboss-4.0.4.CR2, just get errors like:
| java.lang.NoSuchMethodError:
javax.persistence.EntityManagerFactory.createEntityManager(Ljavax/persistence/PersistenceContextType;)Ljavax/persistence/EntityManager;
| at
org.jboss.seam.core.ManagedPersistenceContext.cr
Another way to solve this is to enclose the in
[...]
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3933076#3933076
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3933076
Yes I got all that in the code - basically just took the example from the docs
but change the Bean into EVENT and the DataModel into PAGE.
Now when select() is called the DataModel is null.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3932060#3932060
Reply
Ah sorry no just a plain JavaBean - I guess I better make it an EJB or add
Intercept.ALWAYS?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3930895#3930895
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3930895
---
Tried @PersistenceContext but I'm still getting null. This is an APPLICATION
component.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3930821#3930821
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3930821
I'm using "SeamExtendedManagedPersistencePhaseListener" that might have
something to do with it(?)
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3930290#3930290
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3930290
-
Hmm I just keep getting null in my:
| @In
| EntityManager em;
|
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3930284#3930284
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3930284
Use @In(create=true) to have seam create it for you as needed.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3930283#3930283
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3930283
--
Is it possible to get an EntityManager in the @Create method during @Startup?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3930217#3930217
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3930217
--
1. yes you're right but since you cannot mix to have some conversational
objects on the server while others are on the client this seems like an good
idéa to me. Not important sice I can solve this with @In @Out.
2. Again true but when you start doing kill-all-conversations() will it be
possibl
After some pondering, coding and some enlighment (thanks Gavin!), I have two
suggestions.
I have found myself wanting to keep per-page state, just as you would do in ye
olde days by putting the complete state in the URL-arguments. This can now
easily be done by useing PAGE-scoped data. I howev
I have a slight problem with @Factory (again) ... maybe factory is not meant to
be used this way but anyhow;
I have a 'data' component in the EVENT scope that have a @Factory method. I
want the factory to be called when no other component has outjected the 'data'
component. This works great as
Ok - but to start a new nested conversation for every page can't be good?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3929245#3929245
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3929245
---
Phew thanks - sorry for the confusion - appenrently didn't read up enough ..
still got one more question to understand what can be done.
If the state is keept as above:
I got a list of data in a CONVERSATION Component - data is saved on the server
but the state needed for rendering is on the c
In referance:
http://forum.java.sun.com/thread.jspa?threadID=478928&messageID=2229447
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3929167#3929167
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3929167
-
The problem is that when I click on an item on the list page I expect that the
item-detail view is rendered. But if I use the back-button and then click on
the item the item-view is *not* displayed instead the list-page is reloaded.
If using client-side state the item-view is shown (as expected)
After moving from client-side to server-side state the back-navigation doesn't
work any longer.
I get the typical JSF-behaviour:
1. Rendering a list-page.
2. Clicking on a item.
3. Render the details-page.
4. Using browser back.
5 .Clicking on item
6. list-page reloads --- with client-side state
Sorry soo my bad ... please ignore.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3929117#3929117
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3929117
---
This SF.N
I'm trying to post a commandLink with two params:
|
|
|
|
|
'type' is a @RequestParameter in component A
'index' is a @RequestParamater in component B
and A is injected into B.
When clicking - ZZZ gets injected into A but the action in B is never called.
It might be a bit
Having several Conversations on the same page might be taking it one step to
far at this time. Having named/parallell Conversations on the other hand seems
very usefull to me.
| @Begin(join=true, name="wiz_one"}
| public String startWizardOne() { }
|
| @Begin(join=true, name="wiz_two"}
Sorry I haven't done any performance tests with JSF or Seam but you are
probably right - server side is much better in just about every situations.
My suspicious attitude in this case is biased by prevoius experiances with
(mainly proprietary) frameworks that took tremendous performance hits wi
To keep the server as light as possible. With large tables and many users I
really don't want to keep all that state on the server if that can be avoided.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3928984#3928984
Reply to the post :
http://www.jboss.com/
One thing I'd like to do to is to have a menu of actions. Each action will
start a Wizard but the menu is still present even if a Wizard for one of the
actions is started. Now, if the user clicks on another action, while still
beeing in the middle of the first Wizard one I'd like to start a Conv
Do you have any other suggestions then? Should I put my sensitive information
in the HttpSession by hand?
Another extension to Seam could be to keep SESSION components on the server
just like PAGE components always are on the client.
View the original post :
http://www.jboss.com/index.html?mo
I would like to to have a more fine grained control over what is saved on the
client vs server, something like:
|@Scope(SESSION, state=server)
|
I really like to keep, for example, the id of the loggedin user on the server
for security reasons. Other state data can be saved on the clien
One problem with parallell/named conversations would be to handle bijections
(etc) if the same component lives in parallell conversations. Solvable but its
more to it than just adding name to @Begin and @End.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=392
Ever considered adding named-conversations to seam [EMAIL
PROTECTED](name="adduser")]? This way it would be possible to control serveral
parallell conversation easily at the same time. This could be usefull for ex.
when you have several independent zones on the same page.
View the original pos
Yes but sooner or later (sooner in this case) more then I want to send to the
client is going to be fetched from the database.
>From what I currently understand the only way to avoid this problem is not to
>use the same class as the Entity and the Seam-Component, and that doesn't feel
>to good
I have several Entitys that are related with many-to-one as well as
many-to-many. I need to use entitys that have relations as @Page-components
(actually I use client-side state for the complete app).
What I don't want to do is to serialize the complete "entity-tree" to the
client. So the quie
Sorry haven't got around to the traces yet, but I guess that one way to avoid
the @Factory problem is to scope the affected component as @Page (or higher ...)
/Magnus
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3927585#3927585
Reply to the post :
http://w
I need to a have a conversation running at "all" times. Is there a way to
always have a Conversation associated with a window without having to call a
@Begin method? I also think it would be nice if you could start a conversation
when accessing an Object with the @Coversational annotation
(@Cov
What I'm doing is that I have a dataTable that gets it data from a EVENT scoped
bean. I have commandLinks outside as well as inside the table. When posting
from the page the tree in reconstructed and I'm ending up with the situation
discussed in this thread.
I am not using any DataModel featues
"[EMAIL PROTECTED]" wrote : Actually, can you guys tell me if adding
@Intercept(ALWAYS) is an alternative solution to your problem?
Not for me, I'm getting an IllegalStateException "No Conversation Id"
(Just a quick test - I can give it another go tonight maybe (european time))
View the origina
"[EMAIL PROTECTED]" wrote : Right, but you are using the #{list} during the
RESTORE_VIEW phase. And the thing about the restore view phase is that Seam
doesn't really let you "do stuff" (eg. access databases) during that phase
because the conversation id is not known.
|
Ok - sorry for beeing
Well not really IMHO - I have #{list} and when entering the page in default
mode I want the factory to be called picking up default vales for the list.
Clicking on a link/button, invoking an action, the same page gets redisplayted
but a parameter is provided to the action so that the contents of
Yeaj :-) getting somewhere - so is calling the factory here considered a bug? I
guess that if there's no factory defined then the value will remain null even
after RESTORE_VIEW so would the solution to ignore factory-methods during
RESTORE_VIEW be alright?
View the original post :
http://www.
Some more info, I'm not sure if all this has any relevance or not but here goes.
First this happens when I use a with a parameter, I haven't
tested with a 'normal' post yet.
Seam is trying to find a value for A - A is Scoped as EVENT.
During the BEFORE RESTORE_VIEW phase the factory method for
Is there anything special you'd like to see? Please note that adding @Factory
as above in this thread create a call to the factory method.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3923379#3923379
Reply to the post :
http://www.jboss.com/index.html?mo
Gavin this cannot be a correct behaviour?
It seems like the factory method is called at the start of the cycle before the
action method is called. Shouldn't the the factory method be called at the end
of the cycle if the requested context-variable is still null after the action
invokation?
/M
"[EMAIL PROTECTED]" wrote : Why would it be called?
Well - you tell me :-)
I did the following test - I added a @Factory in HotelBookingAction.java, like
this:
| @Factory("hotels")
| @Begin(join=true)
| public String find() {
|... }
|
This result in that the find() method is c
I have this:
| @In(create = true)
| private InObj inObj;
|
| @Out
| private OutObj outObj
|
| @Factory("outObj")
| public void init() { .. }
|
| public String action() [ ... }
|
The inObj is a Session object.
When accesing 'outObj' from a page the Factory method is cal
No that was missing. So there're no default JNDI bindings?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3919336#3919336
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3919336
--
"[EMAIL PROTECTED]" wrote :
| org.jboss.seam.core.init.managedPersistenceContexts em
| | em.persistenceUnitJndiName java:/EntityManagerFactories/testDatabase
|
| Means look in "java:/EntityManagerFactories/testDatabase" for the EMF.
|
Finally got all to run and so decided to upgrade
Ok - a bit of topic - I'm trying the upgrade to the nightly builds but I can
no longer use:
anonymous wrote : @EmbeddableSuperclass
|
| or
|
| @Id(generate = GeneratorType.AUTO)
are those really gone from ejb3?
View the original post :
http://www.jboss.com/index.html?module=bb&op=vi
Thanks - I saw something in jira now when it was availible again.
@Intercept(ALWAYS) works beautifully
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3919207#3919207
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=39192
I have several session beans that get picked up by ejb3-container and they also
get picked up by seam. But when calling the action method on one of the beans
nothing gets injected - all the other beans all works as expected: The bean in
question is the last one that gets defined by seam.
(Stil
Doh! Yes ofcourse - this is what happens when you just read and don't think!
Thanks for all your help Gavin!!!
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3918995#3918995
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply
Again - I have this is seam.properties:
| org.jboss.seam.core.init.managedPersistenceContexts em
| em.persistenceUnitName java:/EntityManagerFactories/testDatabase
em is created:
[Component] Component: em, scope: CONVERSATION, type: JAVA_BEAN, class:
org.jboss.seam.core.ManagedPersistenceCon
Ok - so it is better to run CVS then beta1? Is there a beta2 anytime soon?
Back to my problem.
Now I get the 'em' is created ok but I get:
javax.ejb.EJBTransactionRolledbackException: null; CausedByException is:
| EntityManagerFactory not found
when I do:
@In(create = true)
|
Thanks - then the info is wrong here
http://docs.jboss.com/seam/reference/en/html/configuration.html#d0e1597 but it
is correct here
http://docs.jboss.com/seam/reference/en/html/components.html#d0e2395,
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3918882#39
I'm now trying to get seam-managed persistance to work by adding this to
seam.properties:
org.jboss.seam.init.managedPersistenceContexts em
| em.persistenceUnitName java:/EntityManagerFactories/testDatabase
but 'em' does not get created. I have also tried to add bogus stuff to
seam.properties a
Yes great thanks - when thinking about it that is the best and most clean
solution. Thanks again.
/Magnus
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3918640#3918640
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=39
I'm back after some playing around and I could really use some pointers.
I have done some tests using SeamTest trying to use my own EM but I cannot get
it to work. This is mainly because 'Component.getInstance()' returns a Proxy
and therefore I cannot replace the EM in the returned instance. Whe
anonymous wrote :
| But I really think it is very wierd to mock the database in integration
tests. It is much, much better to actually test that the data is getting all
the way to the db.
|
I have to disagree, just because you want to test the interaction between two
objects it does not n
Really? A concrete example of what I would like to do, would be to run the
"RegisterTest" with a mocked em instance, to test that the session-bean-logic
and the navigation flow is working as expected, but without actually insering
anything into any database.
This (imho) should be very usefull i
Hmm ... yes ... not that I'm sure how to do that ... an example would be nice.
I would still like the test to run in the microcontainer so that some object
still uses a "real" EntityManager, if that is this possible? When should I
inject my EM so that the microcontainer doesn't inject its EM af
What I mean is I want to use a EntityManager that basically just returns what I
tell it to return without accessing the database, this to test code given a
test scenario without having to access a database.
One such "mock" is to make persist() just do nothing or make it fail ...
This would to
Maybe this is a pure ejb3 question but I cannot find how to to this:
I want to replace the EntityManager with a mocked EntityManager so that
my EntityManager is used for all @PersistenceContext injections.
How would I do that? Any pointers appreciated.
Thanks,
/Magnus
View the original post :
I have just started to play a bit with seam and I have a questions on how to
best use seam.
If I want to divide my application i two layers/tiers how do I do that? What I
want to do is to have the webapp in one server and the business layer (ejbs) in
one server. It seams a bit tricky to me to d
64 matches
Mail list logo
