Hi,
I still have problems with getting my local beans into java:comp/env.
In my application I have annotated Local beans in an ear - I will deploy the
ear more than one time so I need my beans in the 'ear-name/' global-namespace.
I must also do some dynamic-lookups (non-annotated) using the
Thanks,
but is this not possible to accomplish this with annotations?
Currently my beans ends up in my-ear/MyBean/local (or remote) with the default
behavior with simple annotations. If I want (the local) beans in java:comp/env
as well I need ejb-jar.xml as well as jboss.xml?
I cannot
Hi,
I'm trying to look up a Bean using java:comp/env/MyBean but I just keep getting
env not bound (using jbossAS 4.2.1.GA)
Isn't java:comp/env/ supported for looking up Bean in the local namespace?
Thanks
/Magnus
View the original post :
I have added a comment to the issue above - this cannot be just a configuration
issue, can it?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4101598#4101598
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4101598
s:link builds absolute paths for me, (just like this:
http://jira.jboss.org/jira/browse/JBSEAM-2144)
does anyone know why?
thanks.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4101550#4101550
Reply to the post :
When clicking to fast on my ajax-links that calls methods in my backing
conversation I get: The conversation ended, timed out or was processing another
request
What is the best way to avoid this? My user tends to be over achievers who
clicks a-lot ;-)
View the original post :
All very good suggestions and I have cycled through most of them in one way or
another.
Hopefully Gavin is right and it will just work(tm) letting the Conversations
timeout.
Starting the Conversation at the first submit might work in some cases but
usually the state (lists of objects etc) is
stephen.friedrich wrote : To further complicate matters:
| What one would sometimes want instead is to have a separate long-running
conversation for each tab/menu/page, isn't that so?
This is pretty much covered by explicit conversation id (§6.6) and Workspace
management (§6.7).
View the
Well you could use conversationList but how do you know what conversations are
in use? The user could use several windows so many conversation could be active.
The (only) way do solve this (if it really needs solving) is to extend s:link
(or similar) with a new propagation, say, endAndBegin and
I have a menu system where the user selects tasks/pages, the menu system is
shown on all pages so the user can select a new task/page at any time.
Each selection creates a new Conversation - my concern is that this leaves a
(possibly) huge amount of discarded Conversations around.
Is this bad
No - I might have dirty state in the Conversation that a want to get rid of.
Also if the user selects the same page/task I want a new, empty, conversation.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4067199#4067199
Reply to the post :
I have a Component defined like:
| @Name(myList)
| @Scope(ScopeType.CONVERSATION)
| @Conversational
| public class MyList extends LinkedListMy {
| }
|
when using this on a page and posting back from the same page for the second
time, i end up with an error:
value of context
When I post an enum-value value using the s:convertEnum I just end up with:
| java.lang.IllegalArgumentException: java.lang.Object is not an enum type
| at java.lang.Class.enumConstantDirectory(Class.java:2965)
| at java.lang.Enum.valueOf(Enum.java:187)
| at
I get the same, Seam calls EJB3StandaloneBootstrap.boot(null) and
EJB3StandaloneBootstrap apparently does not like the null name.
Is there maybe a version conflict here?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4053663#4053663
Reply to the post :
I'm using Seam 1.2.1.GA with the included jboss-ejb3-all.jar
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4053673#4053673
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4053673
I have also had issues like this and what I actually would like to suggest is
that Seam adds yet another Scope a Window-Scope.
This Scope should be connected to a Window and should be started/forked with
each Window. It should not be @Ended like a Conversation but work more like the
Session
I have some problems making the Conversation work like I want to, this is
loosely related to
http://www.jboss.com/index.html?module=bbop=viewtopict=108452.
I have a number of menu-alternatives each menu leads to wizard-like dialog
structure with multiple levels of nested conversations.
Since
Thanks,
this is what I expected - what I also need to do at times is to pop just some
nested levels but still propagate the top conversation(s).
From what I understand a call to @End always ends the inner-most Conversation?
If I need more control over the conversation stack for ex if I need
Is it possible to cancel/evict changes made to the current em when @End'ing a
nested Conversation?
Typically I have two methods save() and cancel() on my nested
Conversation-Components on save I do em.flush() but on cancel() I need to
rollback any changes.
Currently I loop through all
§8.6
http://docs.jboss.com/seam/1.2.1.GA/reference/en/html/persistence.html#d0e5589
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4045487#4045487
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4045487
I just updated from CVS when restarting my application on AS 4.0.5 I get
Caused by: java.lang.NoSuchMethodException:
org.apache.myfaces.application.ApplicationImpl.getELResolver()
| at java.lang.Class.getMethod(Class.java:1605)
| at
http://jira.jboss.org/jira/browse/JBSEAM-1263
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4041300#4041300
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4041300
___
jboss-user
|
| ?xml version=1.0 encoding=UTF-8?
| components xmlns=http://jboss.com/products/seam/components;
| xmlns:core=http://jboss.com/products/seam/core;
| xmlns:security=http://jboss.com/products/seam/security;
|
I'm trying out the entityConverter, and I have a control like:
| h:selectManyListbox value=#{tagSearch.selected}
| s:selectItems value=#{tagSearch.tags} var=tag label=#{tag.value} /
| s:convertEntity /
| /h:selectManyListbox
|
displaying this works fine but when I submit the form
Hi,
I'm trying to veto an update in MyHome by overriding the update() method like
this:
| public String update() {
| if(!valid()) {
| return null;
| }
| return super.update();
| }
|
My problem here is that the UPDATE request to the database is issued even if
Ok,
been away from seam for a while but previously I always used em.merge( .. )
when handling objects in Conversations. Has something changed in seam in
regarding to Transactions/Conversations (maybe the Homes are using Extended-PCs
or something else I have not used yet?)
View the original
When looking up the EntityManager by hand from the JNDI I get:
| javax.persistence.TransactionRequiredException: no transaction is in
progress
|
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4000856#4000856
Reply to the post :
So basically there is no Transaction during startup? So I cannot expect
@PersistenceContext nor a manual lookup to work?
Is there any way to start a Transaction by hand?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4001154#4001154
Reply to the post :
Using 1.1.0.GA
I know I've had this problem before but it started working under 1.0.x
somewhere but now I have the same problem again.
I get no EntityManager during @Startup (Application Scoped).
Using @In(create = true) EntityManager em; does not work and em =
(EntityManager)
I have page that has a ajax4jsf reRender area, that rerenders when a drop-down
changes. I'm also trying to make this page work RESTfully.
The problem is that when the drop-down changes the reponse from the
ajax-request is not an ajax4jsf response but Redirects etc, this is not so
good. I would
This should probably go in Jira, but jira doesn't like me right now so here
goes:
I get this:
| java.lang.NullPointerException
| at
org.jboss.seam.core.Manager.destroyNestedContexts(Manager.java:484)
| at
sorry no 1.0.1.GA should been in the original post *blush*
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3986606#3986606
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3986606
___
(Seam 1.0.1.GA)
I have a page with some input-fields, when navigating to this page data is
outjected in the PAGE-scope.
I fill in some data in the fields and submit the form and then use the
components in the PAGE-scope in the action.
If the validation failes and the page is re-rendered the
Ok, but ias fas as I can see the data writing is commited. I can log on the
database and see the correct data.
If I start a new application the correct data is read from the database.
However the Seam Managed Persistence (SMP) does not re-read already read rows
without an explicit refresh().
Yes I'm aware of that - I just took for granted that the EM/Session was closed
or cleared after the end of the web-request/transaction. I was apparently wrong.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3984216#3984216
Reply to the post :
The following is happening to me when I'm using both @PersistenceContext and
Seam Managed Persistence, maybe this is a no-no?
1. I have a Stateless Session Bean (not managed by seam) that is called by
Quartz once is while to update some statistics in the database. This Bean is
using
Ok, but I'd like to understand why. I have no second-level cache and when I
writing through the @PersistenceContext the data ends up in the database, no
explicit flush().
So why is the data not fetched using the Seam Managed Persistence?
Where is the data cashed?
And why does flush() help?
Using 1.0.1 I have trouble sending beans as arguments in remoting calls.
Using simple types like this:
| Seam.Component.getInstance(searchEngine).doIt(null, daCallback);
| Seam.Component.getInstance(searchEngine).doIt(XXX, daCallback);
|
is working, but when using a Bean as argument:
Upgraded to CVS and it works, so I guess that it is a bug in 1.0.1 - can
someone confirm this?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3976433#3976433
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3976433
Using 1.0.1.GA I am trying to run Integration style test cases with Seam
Managed Persistence. My problem is that nothing is written to the database; so
I tried with a em.flush() but then I get a
javax.persistence.TransactionRequiredException: no transaction is in progress.
So it seams to me
40 matches
Mail list logo
