Ales,
So if I understand this correctly getMetaDataLocations for a WAR deployment
returns the WEB-INF folder, and the isModified method will check every child
within that folder? That does seem to be somewhat undesirable. I know that
there are a fair number of web frameworks that suggest
Cool. Off the top of my head, defaulting the filter to *.xml might be a good
compromise. It seems to me like that would encompass the JBoss config files,
standard JEE config files, and also web framework files that do necessitate a
restart (Seam's components.xml for instance) while excluding
Thank you Ales.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4179134#4179134
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4179134
___
jboss-user mailing list
I've recently started using the latest CR release of JBoss 5, and I've noticed
that my WAR file is often being reloaded when the web.xml file has not changed.
I'm assuming that this is a result of the deployment changes in 5.0, which I
believe are represented in the microcontainer. If so, can
Just to clarify, after watching a bit more closely, it seems like it is a
facelts template file (default.xhtml) located in WEB-INF/templates that changes
and triggers a reload. There are non-configuration files that I tend to keep
within WEB-INF just because they are not directly accessible
At the very least you've saved me a few hours more. Does anyone have a work
around for this that doesn't involve changing the state saving method? This
seems like a fairly large problem if it makes functions unusable with client
side saving, which I believe it does.
View the original post :
I think I see a potential problem. You are deploying EJBs so I'd imagine that
you are deploying them as an EAR file, but you specify your loader repository
in jboss-web.xml rather than jboss-app.xml. I don't think that will apply to
the EJBs if it's even picked up by JBoss at all. Without
It's not really a Seam feature. It comes down to an understanding of EJBs in
this case. If your bean had been a POJO, what you were trying to do would have
worked.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4077415#4077415
Reply to the post :
I think the most simple explanation is that event scope means that you're data
is stored in the request (servlet or portlet). It is available through the
request - response lifecycle. Page scoped data is stored in the faces tree so
if you were to create a page scoped object while a page was
You got it. As far as what you were saying before you should be able to
have a page scoped attribute remain set indefinitely as long as your action
method returns null, or match some other type of navigation rule that causes
the page to be re-rendered. I've never tried it, I'm not a big
Is there a reason why exceptions that occur during the invoke application phase
are handled by the ExceptionFilter rather than by an interceptor? I've
subclassed org.jboss.seam.core.Exceptions and registered some of my own
ExceptionHandlers to allow conditional redirects based on the viewId,
It looks to me like the container is having a problem retrieving your session
bean. When you @In(ject) a session bean Seam will retrieve it from JNDI. What
you are doing in your factory method is simply instantiating the class, which
will not have the Seam or EJB interceptors applied to it.
the jndi-pattern here:
core:init debug=true jndi-pattern=testPro/#{ejbName}/local/
says that your EJBs will be found in JNDI under a hierarchy starting with
testPro.
This line in your stack trace:
Caused by: javax.naming.NameNotFoundException: testPro not bound
seems to say that there is
By the way, I've added my own interceptor that delegates exception handling to
the Exceptions component and it seems to be doing the trick so far. Any chance
we could see something like that become one of the standard Seam Interceptors?
That coupled with an API for registering custom
Your field is of the wrong type. When you inject a session bean Seam looks it
up from JNDI and returns, not a MySessionBean object, but an actual session
bean that implements the MySessionBean_L interface.
View the original post :
To be honest, if I'm really the only person interested in the feature I can
live without it. Unless someone else feels like chiming in I can't see having
you devote the time to changing it.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4052244#4052244
Reply
I remember hearing that Gavin wasn't around when I posted this initially, I
don't know if he's back now but either way, does no one else have any interest?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4051481#4051481
Reply to the post :
First off, Gavin I wanted to say thanks for all the improvements to pages.xml
since 1.0. Even though my patch didn't make it in (JBSEAM-397), it's great to
see most of the functionality there. I do have a couple of questions about how
it's all been implemented though.
In my experience most
I'm a little lost on how this would be useful. Granted, I shunned EJB before
Seam and am definitely no expert, but wouldn't remote services generally be
used by your local EJB actions rather than resolved via EL within pages? I'm
pretty sure you can inject a remote EJB using the @EJB
What you want is:
| page view-id=whatever
| action execute=#{action1}/
| action execute=#{action2}/
| /page
|
You may need 1.2 for this. Check the DTD for other options.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4041468#4041468
Reply to
Check out @TransactionAttribute in the EJB3 spec.
http://trailblazer.demo.jboss.com/EJB3Trail/services/transaction/
If you're not using EJB3 Hibernate might have it's own transaction annotations
but I'm not aware of them.
View the original post :
anonymous wrote : I think I disagree, but perhaps I can kinda see where you are
coming from
Maybe if you can give me a use case where an action should still fire even
though an earlier action requested a view change we can come up with a
compromise. All the actions I've used have been
Ok, I'm working on this now. A few questions though:
I've got the latest CVS changes as of last night. Anything else I should know
about changes to the Pages component that you are working on locally or had in
mind?
What is the process for submitting patches?
View the original post :
That fixed it. Thanks.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3986922#3986922
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3986922
___
jboss-user mailing list
Ah, so there's no chance of getting a patch included before the release?
I've got another question after looking the code over more thoroughly. Is
there any reason to continue firing actions after the first non-null outcome?
It seems to me like a non-null outcome signals an immediate
Ok, well it's just about done anyway. Changes I've made are:
You can now specify page parameters, no conversation view ids, timeouts, and
resource bundles in wildcards. Page Parameters from all matches are combined
while the others will fall back to the value defined on the most specific
E-EJB3
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3985799#3985799
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3985799
___
jboss-user mailing list
jboss-user@lists.jboss.org
Huh, don't know where I got the capital E from, I thought I just cut and pasted
from the @Name. I'll give it a shot and let you know if it fixes the problem.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3985886#3985886
Reply to the post :
Ok. Well that's making it look increasingly like my problem is with when JBoss
initializes since you are using a POJO rather than a session bean. Has this
changed between versions?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3984567#3984567
Reply to the
A quick question about page parameters. As I understand it, they are available
so that conversational state can be reinitialized when the conversation no
longer exists, like when a page is accessed from a bookmark. If that's the
case, then shouldn't there be a way to override Seams default
I've got an idea for revamping pages.xml. What if Page objects had a parent
child relationship with each other, less specific matches parenting more
specific children. For attributes that can only have a single value
(no-conversation-id for instance) if the value isn't defined directly on the
http://wiki.jboss.org/wiki/Wiki.jsp?page=CVSRepository
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3984648#3984648
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3984648
___
You may want to try accessing the bean you pass into your template using the
#{editor[edit]} type notation instead. This is a shot in the dark because I
haven't tried it but I've seen it suggested for this type of use elsewhere.
I figured I'd also point out that your outdated list issue can be
It does seem that we aren't quite understanding each other. Let me clarify a
few points that I think might help you.
1) So I don't confuse things (including myself) I'm going to pretend that
Persistence Context and Entity Manager mean the same thing.
@PersistenceContext(type=EXTENDED) does
1) You are outjecting your parent without an explicit scope, I can't remember
the rules but I think an entity will default to event.
2) No, I would say that mixing and matching the two is not a good idea. I
can't say for sure why your em isn't injecting properly, but play around with
it. It
From the docs
anonymous wrote : By default, entity beans are bound to the conversation
context. They may never be bound to the stateless context.
The scope specified in the bean is the scope it will be outjected to if it is
created through seam (i.e. @In(create = true)). When using @Out the
Is anyone using seam components to perform actions on the database when their
application starts? With Seam 1.0 I had a few SFSB that were application
scoped and used the @Startup and @Create methods to check if certain necessary
data was available and create it if it wasn't. These are
Your on the right track, now you're starting to get how the EM works and it's
time to bone up on your hibernate docs. Look into how collections are handled.
A tip, you can't set a new List into your object after it's retrieved.
View the original post :
Fair enough. I'll look into it some more when I'm testing the page parameter
converter change in a little bit. Either way though, I'm curious if you or
anyone else has a better solution? Creating an SFSB only to have it remove
itself from the application context in it's own @Create method
Looks good. Thanks.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3984299#3984299
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3984299
___
jboss-user mailing list
It doesn't need to be done. You have to merge your child because it was
retrieved before you began your conversation. If not, it wouldn't be available
to pass into your method annotated with @Begin. If you are conscious of your
conversation lifecycle and the fact that your persistence
No problem. It's frustrating at first, but once you get the feel for thinking
about things in terms of conversations it can make many complicated tasks much
easier (in my opinion at least).
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3984320#3984320
Reply
I'm thinking the completed flag is the way to go.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3984327#3984327
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3984327
___
I think the problem here has to do with the @Startup annotation. I take it
you're not using that?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3984343#3984343
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3984343
No problem. Happy to help.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3983857#3983857
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3983857
___
jboss-user mailing list
I'm running into another problem. It seems that the converter specified in
pages.xml is used to convert from String to Object, but not from Object to
String. I don't suppose that's by design? The method I'm looking at is:
public MapString, Object getParameters(String viewId, SetString
With a proper cascade on the activities list stored within the user, you should
be able to just bind the values that are editable via the value attribute of
each JSF component. After they are validated and the model is updated (i.e.
new values are set on each appropriate activity) saving the
I think you're biggest problem is you haven't gotten your head wrapped around
the conversational model yet. It definitely takes time and I'd recommend that
the first thing you do is at least skim through the Seam reference
documentation in it's entirety.
That being said, I'll try to explain
No problem. I'll try to play around with that next week. As far as the
ordering of page actions is concerned, I can see where you are coming from.
Most of the generic page actions I've set up have been for things like checking
permissions and I'd definitely want them to fire first. But what
I have several conversational components that retrieve a List of search results
and outject them as DataModels. To make my life easier, I had them all
subclass an object with the ability to paginate. To summarize, it basically
just keeps track of an offset into the data and a limit (how many
Ok, let me amend that. I just tried it with the page action returning a
symbolic view-id and it still doesn't get added as a query parameter during the
redirect. I'm using 1.1 beta. Am I missing something?
View the original post :
I believe returning null would result in a forward to the same page, I'm
looking for a redirect. Returning a view-id that begins with a / (like
/products/search.jsf) does seem to redirect correctly. Does anyone have page
parameters working? I've started looking through the source and it
It looks like it's a bug. The method public static String getViewId(String
url) in the SeamRedirectFilter uses url.substring(contextPath.length(),
getParamLoc(url) - suffix.length() + 1) + suffix; to calculate the viewId, but
that seems to clip the last character off. I think that
Wait, I take that back.
url.substring(contextPath.length(), getParamLoc(url) - extension.length() + 1)
+ suffix;
Is probably what you were looking for... I'll test that.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3983569#3983569
Reply to the post :
After looking at the source I'm thinking that using a wildcard to specify a
no-conversation-view-id for a group of pages isn't currently possible. Is that
right? Shouldn't it be? Generally I have several groups of pages that each
constitute an individual conversation, but they are not really
That really is cool. It makes you wonder what the JSF spec leads were thinking
to not allow action parameters in the first place.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3983128#3983128
Reply to the post :
Thanks Gavin. That's exactly what I had in mind myself.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3982128#3982128
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3982128
___
What if one wanted to use a different message depending on the circumstances?
It seems like it would be nice to be able to define a key besides
org.jboss.seam.NoConversation in the pages.xml file along with
no-conversation-view-id.
View the original post :
That was a bit vague I guess. Depending on what part of the application is
being accessed. In other words, something like No Conversation or Operation
timed out are fine for areas where the users are familiar with the application
(administrators perhaps) but other areas might require a bit
I could work with it, although I'm not sure how to set a different Manager
implementation. Just a thought though, how about the ability to define a
resource bundle in pages.xml that would be used by the resourceBundle component
to override the default values? Something like that could be
Thanks. That'll be helpful.
The resource bundle change is something that I could use now. If you want to
discuss possible implementations I might be able to contribute it over the next
month or so.
View the original post :
I hadn't really thought of that, however in the case where I would want to use
something like this the scope of the object would be its parent - i.e. the
object which created it.
I'm not saying that a createComponent method is necessarily the way to go,
but right now it seems to me that Seam
Not an inner class, the class definition would not have to be within the parent.
An example of how it works now:
| @Stateful
| @Name(productSearcher)
| public Class ProductSearcherImpl{
|
| @DataModel
| private ListProduct searchResults;
|
| private ListProductFilter
I think you're misunderstanding my problem. I don't want to put the objects
into a Context. I want to instantiate a variable number of unique objects of
the same Class, have Seam intercept each of them, and add them to a list.
Placing them in a Context is not only unnecessary since they are
You still there Gavin? If you've got a moment I'm curious to know what you
think about my issue with @Roles.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3963643#3963643
Reply to the post :
anonymous wrote : 1) Use @Roles
Roles are only useful if you can choose unique names at compile time. In the
use case I gave, the filters are built on categories which are dynamically
defined through the application so roles won't work. I've got code that looks
something like:
Now that I've been using Seam for a while, I wanted to point out a couple of
points that I've had trouble with or thought might be useful enhancements just
to see if anyone else out there agrees/disagrees/or has any suggestions of
alternatives.
1)I haven't found a good way to instantiate
You could, but I don't think it would make much sense. If you want to outject
a @OneToMany collection as a DataModel why don't you create a bean that
extracts the collection from the correct entity when it's accessed by your
application. Then your new bean can have the extracted collection
anonymous wrote : I can see uses for this, but remember you can do bijection
etc. through Component and the Context.
True, but then why not always use method calls and disregard annotations all
together? It seems to me that most of the functionality is available
programatically, but the
anonymous wrote : You should really use Component.getInstance(), not
Component.newInstance().
The problem with getInstance() is after I create the first instance subsequent
calls will retrieve the same instance from whatever context it was published
to. I need seperate, unique instances of
anonymous wrote : By stateless, I don't really mean using a SLSB, I mean
using only request-scoped state, and passing state as request parameters (like
the blog example does).
I'll check out the blog example, but I'd imagine that does bypass the usage of
a DataTable. Seems a shame since at
It's very much like a WebSphere DataSource, which is just a DataSource bound to
JNDI. Looks at the examples, particularly in the file jboss-beans.xml for how
to do this with JBoss.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3957801#3957801
Reply to the
anonymous wrote : petemuir wrote : anonymous wrote : Is there no way to end
a current conversation and begin an entirely new one in the course of a single
request?
| |
| | I'm pretty sure there isn't, Gavin wrote about this sometime ago on the
forum.
|
| I searched the forum and
anonymous wrote : Have you tried @Begin without the join=true?
I have not, but I'd imagine it will do the same thing. I don't think the
problem is that it's joining a long running conversation, but that it's seeing
the ended conversation, thinking that it's a temporary conversation and setting
Gavin,
I think you understand where I'm coming from and thanks for the link. I've
been thinking that it would be really helpful to have a resource for Seam
design patterns before. There are a couple of things I think I'm missing
though.
We've already discussed why a page scoped DataModel
75 matches
Mail list logo
