I usually get this when there is an error in pages.xml somewhere.
Check your pages.xml.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4103800#4103800
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4103800
My understanding of it is that :
@PersistenceContext (EJB PC) - Single shot persistence context for the duration
of the method call
@PersistenceContext(Type=EXTENDED) (Extended EJB PC) - Persistence context that
lasts for the duration of the session bean, but not shareable across session
I know the s:link and s:button controls append params to the URL using page
params, but is there any way to do it for the h:commandButton control, or the
ajaxy submits from Richfaces? Bearing in mind the s:link/button controls don't
post the forms so they are useless for data entry submitters.
(I know this is an old-ish post, but I came across it when I had another
problem, so thought I'd chime in for the next person to come across it)
It seems like the current solution is to manually add a param to the link with
the param name, and set it to null. This is what the contact example
That's a great article and highlights how nested conversations should be used.
Seam needs more of these kinds of articles that illustrate how things should be
used, rather than everyone (including myself) trying to shoehorn their ideas
into Seam based on how they THINK it should work.
Great
Seam removes most if not all the pain with parameters, get requests, bean
initialization, and well, basically everything else. Seam offers a couple of
different models of navigation, from a JSF style, to a full work flow style.
Regarding Orm, if you use JPA, with the hibernate provider, you can
I have a factory method that takes a request parameter, and loads an entity. My
problem relates to what happens when the factory is passed an id that is not a
valid value, and how it is handled.
One option is to throw the entity not found exception which then redirects to a
single error page.
Yep, that worksThanks for the response!
FYI for the next unfortunate soul that comes across this. Instead of using :
| @RequestParameter
| private Long myId
|
you need to take out the request parameter annotation and just have the member
declaration.
In your bean interface add the
Did you have any luck with this in the end? I've come across the same problem
in that params are not carried across checks for logins. Kind of causes
problems with RESTful URLS.
In my case, Seam is checking for the login because I have a restrict tag on the
page, which in turn is checking for
I've got a problem with params defined in pages.xml disappearing. The problem
can be seen by adding the following button to the search.xhtml page in the seam
contact list demo :
|h:commandButton value=Dummy action=none/
|
If you add this after the search button, open up the
In pages.xml put something like :
| conversation name=testConversation param-name=myID
param-value=#{widget.id}/
|
Then for your page use something like :
| page . conversation=testConversation/
|
This sets the conversation Id to the value of widget.id, but there are a
First off, this isn't against Seam, or any implemented feature in seam, just
some general thoughts on the usefulness of conversations in real world
environments. In particular, I'm thinking of some of the aspects that Seam
gives us such as the non-modality of conversations (open in new
I'm no expert on Seam-Gen generated edit pages, but I think it goes like this :
The edit pages edits a Widget called widget, it doesn't matter if it is a new
one, or an existing one.
You create a factory method for widget which in the same bean, injects the
parameter widgetId. The factory
Wasn't there something about outjecting entity beans being a bit of a hog, with
the preference being to use properties instead of outjection?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4078873#4078873
Reply to the post :
amitev :
Yes, basically, when using begin-conversation in pages.xml your only option is
to use join=true
without it, a page refresh tries to start a new conversation, and nested=true
means a new nested conversation is started each time the page is rendered, even
if it is coming from an event
*Bump*
Yeah, I'm wondering the same thing. I thought it did as you are suggesting, but
when I tested that assumption back around 1.2.0, it didn't quite work out
(can't remember why).
A Page scope such as this would be great for search pages where you want the
scope to last as long as you are
The fact that there needs to be two separate ways of defining the start page,
and are both mutually exclusive is a bit of a pain. It forces you to choose a
method that you will be using to start pageflows (either in the link, or in the
@begin annotation) unless you want to start maintaining two
Thanks both of you for taking a stab at it. So basically, it is an object that
has the same kind of duration as the JSF component tree while an event duration
lasts until the end of the request.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4077515#4077515
anonymous wrote : This exit to the entry point conversation handling is
actually already available with a slightly different model (but Gavin convinced
me it is better) in any seam-gen produced application.
Just curious, but how? I posted about it a while back, and I think Gavin
pointed me to
Yeah, this is something I'm interested in.
I know you can have a per-page xml file, but one problem is that there is still
some shared stuff that must go in pages.xml like the elements that define the
conversation ids using business ids. These cannot go in xyz.page.xml files, and
chances are
Wonderful, as usual, I stand corrected!
Thanks Chaps,
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4068348#4068348
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4068348
___
AFAIK, you cannot perform multiple data entry conversations in a nested fashion
without having an all-or-nothing problem with regards to saving the data.
The problem is that each nested conversation uses the same persistence context,
and when you flush for a nested conversation, you are
Origingally, my icky comment was related to the fact that I think you *might*
run into a problem using the rollback code on a method annotated with @Remove
and @Destroy since I don't know whether these annotations result in the method
being called at other times (i.e. the bean is passivated,
It is possible.
Maybe you haven't defined the getters and setters on the interface for the
session bean. If you post any error messages or results you get along with any
code, that might help.
Any properties on the session bean are read and written to just like any other
property is handled
I've come across this problem before, and pretty much used the same solution to
solve it.
When you move from your edit page to the view page after canceling your
changes, the conversation object itself is re-used, and uses the same entity
manager. The entity manager contains an instance of
Is getProcessDefinitions() defined in your ToolBar interface?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4060543#4060543
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4060543
Obviously, this is an undocumented feature so I could be wrong here but:
The conversation element is for business conversation Ids, so you can define
the conversation Id based on a context variable. You can also use the
conversation element to define a conversation parameter definition and
anonymous wrote : If you are brand new to Java web development, Seam will
appear to be confusing and terrible.
I'm new to web development, and found that coming from Client Server to the web
was thoroughly depressing Once I understood the problems involved in the bigger
picture of web
anonymous wrote :
http://blog.xam.dk/archives/72-Exadel-Plugins-are-now-opensourced.html -
working nicely for me here :)
You must be the lucky one ;-)
I downloaded everything, including the build drivers included on the nightly
build page, dumped it all in a folder, and it doesn't quite work.
enhanzo :
I think the problem there is that the information has to cross the conversation
boundary. The bean receiving the param needs to exist in the next page's
conversation, and the entity containing the param exists only in the previous
conversation which we probably just ended and is
As a possible suggection, did you put getters and setters on the entityIdField
and in any interface that the bean implements?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4058329#4058329
Reply to the post :
I think view-ids are used as identifiers as much as a url, hence there is no EL
interpolation done on them. If you notice, anywhere a view is referenced for
redirection, the parameters for the view are separate as opposed to part of the
view-id.
I did think about my problem and whether EL
Oviously that should have been :
| String returnHome() {
| return homePage;
| }
|
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4058342#4058342
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4058342
Depends on a few things, posting some code might help.
What are the create and required attributes on the @In annotation set to?
If Seam cannot create a component because of an error somewhere in the creation
process, that might be a source of the problem, but it should raise an
exception
If I'm understanding the problem right, you could put the initialization code
into a @Create annotated method which would be called when when the backing
bean is created as long as the backing bean is used only with this page. I
think you would have to make the bean conversational scope, and
Now my understanding of stateful vs Stateless session beans is that stateful
ones contain state, and stateless beans don't, and are just worker beans that
perform tasks.
However, Seam kind of blurs the lines between the two since any state can be
held outside the bean as a context variable and
If I'm understanding your question, you could just use a factory method to
create the bean and initialize it on demand.
| @Factory(name=gameAction,scope=SESSION)
| public GameAction initGameAction() {
|
| GameAction result = new GameAction(someId,someName);
| return
What I'm trying to do is at the end of a pageflow, go back to the original page
that started the page flow, in this case the widgetView page. To do so I need
to pass the widgetId as a request parameter so the widgetView knows which
widget to display.
I see from the xml schema that pageflows
anonymous wrote : I would seam-gen up an application, add a couple of CRUD
entities and take a look at the approach used there - it's what we would
recommend. You nest as many CRUDs as you like using this pattern - it's
simple to extend.
I did try to seam-gen up an application using my dummy
I started to have another look at the Issues example application that comes
with Seam since it has a lot of nested conversations as you drill down from
project to issue etc.. kind of similar to what I'm looking for.
Looks like it has problems also. If you change the project name, click done (no
I have an edit page for a widget, and each widget has a set of sub widgets. I
want to show the widget details as editable inputTexts, and have a clickable
list of subwidgets. If you click on a subwidget, you go to a page to edit the
subwidget, click save on the subwidget page, and it should
Hey,
I had considered that, and part of my reluctance is the messyness involved in
keeping a new subwidget informed of it's widget and vice versa. The subwidget
has a property called Widget which refers to the owning widget. The Widget has
a property called getSubWidgets which returns the
In theory, it should be easier if you are using facelets since you should
already have your view code split into sections such as header, body, menu,
footer etc, it's just a matter of putting the ui:insert facelet tags into the
right place in the layout table, or wrapping the ui:insert in a div
Hey Pete,
Yes, I saw that, I have looked at the decorate stuff, actually, I think I have
copied edit.xhtml to my app to look at start trying to use it. I do need to
add an access key element on to there, but that should be easy.
I did implement a facelet for date edits, and my main problem
Oh yeah a list apart is a great resource for css stuff, including articles on
why we should be using css.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4055832#4055832
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4055832
What kind of link is it you are clicking on?
I had a weird error where I was getting the same value in my data selection,
and it seemed to be because I was returning a page flow action in the command
link
| h:commandLink action=editMyObject/
|
It appeared that when I did this, the data
Perhaps this might help :
http://jira.jboss.org/jira/browse/JBSEAM-949
If I am reading it correctly, then it would be possible to write your own
custom session manager for seam, which may allow you access to the session for
another user.
Of course, it would mean writing a session manager
Ok, all done :
http://jira.jboss.org/jira/browse/JBSEAM-1423
I had to attach it in 4 parts, all zipped. I've included test cases that
demonstrates the problem.
In the test app (a cut down version of my dummy book store app) there is no
exception on the page flow navigation page changes,
As a really big stab in the dark, how about :
| page view-id=/showSpace.xhtml
| restrict#{not selectedSpaceInstance = null}/restrict
| /page
|
I'm not even sure if this is the correct syntax, but I'm sure you get the idea.
If this doesn't work, you could always have a bean method
Ok, now I think I know what the problem is (but not the answer).
| conversation name=bookConv parameter-name=bookId
parameter-value=#{book.id} /
|
This xml lets seam detect an existing conversation for the same entity, and
switches to it instead of creating a new one. It works fine when
Sorry, should clarify that :
according to http://jira.jboss.com/jira/browse/JBSEAM-976, the id= portion of
the @Begin annotation is possibly being deprecated in favour of natural
conversation Ids in the pages.xml, not the whole @Begin annotation.
View the original post :
Personally, I would consider this a data issue, not so much a framework issue.
Just put a completed field in your Order entity that is only set when the
order is completed.
Then you can call select * from orders o where completed = null or whatever
to see the incompleted orders.
I have stripped down my seam-gen generated bookstore test app to the minimum,
and created an import sql script and written some test cases to demonstrate the
problem.
Do you want me to include all 30meg (zipped) of jars also, or should I just
delete them from the zip file? There's nothing
Hey all,
I keep getting this error message at various times as I navigate through my
test bookstore app. Usually it appears when I change conversations on the
switcher, but also during pageflow navigation. I'm using seam 1.2.1GA on JBoss
4.05
In pages.xml I define :
| conversation
I use it to create an empty application shell as a starting point.
I tend not to use the CRUD stuff, since as I recall, it uses the Seam Framework
(entity home Co) for that.
Call me a masochist, but I'm still working out how to do entity Crud, with
RESTful edit pages on my own (I'm almost
D'oh, yeah, I know that should be :
| propagation=nest
|
That seems to get rid of the original problem, but introduces other problems
that I'll have to go investigate.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4051908#4051908
Reply to the
I use Windows and exploded deployment, and am not sure what the problem is.
When I am devloping, if I do a 'clean', it tries to delete everything but some
jars are locked. I just ignore that, re-deploy, and all my code is updated even
if some of the deployed standard jars are not.
I'm using
What? nobody using non-session scoped, stateful search forms? ;-)
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4045995#4045995
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4045995
Ok, thanks matt.
It's not so much the resources, its more a case of having to deal with the
conversation on the page (ending it properly).
If they search and click a menu item to move to another section, then the
conversation sticks around, assuming that you have propagation=none on your
I have a quick question regarding the scope of a bean used in a search form.
The search bean holds a fixed number of results (i.e. the first 100 results)
and since it is not an unbounded query, I'd like to make it stateful so I don't
have to re-query every time the user changes page number, or
Why not just swap object X for object Y when you make the selection, and
outject the value as a conversational context variable, assuming they are meant
to be sharing the same context variable?
The other option (and I'm not sure whether this will work, or how well it will
work), is to put
Do you have an s:validate tag around your control, or an s:validateAll tag
around multiple controls?
From the reference guide :
anonymous wrote : The only thing here that is specific to Seam is the
s:validateAll tag. This JSF component tells JSF to validate
| all the contained input fields
I've been playing around with the notion of a RESTFul URL that starts a
conversation.
The most obvious place to start a conversation for a restful URL is in
pages.xml with the begin-conversation join=true pageflow=MyEdit tag in
the edit page. The pageflow requires the flow to start with the
I believe that the @DataModel annotation should work with any kind of object,
entities or not regardless of where the list came from. In theory anyways!
The datamodelselection member should probably be of the lowest type on the
object hierarchy. If you have completely unrelated object types,
If you are talking about CRUD using the Seam Framework (EntityHome and all
that) then I believe the contact list example uses that particular method of
crud.
If you are talking about writing your own set of CRUD pages, then there are a
number of ways to do it.
In the Issues example - inject
I haven't really gotten into JSF selectors and enums so I don't have a clue.
Ye gads man, 27 pages in one. How about using a nice page flow and individual
pages and save yourself some sanity (maybe)
View the original post :
Can you post your h:datatable or whatever you are using to display the list.
Off the top of my head, when I get these problems it's because I am using the
member variable for the list source as opposed to the context variable. Check
that you are using :
| h:dataTable
Regarding seam re-starting conversations in pageflows
http://jira.jboss.org/jira/browse/JBSEAM-1292
aka forum post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4043286#4043286
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4043694#4043694
Reply
I don't know anyplace that currently does it, but I'm no expert. Take a look at
Michael Yuans posts about virtual private servers that lets you put what you
want on the server.
I'll refer you to his blog for details :
http://www.michaelyuan.com/blog/index.php?s=hosting
View the original
anonymous wrote : i know max is strongly in favour of a wtp style structure so
i think that will be in there!
Can you elaborate on what a wtp style structure is? Do you mean a standard web
project type structure i.e. an organized seam-gen project in the IDE?
I really can't wait for RHDS to
Can you show where the customers list is coming from, and what your syntax for
the datatable tag is?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4043257#4043257
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4043257
Hey, thanks for the reply,
anonymous wrote :
| Yes, I think this is correct. I need to think about it tho.
|
Ok, my only thought was that nested=true would result in a new nested
conversation on each render, and join = false results in errors on each render,
so if it was by design, it
anonymous wrote :
| All the plugins that make up rhds will be available free on an eclipse
update site - so for home dev you maynot even need a license
|
It's a question of this whole RHDS vs the community version which hasn't fully
been explained clearly. From my last take on it, from a
Looking at this a bit more, it seems that join=true might not be the best
answer.
In my dummy app, I have meeting objects which has one or more person objects as
members. When editing the meeting, you can select add member to go to the
person search page where you select a person and the
If I'm understanding correctly, you want to use a more spring like
service/dao design for developing your application? .You can implement DAOs and
have them injected into your stateful beans :
I think you can implement your DAOs as stateless session beans since the only
'state' you have is
Oops, sorry, posted before I saw your last post describing your problem.
From your code, the injection happens after the constructor is called.
What you need is :
|
| @Create
| public void forwardToBaseAction() {
| super.setEntity(company)
| }
|
|
The @Create
Hey Carlos
anonymous wrote :
| but when should i call the forwardToBaseAction() ??? In my Action
constructor ??
As Christian said, the @Create annotation tells seam to call this function once
the bean has been constructed.
If you use Christians method beware that when you call setEntity,
There have been a number of posts here from people using Glassfish, I'd suggest
using the forum search for Glassfish.
AFAIK, people have Seam apps running under glassfish, but it takes a little
more work on the config files.
View the original post :
Got mine today from Bookpool.
Now I just need to find some peace and quiet to read it this weekend.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4043391#4043391
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4043391
FYI - using Seam 1.2.1 GA, with a seam-gen built app.
I was having some issues with pageflows while I was writing a dummy app, and
ended up running into so many brick walls with pageflows that I decided to
write a PageFlow test application so I could determine how they really work. I
have a
Regarding packaging, I started with Netbeans, and built the whole ear/jar/war
project structure, and built it from scratch (obviously utilizing the
documentation and examples, and a couple of posts from Netbeans bloggers) and
it went pretty well and I'm fairly new at Java. I think it is very
anonymous wrote : The thing I don't like about seam-gen, is that I feel like my
applications gets to have lots of code I don't quite understand... ...
Hey, this isn't app fuse ;-)
I had the exact same problem with app fuse, so I understand your concern, but
seam-gen creates very little code
Thanks Captn,
I changed the entity manager reference over to :
| @In
| private EntityManager entityManager;
|
and it works like a charm,
DG
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4038039#4038039
Reply to the post :
Hey Peter, thanks for the reply.
I changed my page flow to use :
| start-state name=teststart
| transition to=test1/
| /start-state
|
|
| page name=test1 view-id=/testpage1.xhtml
| transition name=next to=test2 /
| /page
|
and
Regarding pageflows from the pages.xml file, are you using the generic
catch-all *' view id and assigning outcomes to pageflows? i.e.
| page view-id=*'
| navigation
| rule if-outcome=startWizard
| begin-conversation pageflow=wizardFlow/
| /rule
| /navigation
| /page
|
anonymous wrote : The outcome you return from your action method on starting
the pageflow should determine which transition it uses from the start-state -
if you are sure it doesn't, raise an issue in JIRA
AFAICT, when using the start-state pageflow the following applies :
void action methods
anonymous wrote : Actually, you should have this in your component:
Ah yes, you are correct, the factory is used to generate the content, not the
to declare actual variable itself which must be specified elsewhere (using the
datamodel in this case).
Thanks for the correction,
DG
View the
I'm having some problems with using flushMode to prevent auto flushing of
changes to the data.
In the example, I have a meeting object, with a one to many relationship to
person objects. In the meeting editor, I have the meeting info, and the list of
members, each with a remove link to remove
Here's my take on it, I'm not a seam expert, but I have had my fair share of
these types of problems. However, trying some or all of these ideas may help
you out.
I believe that the standard JSF way of accessing a list (i.e. MyBean.myList)
isn't good enough for the enhanced EL syntax, nor for
Ah, OK, thats the EL enhancement, I had seen it, just didn't realize that was
what it was called.
My only problem with the el enhancements is using it in pages.xml since in
order to refer to it as an outcome, you need to include the whole expression,
including the variable name i.e.
What is this El Enhancement that you speak of?
When you say page parameters, I assume you mean passing the Id of the object to
be edited from the search page to the edit page as a parameter of the URL..i.e.
editperson.xhtml?PersonId=123 ?
I've been thinking about the issue of moving objects
Does your dataList have the @DataModel annotation?
I believe this is required in order to allow things to be passed around
properly, at least from my experience when I had a similar problem with null
objects being passed in.
In your class for the ricercaMenu bean, you should have something
First off, thank you all for the replies.
Gavin, the release of RHDS may take months, but that isn't a problem. This
project is in-house and will be in production for the next decade so it is
still worth it for us to aim for RHDS as the tool to use long term.
While the Seam-Gen route is
We are starting a new EJB project in Seam, and are wondering what type of
project to use. Given the Exadel announcement we anticipate using Exadel
initially until the formal release of RHDS as opposed to Netbeans. We felt that
the final incarnation of Exadel studio as RHDS would be more in tune
Try and open up the ant build file in Eclipse and use the deploy target.
I don't believe you can associate these projects with a server in Eclipse and
use the publish functions, it needs to be ant driven.
I use Netbeans so this is at best a guess.
Alternatively, just use the command line, open
95 matches
Mail list logo
