[jboss-user] [JBoss Seam] - Re: is an upgrade guide available for Seam?
I'd use the latest version of Seam and seam-gen to generate a new seam project, then migrate src and resource files. In the future you should be able to then update the seam-gen generate project when new versions of seam come out, as seam-gen has an update capability for automatic update conversion. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4040096#4040096 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4040096 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Being redirected to the same page
Put an h:messages on your page. Skipping DOB is likely causing a conversion error, which returns you to the same page. But since you aren't displaying any error messages it can be a little confusing. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4040223#4040223 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4040223 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: is an upgrade guide available for Seam?
I agree, an upgrade guide from release to release would be useful. However I doubt you'll get an upgrade guide that describes how to upgrade apps based on examples. I think your approach of taking the new hibernate2 example as a base and then patching in your code/config is the way to go here. All that said, I wouldn't be surprised if any new update guide made references to seam-gen as it's a nice automated way to go. Later versions have a number of project types and deployment options. If your particular hibernate2 style project isn't yet able to be bootstrapped with seam-gen I'd submit an improvement JIRA for someone to take a look at supporting it in the future. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4040228#4040228 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4040228 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Being redirected to the same page
Can't wait for JB AS 4.2.GA. :) View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4040230#4040230 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4040230 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Interceptor Question
What Interceptors class are you importing, the Seam or EJB 3? The EJB 3 annotation needs to be run within an EJB 3 context. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4040240#4040240 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4040240 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: question : avoid conversation id parameter for RESTful a
Why do you need to get rid of this cid param? I wouldn't think that RESTful apps would care about it. The server shouldn't mind its absence, it's likely just a temporary conversation that is being exposed by the conversation filter. I suppose you could remove that filter, but again, why would you want to? View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4040242#4040242 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4040242 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Interceptor Question
So naturally this | @Printout | public String register(.) | . | method is part of an EJB 3 session bean right? View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4040259#4040259 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4040259 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Tomahawk
If they say yes, remember you'll still need a tomahawk.taglib.xml file for Facelets. You can find one on the Facelets home page. I'm using MyFaces 1.1.5, Tomahawk 1.1.5 and the Tomahawk treeTable with Seam 1.2.1.GA. This setup works. Please report back if the MyFaces guys say there are problems with the 1.2 RI, that would be an unfortunate gotcha. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4040329#4040329 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4040329 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Out of Memory Leaks
Try using JRocket. Permgen issues are tricky and are a real problem for apps like yours that load and reload a zillion classes. Someone else can probably go into the details but JBoss isn't alone, for a quick fix grab the latest R27.2 JRocket release. JRocket handles permgen differently than Sun's JVM. No settings to tweak and generally no permgen problems either. Be sure and grab the latest, I had problems with the prior version. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4039729#4039729 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4039729 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Obtaining a handle to a EntityHome object
EntityHome was designed to be able to be used by JSF CRUD pages without needing additional java code. That said, it's generally preferred to access Seam components via @In than Component.getInstance(). View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4039895#4039895 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4039895 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Initialization code
You might be able to use an observer on a seam contextual event. Unfortunately I don't see a seam fully initialized event. Maybe postCreate, or if your app requires authentication, preAuthenticate. I'm just looking at the docs, there may be additional events that have been added. It shouldn't be hard to add that fully initialized event so other components can kick off startup tasks without worrying about what resources are available and what aren't. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4039934#4039934 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4039934 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Initialization code
Hmm, PMs don't seem to be activated. Anyway, please take a look at the placing of the Events.instance().raiseEvent(org.jboss.seam.postInitialization); line. I'm guessing that this should come at the end of the method, or at least after the Lifecycle.endInitialization(); since endInitialization resets all the contexts. After the done initializing seam logging seems appropriate since once the event is raised Seam will synchronously execute any observers which may have logging of their own. All of this should happen after seam has finish initializing. Sry for the forum post. Didn't know of a better way to send this. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4039981#4039981 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4039981 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: HowTo: When going to a page to enter data, pull from db
[EMAIL PROTECTED] wrote : I prefer exactly the opposite, with a Search conversation scoped component that holds my prototype entity during the search conversation. Gives me a lot of control over what the user can select on the search screen and how I handle this in the backend: I really like your search controller. I especially wish Seam's generic DAO (or maybe Query) construct came with *ByExample() methods. The problem I usually face, and maybe search is a bad example, is the necessary reuse of the entities in other controllers. Lets take profile or preferences. Maybe our users are able to set the default number of entries per page in some profile entity. We could have a ProfileController.profileEntity type system (ok, an EntityHome would probably work well here, whatever just an example). But then what if you want to access some profileEntity properties in your UserSearchController. In the past there was value binding expression ugliness and you had to couple your ProfileController to your UserSearchController because it was the accessor. Seam allows me to avoid all of that baggage. Unfortunately, I seem to get bitten by this regularly. It seems like no sooner do I define a UserSearch like yours, than a PM wants to reuse the entity used in this search in some other area of the application (without re-entering the data of course). This is why I generally prefer to separate my entity creation logic from my entity manipulation and business logic. I still love the UserSearch example, I'd just pass in the exampleUser along with the other values. On the flip side, I'd love to learn something new. If I could be achieving my goals in a better way, please set me straight. What my original post was trying to get at was that regardless of whether exampleUser is passed in or is part of the UserSearch component, the exampleUser is not retrieved via a call to UserHome.instance. Where UserHome is created for the sole purpose of providing the exampleUser. This is what I think the original thread creator was doing, and I think we can both advise against using EntityHome in such a way. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4039658#4039658 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4039658 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Disable butons till the screen renders
You might be able to set the default Facelet or JSP flush size to something large enough to keep everything in memory until your entire paged had finished rendering. However you apparently have large pages that take a long time to render, so it's probably not desirable to do this. If you're able to reproduce the problem, and it sounds like you can, you might want post it here or in JIRA. Someone may find a way of at least preventing Seam from crashing. Or you could take a look at the exception type, and supply custom navigation to an error page asking your impatient users to allow the page to fully render before they start clicking on stuff. :) View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4039659#4039659 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4039659 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: HowTo: When going to a page to enter data, pull from db
It's late, but I'll give this a go. Christian or Pete feel free to jump in.
It sounds like your mixing your retrieval and persistence mechanisms.
@Factory - Method called when a JSF page tries to reference a contextual
variable that doesn't exist, but has a named factory method. So if #{activity}
isn't found and there is a @Factory method, the method will be called and the
contextual variable populated. The variable will have the scope defined by
@Factory or if absent, the scope of the enclosing component. @Factory is only
called if the contextual variable is null (needs to be created).
@Unwrap - Method called on a component that allows the component to manage the
creation of a contextual variable. So Component ActivityManager might have an
@Unwrap method that puts an Activity into scope referenceable by the EL
#{activity}. This method will be called every time the #{activity} variable is
referenced or injected into a bean. Because the @Unwrap annotation is on a
method within a Seam Component, the component can take advantage of the entire
Seam life cycle, including providing tear down logic.
EntityHome - These are classes the provide generic DAO capabilities to objects.
By using an EntityHome you can Create, Update, Delete a single entity via its
primary key. In order to Update or Delete with an EntityHome you must pass the
ID of the object to the EntityHome prior to calling update or remove.
EJB3 Entity Beans - Seam components that are EJB3 Entity Beans are
automatically registered as event scoped components. They have an implicit
auto-create when used with JSF pages. So you could @Name(activity) your
Activity EJB3 entity bean. And reference it in your JSF page as #{activity}.
Seam will call the default constructor and you'll be able to use EL to set
values and can inject @In(activity) into the controller that deals with the
form action. Beans can have multiple names, and multiple scopes. Read more
about the @Role/@Roles annotation for more information.
The Seam documentation covers these concepts in greater detail.
If all you want to do is supply simple CRUD operations, then you can use an
EntityHome. By using an EntityHome it becomes your controller (action method),
and thus you don't have to write one. EntityHome can be configured with
FacesMessages to notify your users that CRUD operations have completed.
Remember that in order to use EntityHome for update and remove you need to pass
in an id. The developer guide shows how.
Based on the description you can decide whether @Factory or @Unwrap are best
suited for your needs.
Also, by default JSF will populate an unfilled form with empty values, not
null. So if you're trying to populate your #{activity} entity, have a blank
form and hit submit. Your controller will be injected with a live object with
the form values set to their empty state (empty Strings, 0 ints, etc). If you
want these values to be null instead you'll need to write a custom converter.
I've written a simple one below. Use the converter method or the f:converter
tag. The version of MyFaces that ships with JBoss 4.0.5 doesn't seem to want
to let you override the default String converter, so you'll need to specify the
converter on every input component you'd like it on. This might change on the
1.2 RI, I've heard different things about the RI in the 4.2 CVS tree.
@Name(emptytonull)
| @org.jboss.seam.annotations.jsf.Converter(forClass=String.class)
| public class EmptyStringToNullConverter implements Converter, Serializable
| {
| public Object getAsObject(FacesContext arg0, UIComponent arg1, String
arg2) throws ConverterException
| {
| return arg2 == null || arg2.isEmpty() ? null : arg2;
| }
|
| public String getAsString(FacesContext arg0, UIComponent arg1, Object
arg2) throws ConverterException
| {
| return arg2 == null ? : arg2.toString();
| }
| }
Hope this helps. I'm going to crash now.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4039504#4039504
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4039504
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: HowTo: When going to a page to enter data, pull from db
Re EJB3 Entities:
anonymous wrote : Not quite, they are only components if the have @Name (in
which case they would be CONVERSATION scoped). The preferred way to do this
is to use Home objects to manage an Entity, rather than expose it directly with
@Name, and uses pages.xml for wiring. We could probably do with an example app
built using Seam-gen that does a couple of simple CRUD operations
Yep, it was late, I forgot I overrode the scope on some of my entities.
However there are plenty of times where simple CRUD doesn't fit the bill. If
you're actually managing an entity, sure, use a Home. However if you're using
a form to populate an entity for another purpose, using Seam to populate a
scoped entity and hand it off for further processing has advantages. Of course
the entity doesn't need to be an EJB 3 entity. Seam does the same for POJOs.
For example I don't think I'd recommend using a Home to populate a search
prototype. For search pages, an entity with an event scoped role combined with
Hibernate's Criteria API + Example criterion is great.
In general if I'm not doing CRUD I prefer to decouple the entity population and
the controller doing the work. Prior to Seam I had to populate
#{someController.entity.value1}. Now that I can simply work with
#{entity.value1} means I have some additional flexibility.
What would be really great would be to put out a Seam cookbook. About @Unwrap,
Pete is right, most people just want a contextual variable to go from void (not
there), to initialized, and that's usually the job for @Factory. However the
managed component pattern can be useful not just for scafolding and exposing
non-Seam services. For an example you could have a managed component observe
many events that happen within your system and change the underlying
representation as a result of those observations. With the managed component
pattern a component can manage these actions itself and because the component
is unwrapped on every access, all callers will have a consistent view. This is
a much different use than what Factories provide for.
I wasn't sure exactly what the user wanted so figured I'd lay out everything
and let him choose.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4039566#4039566
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4039566
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: HowTo: When going to a page to enter data, pull from db
anonymous wrote : hey you live in san mateo near by to where i live dublin/pleasanton :) Small world. Maybe I'll see ya at the Seam JavaOne get together. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4039567#4039567 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4039567 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Login Best Practices
My apps simply have their own secure login pages so I don't have a best practice, but I'll help hash something out. I suppose my first question is. Are you using Facelets? My knee jerk solution to this would be to write a simple my:loginForm tag with Facelets that used a regular html form and an https action URI. The action URI can be backed by a servlet that would get everything sorted. When it's all said and done you end up being redirected to your app's home jsf page with a new secure session and populated identity. Sure it would be nice if some nice jsf framework provider did all the work for you. Fortunately I don't think it's that much work and should fit the requirements. I'm sure Seam will eventually get there, they just need to step back and think about the problem. I think they've been burnt rushing into things in the past. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4039573#4039573 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4039573 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: HowTo: When going to a page to enter data, pull from db
Borrow whatever you like Pete. Anything for the cause. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4039575#4039575 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4039575 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: HowTo: When going to a page to enter data, pull from db
One down side to using EntityHome for generic crud is lack of built in security. One needs to be careful when using Homes for crud operations that allow or require RequestParameters. You need to ensure the operation on this ID is valid. You don't want to expose information you shouldn't and you definitely don't want to modify or destroy information you shouldn't. For example, you don't want a user to update or delete another user's entity just by changing an ID in the URL and hitting return. Seam supports entity level security and you can probably extend a Home to double check access restrictions prior to operations. Likewise, you don't want private information available on lets say a user profile screen, to be available to anyone able to modify a URL. My concern is that new Seam users may over use this feature and run into these problems down the road. Or that they won't bother to learn how entity level security works or how to configure it. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4039576#4039576 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4039576 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: HowTo: When going to a page to enter data, pull from db
Take a look at the documentation on Factory and manager components. They will help you do what you want. Also the blog and messages examples show how you can initialize a contextual variable with DB data when a page is viewed. The messages example makes use of a DataTable binder, but you can use @Factory for anything, not just DataTables. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4039387#4039387 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4039387 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: HowTo: When going to a page to enter data, pull from db
I like to keep my entities clean. Just get/set/toString/equals/hashcode. So I'd put the @Factory on a method in your controller/action/manager Bean. If you need some heavyweight resources that you'd like to clean up, you can use the manager pattern and the @Unwrap annotation. In the case of the manager pattern you have an additional bean dedicated to managing this contextual variable. For the most part though, if I'm simply going to initialize a variable that I'll use later within a controller's action method, putting the @Factory on a method within the controller is the way I go. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4039403#4039403 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4039403 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: HowTo: When going to a page to enter data, pull from db
...and on scope, go as narrow as possible while still being functional. :) View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4039405#4039405 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4039405 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Seam Framework EntityQuery restrictions does not work fo
If that's correct, then great. I'm wrong and everything is safe. I've been
cleaning out a lot of select ... where name like +name+% from a codebase I
inherited. So I may just have been spooked by seeing #{expression} + %.
That said, I don't recall reading anywhere that Seam does what you describe.
Seam inlines these EL expressions elsewhere in components.xml.
component class=com.helloworld.Hello name=hello
| property name=name#{user.name}/property
| /component
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4038231#4038231
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4038231
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Seam Framework EntityQuery restrictions does not work fo
I guess I'm just expecting the values to be run through Seam's interpolator, which just does a string replace. I don't expect that Seam will generate a prepared statement, replace the EL with bind variables, etc. If it does, more power to Gavin. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4038239#4038239 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4038239 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Seam Framework EntityQuery restrictions does not work fo
Yep, +1 Seam crew. I should have known better. :) View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4038452#4038452 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4038452 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Query caching with Seam
The framework schema seems to support the following form. framework:entity-query |framework:hints | key/keyvalue/value |/framework:hints | /framework:entity-query View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4038616#4038616 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4038616 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Framework: Counting query entities
Looks like a problem to me. As a work around try something like:
@Name(myQuery)
| public class MyQuery extends EntityQuery
| {
| protected String getCountEjbql()
| {
| return select count(*) without fetch;
| }
|
| public String getEjbql()
| {
| return original query;
| }
| }
|
Not as great as the components.xml solution, but should keep you functioning
until this is sorted out.
Oh what the heck, you should be able to smack things around a bit. Maybe even
even include some components.xml like this.
component name=someQuery auto-create=true class=x.y.MyQuery
|property name=countEjbqlselect count(*) no fetch/property
|property name=ejbqloriginal/property
| /component
|
| component name=OtherQuery auto-create=true class=x.y.MyQuery
|property name=countEjbql/property
|property name=ejbql/property
| /component
not sure if the countEjbql stuff has a public setter might need to add one. I
guess in the end you have something like:
public class PersonQuery extends EntityQuery
| {
| private String countEjbql;
|
| protected String getCountEjbql()
| {
| return countEjbql;
| }
|
| public void setCountEjbql(String query)
| {
| countEjbql = query;
| }
| }
I haven't tried any of this, but it sounds about right to me. Let me know.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4037844#4037844
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4037844
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Framework: Counting query entities
Oops, PersonQuery class in the last code block should be MyQuery. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4037846#4037846 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4037846 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: inconsistent behaviour
Doing a lot of hot deploy? I usually find when things are screwy like this there's a permgen memory error at the very bottom of that stack trace. A restart of the app server causes the problem to go away. I've recently migrated to JRocket R27.2 and haven't had any trouble so far. JRocket does a much better job than Sun's JVM with permgen clean up. Bascially I think they put it on the heap and clean up normally. If you do try JRocket, go with only R27.2, R27.1 had a ton of problems. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4038031#4038031 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4038031 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Framework: Counting query entities
Lol, should really not drink and make forum posts. :) A combination of dsmith's solution and my components.xml should give you what you're looking for. You only need 1 small class that you reuse in components.xml. You could even write your own namespace and have your own myframework:entity-query tag. But that's probably overkill, the component... syntax isn't that verbose. Although I haven't tried it, you may even be able to use the class attribute on framework:entity-query to tell Seam to use your EntityQuery subclass. If so, great. You have plenty of options. Based on the HQL, you'd think that Hibernate should be able to look at any digested query that has a single return and determine the correct count() syntax. Even eliminate unnecessary joins like the one you have here. Given how frequently this is used I think this would be a great convenience feature, especially for folks that use the Criteria APIs. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4038001#4038001 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4038001 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Switch from DEV to PROD
Try creating a build.properties file next to build.xml and include profile = prod View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4038003#4038003 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4038003 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Switch from DEV to PROD
or simply pass as a command line arg to ant View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4038004#4038004 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4038004 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Seam Framework EntityQuery restrictions does not work fo
exception? View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4038020#4038020 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4038020 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: DataModel in two SFSB issues
In Bean B try sharing with @In @Out DataModel sections; If you're trying to manipulate the DataModel in B. Otherwise your investigation seems to show that Seam isolates the @DataModel data binding on a per bean basis. Not sure why. Gavin is around here somewhere, try adding a post to the Back... thread. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4038036#4038036 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4038036 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: easy alternatives to ui:repeat and c:forEach for Seam 1.
ui:repeat is the preferred way to go. If you're having problems with it I'd try and resolve the issue on the facelets mailing list. Or you could try an alternate implementation. I believe that RichFaces has a repeat tag of their own as well. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4038018#4038018 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4038018 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: DataModel in two SFSB issues
anonymous wrote : ...it doesn't do a subsequent injection Really? Although I only outject in my code, I thought DataBinders performed bidirectional binding. Why else implement a getWrappedData() DataBinder method? View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4038046#4038046 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4038046 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Seam Conversation Should Be Flexible but NOT
So you're asking for something like @Begin(timeout=ms)? View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4038097#4038097 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4038097 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Seam Framework EntityQuery restrictions does not work fo
This just seems begging for a SQL injection problem. Be careful when using this feature. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4038215#4038215 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4038215 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: EntityNotFoundException when performing EntityManager.re
This is really a Hibernate/JPA question, you might get more help from that forum. What I'd expect is happening is that due to your cascade level, refresh is attempting to refresh the database state of your detail entities. Since they don't exist, you get an error. Perhaps you should enumerate the cascade options you want, and leave out refresh on your detail association. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4037659#4037659 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4037659 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Manual Flush Mode for Removing detail records
You appear to be using an EJB3 SFSB and a JPA extended persistence context. Only Hibernate supports a manual flush mode. What I'd assume is happening here is that your @Begin(flushMode=...) declaration is being ignored and that EJB3 is defaulting to its standard transaction/flush demarcation. Instead of using a JPA extended persistence context, try using a Seam managed persistence context instead. Either that or use the em.getDelegate() method, perform operations on a Hibernate Session, and manage the flushmode and flushing within your application. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4037664#4037664 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4037664 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Validation messages
Take a look at the message attribute of the Hibernate Validator annotations, they allow per field overrides of the default message. NotNull is still handled by JSF's required=true mechanism, but you have greater flexibility for other field constraints. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4037111#4037111 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4037111 ___ jboss-user mailing list [EMAIL PROTECTED] https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Validation messages
Yep. It makes sense, it would be nice if you could override the validation message at the s:validate level. This has long been a complaint of JSF, and one that I believe will be fixed in JSF 2.0. JBoss will start using the 1.2 RI in 4.2, and that may allow some jsf-ext work to be used, including maybe support for what you're looking for. Until then, ask Gavin real nice for a s:validate message=my message feature. Note though that NotNull is a special case in JSF. I believe that JSF will always handle required fields via its required=true mechanism so NotNull isn't a great example of using Hibernate Validator. Also, Seam provides EL and context aware markup in JSF resource bundles. I don't know if it extends this capability to Hibernate Validator resource bundles, I'd assume not. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4037127#4037127 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4037127 ___ jboss-user mailing list [EMAIL PROTECTED] https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: core:managed-persistence-context question
The is the typical @In vs @PersistenceContext question. The answer is summed up nicely in this thread. http://jboss.com/index.html?module=bbop=viewtopict=106019 Basically to answer your questions: 1. What the core:... is doing for you is configuring a Seam managed persistence context. You take advantage of this by using the Seam managed context instead of the EJB3 managed context. 2. How do I do that? Use the @In annotation. The Seam managed context is a Seam component exposed via Seam's bijection mechanism so use the @In annotation to get it. 3. So how are they different? See Christian's answer in the link above, or read my answer here. First, the following link has a good description of Seam and ORM. http://docs.jboss.com/seam/1.2.1.GA/reference/en/html/persistence.html Use the link to familiarize yourself with the benefits of the EJB3 extended PersistenceContext. The difference between the Seam PC and the EJB3 PC is that Seam provides a couple of features that EJB3 doesn't, otherwise in terms of APIs they're the same. 1. The lifecycle of the EJB3 PC is bound to a Stateful Session Bean, and is only shared between components participating in the same transaction. The Seam PC has conversation scope and can be injected into any component participating in that conversation regardless of its transaction context. 2. Seam PC has better clustering and caching abilities. See the Seam doc link above for reasons why. 3. Seam PC is managed by Seam not EJB3, thus it can be used within non EJB3 Seam components. So you can still benefit from a standard JPA interface while allowing Seam to manage the PC and transactions for you, all outside of EJB3. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4037241#4037241 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4037241 ___ jboss-user mailing list [EMAIL PROTECTED] https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: @Convert and overriding standard types
Hmm, what I was seeing on JBoss 4.0.5, which should be MyFaces on JSF 1.1, is that my converter wasn't being called at all in either direction when I tried to override forClass=String.class. What I've written is a quick converter to translate empty Strings into null. This makes my DB happier (as well as my equals()). Currently when I take input from a form and don't populate fields, they become empty strings. I'm trying to replace that default semantic with my Seam @Convert converter. Works great if I specify a f:converter everywhere, but that's kind of a drag. On the whole I still love being able to register a JSF converter with two annotations. Thanks Seam. PS: Perhaps this is an issue with MyFaces. As you say, the spec may not be clear. I'm looking forward to JBoss 4.2 and the 1.2 RI. (yea I know I could hack 4.0.5, but I'm not gunna :) View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4037247#4037247 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4037247 ___ jboss-user mailing list [EMAIL PROTECTED] https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Seam and 3rd party EJB
Double check that jndi-name with the pattern in components.properties. All of
my lookups are of the form #{ejbName}/local no domain.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4037278#4037278
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4037278
___
jboss-user mailing list
[EMAIL PROTECTED]
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - @Convert and overriding standard types
I've written a Seam component JSF Converter. It works great if I specify an f:converter tag on my input. However if I specify @org.jboss.seam.annotations.jsf.Converter(forClass=String.class) and leave off the f:converter, the converter isn't called even if there is a String value binding. Any tips? Is Seam not able to override the JSF defaults? I suppose forClass=Foo.class (no default converter) could be an intended usage patter, but figured I'd ask those in the know. I'm on Seam 1.2.1GA View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4036824#4036824 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4036824 ___ jboss-user mailing list [EMAIL PROTECTED] https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: I get a exception
anonymous wrote : Caused by: org.jboss.tm.JBossRollbackException: Unable to commit, tx=TransactionImpl:XidImpl[FormatI | d=257, GlobalId=kostja-mobil/468, BranchQual=, localId=468] status=STATUS_NO_TRANSACTION; - nested t | hrowable: (javax.persistence.EntityNotFoundException: deleted entity passed to persist: [kk.rentform | .entity.Kfz#]) | I'd start looking here. Make sure you aren't trying to persist null or an object that has been removed. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4036840#4036840 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4036840 ___ jboss-user mailing list [EMAIL PROTECTED] https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: I get a exception
How about the second part? Have you done something like this? 1. Lookup entity. 2. Remove entity. 3. Try and persist removed managed entity. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4036844#4036844 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4036844 ___ jboss-user mailing list [EMAIL PROTECTED] https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: I get a exception
anonymous wrote : 1. Lookup entity. | 2. Remove entity. | 3. Try and persist removed managed entity. The above is what not to do. So if you're doing that, that's likely your problem. Sry, your code is just too long to sift through. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4036849#4036849 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4036849 ___ jboss-user mailing list [EMAIL PROTECTED] https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: I get a exception
In this case you never try and re-persist kfz1. If you did you'd probably get the same error here as well. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4036875#4036875 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4036875 ___ jboss-user mailing list [EMAIL PROTECTED] https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Back...
Question regarding the semantics of @Convert(forClass=...) http://www.jboss.com/index.html?module=bbop=viewtopict=106354 View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4036880#4036880 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4036880 ___ jboss-user mailing list [EMAIL PROTECTED] https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: JavaOne
Up for drinks +1. Do you really want everyone to E-mail? Easier filing system than forum? View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4036882#4036882 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4036882 ___ jboss-user mailing list [EMAIL PROTECTED] https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: JavaOne
Same here Rob. It shouldn't be a problem though, there are plenty of hotels and bars nearby as well as good cab service. I'm not even sure Moscone allows alcohol. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4036910#4036910 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4036910 ___ jboss-user mailing list [EMAIL PROTECTED] https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Request Parameter not found
@RequestParameter is for HTTP request params. http://host/page.jsf?username=Steve @RequestParameter(username) String username; assert username == Steve I'd guess the problem here is that you don't actually have a request parameter with this data or that Seam has no idea how translate from this string (how did you generate the string?) into an X509Certificate[]. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3974630#3974630 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3974630 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Using the @Factory annotation and stateless session bean
anonymous wrote : I assumed that because the init method has been annotated
with a Factory annotation and the testVar component is initially null - that
this would cause the init method (i.e. method annotated with the Factory
annotation) to be invoked whenever one invokes any business method in the
stateless session bean (in this case, testSLSBMethod in TestSLSBBean stateless
session bean).
This is your mistake. Factory methods are only called when something looks for
testVar in a Seam context and it isn't already there. So if your JSF page
tried to display #{testVar} or another componented tried a
@In(value=testVar), etc. Simply referencing the instance variable testVar in
a method won't get the job done. The difference is between the notion of an
instance variable and a *context* variable.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3973803#3973803
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3973803
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Using the @Factory annotation and stateless session bean
The difference between @Factory and @Unwrap is that @Unwrap only works on components. @Factory can work on contextual variables as well, like the String example given. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3973923#3973923 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3973923 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Automatic Entity merge
anonymous wrote : One alternative approach is instead of passing the entity object around, just pass the id in a request parameter and use something like the ManagedEntity component (in Seam CVS) to auto-load the entity instance and expose it via a context variable. Since request parameters can be easily manipulated by a malicious user, this seems like a pretty dangerous general approach to me. When you're searching a blog or providing REST services, this works great. For a general CRUD framework this worries me. For example, I wouldn't want my bank's online add joint account member conversation to take in currentUserId and newJointUserId as a request params. Of course, I haven't seen this thing in action, maybe there are safeguards in place to detect manipulation of these params. Please assuage my fears. :) View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3974032#3974032 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3974032 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: org.jboss.seam.jsf.SeamNavigationHandler is no javax.fac
I'm pretty sure this is a classloader issue. I think there's a Seam FAQ out somewhere that addresses this. I'm on the run, but poke around a little more. I'm pretty sure this has been answered. JBoss has a number of classloader options, it also ships with a JSF implementation so your inclusion of MyFaces shouldn't be necessary. * Try removing MyFaces from your deployable. * Try removing MyFaces from it's default location within JBoss. * Change the classloader params for JBoss to provide the isolation level you require. * Wait for further help, sry I only have 30sec for this message. :) View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3974034#3974034 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3974034 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: JSTL tags ignored
I'm pretty sure we were both using JSTL correctly, but had the wrong namespace. If you don't specify the proper namespace facelets will happily just spit out your tag as text instead of performing the appropriate taglib processing. This is the problem we both had, and it's solved by using the above namespace. That's not to say that other problems with EL, JSTL and Faclets aren't possible. I just don't think we experienced them here. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3973698#3973698 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3973698 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Blocking direct access to .xhtml files
Writing a filter that blocks direct .xhtml access shouldn't be too hard. I wouldn't expect facelets to perform a web request to access the .xhtml files, so you should be able to 404 any direct HTTP access. I'm not 100%, but this should be easy enough to test. Either just write the filter, or look at the HTTP request log during expected usage. Even if facelets makes a web request for some reason, it should come from localhost or your local IP. You can adjust your filter to permit that access. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3973153#3973153 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3973153 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Blocking direct access to .xhtml files
You could also try setting your Faces Servlet to match on *.xhtml instead of *.seam. I'm not sure if that causes a problem or not. I wish I were closer to a dev environment. These are all quick tests. For some reason I thought that facelets was still like JSP in that if you screw up and don't go through the JSF servlet things will crash. Not pretty, but secure. I also tend to use a JSP 2.0 jspx like syntax with my facelet pages to get tag JSF completion. That also helps things explode rather than render if someone attempts to access the .jspx file directly. Let me know what you find. If nothing works, I should be more helpful tomorrow. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3973160#3973160 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3973160 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Seam magic on non-seam-components?
You can also define components, including JavaBeans, in components.xml. If you define them here, you don't need the @Name annotation. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3973104#3973104 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3973104 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: how to stop unknown user from seeing a page
You could also look into using a dedicated security framework like Acegi that would have richer options. http://acegisecurity.org/ View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3973152#3973152 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3973152 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: @SelectItems and @SelectItemsSelection annotations?
This is the expected behaviour. The @SelectItems annotation applies a data
binder and outjects the wrapped object as a contextual variable (regions).
Direct access to the method selector.getRegions() will return the method's
original values. Useful for calling the method from other components or JSF
backing beans. Getting a List of SelectItems wouldn't be right in that case.
As with most things in Seam bijection happens to and from a Seam context. Seam
adds a variable resolver so that JSF can find things stored in these contexts.
However it doesn't prevent you from calling things via the JSF std way, getting
JSF std results/objects back.
If you did want JSF to intercept and apply conversion to #{selector.regions}
you might be able to call the data binder directly within your custom
converter. I think the method that does the conversion might be private, but I
could change that if you think this code could be reused elsewhere. Otherwise,
just remember that #{regions} gets a contextual variable from a Seam context
and #{selector.regions} calls a method on #{selector}
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3972639#3972639
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3972639
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Please help: cannot integrate ICEfaces into Seam applica
home.iface doesn't appear to be handled by the Faces Servlet. Have you tried home.seam? View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3972767#3972767 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3972767 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: When a component is not found should Seam warn or fail?
The thing about this is that null or not found is a valid use case. Many ppl have pages that rely on this functionality to not display something when a variable isn't in context and then to come alive once an action puts this variable into context. In this case you wouldn't want a log message every time, and it's impossible for Seam to know if you're doing this on purpose or by mistake. In practice, with incremental page design and testing, typos are found quickly and are easily fixed. However, given the amount of typo errors we see on the forums, maybe step #1 if you're having a problem would be to double check your spelling. Yea, it's easy to do, but how can Seam really help with that aside from the debug output already provided? An option to promote this debug output to warn in web.xml or seam.properties? View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3972770#3972770 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3972770 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Questions on Seam's PAGE scope
Thanks Pete. This clears things up for me. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3971143#3971143 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3971143 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Interface from C app to Seam?
What I figured. Thanks. Any plans to publish a protocol spec? View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3970660#3970660 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3970660 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Drop Down Menu Using Seam and Facelets
Take a look at the Seam wiki. There are a couple third-party selectItems DataBinders there. These will let you take a list returned from your DB and use it within your JSF menu. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3970806#3970806 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3970806 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Scope/Context feedback
Take a look at the RESTful section in the documentation and the blog example for tips on your mostly stateless apps. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3970807#3970807 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3970807 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Scope/Context feedback
The given Seam examples and documentation isn't PhD work, or even that complex. It does try and provide a complete example (non-trivial) and it does assume a certain foundation. In the case of your team, can I suggest some training. At least on JSF and Hibernate/JPA and then sprinkle in some EJB3 and Seam if available. I believe that JBoss offers training on all of these technologes. I have also had great experience with training from ArcMind. You should be able to get up to speed in about a week. The development team at my organization made a previous technology leap to the one you're making, and let me say that a week of on-site training (available for around $10-15k depending on size) was money very well spent. From there I'd start learning how Seam improves upon what's currently available in the JSF/EJB3/JPA technology stack. You'll see that @Factory and @Unwrap are not magic. And you'll see how Seam can allow for a tremendious line of code reduction vs alternative best practice uses of JSF/EJB3/JPA. In the end this should allow for much easier code readability and smaller modules. Which all equals fewer calls on vacation. I and others are always willing to help here on the forums, but to get the most of out what we're saying about Seam I think training in other areas would go a long way. At the very least you'd no longer be trying to learn 5 things at once, and could focus on doing Seam well. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3970835#3970835 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3970835 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Scope/Context feedback
Agreed, docs can always be better. Although as far as OS projects go, these are pretty good. I did a quick search for PAGE scope and found that the issues example uses it. In particular the ProjectFinderBean. The usage and design pattern seem to fit my guess from a previous post. PAGE scope allows stateless controllers to outject and manipulate data relavant to a specific page (in this case a project search screen or something) across multiple requests. If this use case or Seam doemo doesn't work for you, start a new problem specific thread. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3970842#3970842 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3970842 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Questions on Seam's PAGE scope
It isn't clear how page scoped resources are cleaned up. They appear to survive multiple requests, however can be out of date and require a refresh() as indicated in the issues example ProjectFinderBean class. Is it possible to set a page scope timout so that resources can be cleaned up in addition to providing a way to schedule data refreshes without user interaction? The docs seem to imply that page scoped state is serialized back to the client, so maybe no data is being stored on the server. This might aliviate memory related issues, but having a declarative way to time out this page cache would seem beneficial. Am I missing a configuration option? An example use case might be a stock quote. A company may have an investors page that uses a third-party web service to lookup the company's stock price every 5 minutes. This request should only be made once every 5 minutes, users shouldn't be able to refresh, and it should be easy to implement. Seam + page scope + @Factory seems ideal here. If you can time out the data that is. After the time out, the factory method would be called again, and round you go. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3970848#3970848 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3970848 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: TROUBLE RUNNING BOOKING EXAMPLE ON TOMCAT
If I recall the JNDI lookup for Tomcat/embedded EJB3 is different than regular JBoss. I don't have time right now for a full doc/forum search, but try that first. The root cause appears to be a naming problem. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3970639#3970639 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3970639 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: TROUBLE RUNNING BOOKING EXAMPLE ON TOMCAT
Also, make sure you've updated your Seam's build.properties and generated the example via deploy.tomcat? View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3970640#3970640 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3970640 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Interface from C app to Seam?
Not to knock the work done by the remoting team, but is there a reason a custom protocol was chosen vs a Seam RemotingEndpoint that would handle remoting via some version of SOAP? I would have a thought the benefits of a standard transport protocol would outweigh the down side. Since obviously they did not, what are the benefits of this approach? View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3970642#3970642 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3970642 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Long Running Conversation Timeouts are never occuring
This way idle conversations are timed out, yet the conversation that you're currently in will last as long as your session lasts or until you finish the conversation. You don't want the foreground work you're currently doing to be ripped away from you. But you do want a way for the resources tied up by background conversations to be cleaned up. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3970432#3970432 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3970432 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Problem: Custom validate methods in EJBs crash
I agree with Gavin. I've always been ok with complex validation in the action method (or control flow). If you need something a little more declarative, it shouldn't be too hard to use Seam plus EJB interceptors to write your thin framework. If you think about it this is what JSF is doing anyway with its phased approach to conversion and validation. Being able to use EJB 3 allows you to slip in your own layer immediately preceeding action invocation. You'd then be able to apply any declarative application concerns, including validation, on objects that had already been converted and validated in isolation. Would it help if Seam provided a standard annotation that highlights this ability or should users just implement something like this on their own? I guess if this feature is being requested, giving the masses what they want may have some value, even if it's just providing a utility that they could provide themselves. Utility is a good thing. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3970169#3970169 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3970169 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: @Out frustration
@Out's scope defaults to the scope of the enclosing controller, in this case the SLSB. SLSB have a stateless scope. I think that Seam may actually promote the outjection of context variables of stateless components to event scope for you (but I'm not positive). Event scope is like JSP request scope and page scope is like JSP page scope. My guess is this example didn't work for you because you used navigation in your JSF action. If so, your view came in two requests. The first outjected the Bean, then left scope. Then you made the next request to view the page and saw everthing with their original values. I hope this clears up the scoping question. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3970175#3970175 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3970175 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Error RequiredException during finalize on @In component
Make sure there is a value for your @In tradeDetail.userPrincipal in scope. If not you'll get this error. Although I can't imagine you'd get this error while the GC is calling your finalize() method as this would happen outside of the JSF lifecycle and no bijection should be going on. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3970182#3970182 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3970182 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: @Out frustration
Well this is kind of core to bijection and contextual components. @Out is a general concept supported by all components over six searchable contexts. Where did you think your object was going? I'm not trying to be mean, rather trying to figure out where any new documentation should go. Is the misunderstanding about contextual components, or about the function of the @Out annotation? View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3970184#3970184 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3970184 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Problem: Custom validate methods in EJBs crash
And required checking happens outside of conversion/validation at yet another time. Unfortunately, JSF seems to be designed to support providing a consistent checked state through each phase of the lifecycle and short circuit phases if there are problems. This almost explicitly designs away your desire to collect all this information and display it at once. I don't see a JSF provided solution to this problem in 1.2 (Gavin has mucked more with the internals though, maybe he knows better). It seems to me the easiest solution would be to ditch JSF validation and simply validate yourself within the application. Use the framework or not, but don't fight it. There may be a way to reuse your existing validator classes and write a custom phase listener that would provide your own hooks to the validation phase, but then you'd be using your own validator framework and not JSFs (no UI component tie in). I just don't think JSF was designed to give you what you want. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3970191#3970191 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3970191 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Error RequiredException during finalize on @In component
Whoa. What are you trying to do in your finalizer? View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3970207#3970207 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3970207 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: @Out frustration
Well EVENT obviously won't work because state is destroyed at the end of the request, so it won't be available across redirects (which have 2 requests). PAGE on the other hand I'm not 100% sure about. I'll admit I don't use page scope. I was under the impression that this was like a mini-session tied to a given instance of a page. So if you had data that was specific to a single page, yet needed to save state across requests you could use page scope. A clickable list with data that changes due to other events on the back end is given as an example in the documentation. So in your case where you navigate back to the same view, I'd expect page scope to work. If you're sure it doesn't, then either I don't understand what page scope actually does, or there may be a bug in Seam. Page scope in this understanding would seem to leak memory like the session though, as there would be no way to clean up resources of an infrequently used page. In this case, a conversation may still be desirable even though page scope is available. Plus we know it works. :) It may be that I'm wrong and page scope may simply restrict event data to a given view. However if this were the case, I'd think page would be the narrowest context, and yet the docs say that event is. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3970211#3970211 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3970211 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: @Out frustration
Just curious. What JSF state saving technique are you using? If you change this to client, does page scope work? View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3970214#3970214 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3970214 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: @Out frustration
Well it just doesn't make sense for a stateless component to outject anything, because it wouldn't go anywhere. *IF* (I'm still not sure) Seam is nice and automatically outjects objects from stateless components into event scope, then the examples were likely written in a time where Seam didn't have this feature. If Seam doesn't have this feature, then scoping your session bean into event scope (making it an EVENT scoped component) saves you from having to explicitly scope your @Out annotation every time. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3970217#3970217 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3970217 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: @Out frustration
CptnKirk wrote : Well it just doesn't make sense for a stateless component to outject anything, because it wouldn't go anywhere. And this isn't strictly true either. There are a whole class of problems where you want to have a stateless component (like a SearchManager) to outject into another scope (possibly conversation). What I should have said is that it doesn't make any sense to outject into stateless scope. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3970218#3970218 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3970218 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: @Out frustration
My guess is the client vs server state saving problem is due to a bug in ealier versions of MyFaces that JBoss may still ship with. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3970220#3970220 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3970220 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: @Out frustration
...or maybe that was an earlier version of facelets (or both). Try upgrading those if you need server side state saving. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3970222#3970222 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3970222 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Can you merge multiple annotations in one?
Actually I'm pretty sure Java does have limited meta-annotation support. Look
at how Seam implements its DataBinding mechanism.
| @Target(ANNOTATION_TYPE)
| @Retention(RUNTIME)
| @Documented
| public @interface DataBinderClass
| {
|Class? extends DataBinder value();
| }
Then in whatever your databinder annotation is
| @Target({FIELD, METHOD})
| @Retention(RUNTIME)
| @Documented
| @DataBinderClass(SelectItemsBinder.class)
| public @interface SelectItems
| {...
Code that looks for @DataBinderClass annotated elements will also find elements
annotated with @SelectItems. This is all pretty static, so you won't have the
nice macro effect that you're looking for, but could have your own @SeamSLSB
annotation that encapsulates some boilerplate code (including imports). I
haven't tried this with any annotation other than @DataBinderClass, and it has
a @Target(ANNOTATION_TYPE). It's possible that other Seam annotations may also
work those with @Target(TYPE), it's possible things may fail. Good luck.
I hope this is useful.
-Jim
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3969607#3969607
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3969607
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Can you merge multiple annotations in one?
EJB 3 interceptors also make use of meta-annotations. http://docs.jboss.com/seam/1.0.0.GA/reference/en/html/concepts.html#d0e2635 View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3969611#3969611 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3969611 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: How the setect itens example works???
make sure you have a getter/setter and that if using EJBs that these methods are exposed via the local/remote interface. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3962944#3962944 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3962944 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Facelet and pageEncoding
Later versions of facelets default to UTF-8. If you want to change that I think you can specify the encoding parameter on the xml declaration. If that doesn't seem to work for you, you might want to ask the facelets mailing list. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3961643#3961643 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3961643 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: @Remote still shown as
This doesn't appear to be related to Seam. From this error it looks like you have different versions of your classes on your client and server. You also appear to be mixing RMI, EJB 2.x and EJB 3. I suggest using pure EJB 3 with Seam. Try looking at an EJB 3 tutorial and/or an EJB 3 book (free one here: http://www.theserverside.com/tt/books/wiley/masteringEJB3/index.tss). While you may eventually get EJB 3 to recognize this code due to the annotations, it's confusing to look at. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3961661#3961661 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3961661 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Outjection of previous value: selectOneMenu : One 2 Many
Your example is just too huge for most ppl on the form to walk through. Try reproducing your problem in a much smaller cut down. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3961354#3961354 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3961354 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: DataModel issue
I think the original post is conceptually wrong. ui:repeat is an iterator. It can iterate over lists of things, including DataModels. However it doesn't modify the model that is iterates over. For example it will never set a DataModel's selected row and using @DataModelSelection with it will never work. ui:repeat is a powerful substitue to using c:forEach. It is not a direct replacement for h:dataTable. Maybe I misunderstand the original question. If you need @DataModelSelection to work, you'll need to go back to h:dataTable. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3961410#3961410 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3961410 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Progress
An exception shouldn't implicitly kill the conversation. In fact you've proven that it doesn't. You might roll back a transaction on an exception, but conversations aren't the same as transactions and should survive your given use case (although if you wanted to, it wouldn't be hard to end a conversation when you navigate to your error page). View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3961437#3961437 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3961437 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: @OneToMany Question
This is really an EJB3/JPA question, not a Seam one. You may get better support if you post your question in that forum. It sounds like you want a ManyToMany relation. If Tasks can have many TaskItems and a TaskItem can be associated with more than one Task this is a ManyToMany relation, not a OneToMany. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3961445#3961445 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3961445 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Get ServletContext in Session Bean
How are you making this call? You'll only be able to lookup a Seam context after Seam has initialized and while you're within some web request. So calling this method via a startup servlet will probably fail. Calling this method via an EJB or MDB that is executed via a non-web request (ie executed directly via IIOP) will also probably fail. With few exceptions Seam only really works (has context) within the JSF lifecycle. It sounds like you may be trying to use it outside of this. Or you may simply have Seam misconfigured. I need more info please. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3961465#3961465 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3961465 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
