http://wiki.jboss.org/wiki/Wiki.jsp?page=ClusteringInJBossVersions at this
moment doesn't have info for JBoss 4.2
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4118696#4118696
Reply to the post :
Installing JBoss 4.2.1 and 4.2.2 from distribution in both there is one hard
coded
jboss:service=DefaultPartition
left instead of
jboss:service=${jboss.partition.name:DefaultPartition}
and that is towards the bottom of file
server/all/farm/cluster-examples-service.xml
Also, did I get this
Have same problem since switching from Seam 1.2.1.GA (with JBoss 4.0.5.GA) to
Seam 2.0.0.GA (with JBoss 4.2.1.GA)
ERROR [org.jboss.seam.drools.RuleBase] errors parsing rules in:
/META-INF/security-rules.drl
| ERROR [org.jboss.seam.drools.RuleBase] Rule Compilation error Type
mismatch: cannot
Quasi-empty rules file works for me too, but that is useful only in one of our
applications.
If I need rules it still does not work.
It works in a test application I wrote.
But it doesn't work in this larger application we're moving over from Seam
1.2.1.
Is it some tricky configuration issue
Seam 2.0.0.CR2, seam-gen an ear application.
In target name=ear I see
include name=lib/janino-*.jar/
and
include name=lib/richfaces-api*.jar /
which I think should be without dash
include name=lib/janino*.jar/
because in the lib directory there is janino.jar and the other one should be
In the seam-gen generate components.xml the two
action execute
apparently don't go with the 2.0 schema, says my Eclipse.
It is happy with an
action expression
instead. Not sure who of the parties is wrong, but one of them is.
View the original post :
Looks like execute might be the new way, per
http://jboss.com/products/seam/components-2.0.xsd
but it seems my JBossIDE for Eclipse doesn't know yet. Cached Schema from how
long ago?
Also
http://jboss.com/products/seam/pages-2.0.xsd
now uses execute instead of expression.
Per reference
Ok, I retract the richfaces, I see the impl and ui elsewhere, but how about the
janino, there is no janino-, I can't find one.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4101159#4101159
Reply to the post :
I seem to see a difference with the way action classes are handled in
seam-gened projects whether
- ear project (no special treatment) or
- war project (exploded in own directory).
Does that have to be that way by design, or is it just not implmented yet in
seam-gen for ear?
View the
You're right. Property action.dir is overridden in the build-dev.properties
file. I wouldn't have looked there unless you had pointed it out. Thank you.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4100657#4100657
Reply to the post :
According to build.xml the action and the model source directories both get
compiled into the same jar directory.
So we're wondering: Is their separation just for clarity?
Don't see a difference in the build.xml ant way of exploding or deploying.
Don't see a difference in the Eclipse way
1.) Please clearly define behavior of @Startup and the call to @Create for an
application scoped component in a cluster.
2.) Aware of other mechanisms, but yet wondering ...
Is there, will there be a simple way to have an application scoped component
have the same state across a clustered
Is http://jira.jboss.com/jira/browse/JBSEAM-1009 going to make it into 2.0?
Already breaking compatibility, good time for fix to that old problem.
If not the code of JBSEAM-1009, then equivalent functionality?
Main point: Allow restrictions to be set per wildcard and per page without
Some objects live a long time, e.g. application scoped components, EJBs with
timers, and I guess MDBs.
Now if there is an @In, will that object that's been injected be passivated
ever, sometimes, or never?
As passivation occurs only outside a business method call (right?) there
shouldn't be a
Making sure I get this right:
An application scoped component is good e.g. to keep settings. It has the same
contents on all machines in a cluster. Nice magic working for us inside JBoss.
Now if I change (i.e. code changes) the value of a member field it will be
available on all machines in
Great!
That means I don't have to worry about injecting an object that has a huge tree
of objects hanging off it. At least no worry about passivation.
Still trying to figure how to reduce the amount of stuff that JSF thinks is
state worth shipping to the browser and back, but that's another
If they aren't clustered, then how does this work in Seam reference section
3.1.7. Application context:
Application context is mainly useful for holding static information such as
configuration data, reference data or metamodels.
How then to update configuration data?
View the original post :
I think what I see is that in the MDB I don't have access to Seam contexts.
But I'd like to get my server wide settings out of an application scoped Seam
component.
I think I've seen that if I'd declare that component an SFSB and try to get it
as EJB3 than I won't get the same instance as if I
Just about the same minute you wrote that I looked at Seam reference section
3.2.5. Message-driven beans, which says what you're quoting. I was figuring
the same solution, I'm going to try @Name and injection.
I think we had the same problem with messages coming to MDBs before Seam is
Can that be fixed in the future?
What is it? Name conflicts?
Sure, some combinations might be impossible or to too hard to work out.
But some combinations should be possible.
Components are supposed to be plug-and-play, as much as reasonably possible.
View the original post :
Before I'm going to start following advice from
http://www.it-eye.nl/weblog/2006/11/20/adf-faces-and-cache-control/
I'm just wondering, is there or is there planned any construct to augment HTTP
cache-control from Seam, maybe per page, maybe in page.xml?
While on the topic, is there any
My problem apparently has gone away too, yesterday, so far running fine on two
servers.
I happened to rearrange how two Seam components (both stateful with scope
application) were interacting. (For completeness of record: I moved storing
of some kind of unique id from the one executing on
Can I help along JBSEAM-1009 by writing regression tests for it? Please point
me to relevant files in Seam source that test security so I can imitate.
My current application would be a pain to secure without it, and I'm planning
on writing another app. I am interested in having 1009 in an
I recant. The s:link view=/myOther.xhtml action=#{conversation.end}
value=Outta Here / doesn't work like an action on the source page, but on
the target page.
Now I have tested it works to write one component like
import org.jboss.seam.annotations.Name;
| import
Then how about introducing propagation=kill which mostly works like
propagation=none but doesn't let the conversation linger around until it
times out.
As I want to use these inside s:link/ and not inside navigation rules that
beforeRedirect=true doesn't work for me, does it?
View the
Pete, I think you're thinking of uses of s:link with action=some.action,
while...
I'm thinking of uses of s:link with view=/some.xhtml.
There is no action involved. I don't think there is a redirect. Right off to
the target page with a GET from a URL, render it, done.
I want to use s:link,
Found something that works as I want it to:
s:link view=/myOther.xhtml action=#{conversation.end} value=Outta Here /
Not sure whether to call that syntax sweet, but it seems to work.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4034364#4034364
Reply to the
I admit, you have to know what conversation to end. I looked closer at what
I'm doing, and the problem/question seems to be:
Should propagation=end end the conversation when entering the target page or
when leaving (!) the target (!) page?
I argue it should when entering, but it apparently
Started using Exadel Studio 4.0.4 installed on top of JBoss IDE.
Much happier now with the Ctrl-Shift-F formatting of XHTML documents.
Very nice too if you're using Facelets for templating.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4033101#4033101
Reply
Ok, we're comparing JBoss IDE downloaded a couple of months ago versus then to
it adding Exadel Studio downloaded this week.
So different, even a blind cow would see the difference.
Maybe that's merged into JBoss IDE now? I didn't check last month.
I know you work there, I guess you must have
So when I right-click on the my.xhtml there is an option Open With Exadel
HTML Editor.
That one also at the bottom has tabs Visual/Source, Visual and Source.
That's quite different than Open With HTML Editor or Oprn With XML Editor,
which are the JBoss IDE editors I think you're talking
Well, then maybe some of it configuration parameters are different.
Because the way it worked in JBoss IDE made my code look horrible. I couldn't
teach a guy working with me to write decently formatted XHTML.
Now the way it works with Exadel (installed on top of JBoss IDE) is better.
Funny
First, that propagation=end was hard to find. There was no example in the
reference doc. I think only recently it mentions for s:link that propagation
accepts end as option.
Pete mentioned a while ago that none leaves the conversation sitting around,
while end disposes of it. So I'd like to
Is there any way to write something into a my.page.xml so that when coming into
that page from no matter where there will be a new conversation. Temporary
unless requested to be long running. But new and empty.
That should work no matter whether arriving with or without a conversation.
Point
Reference doc section 21.1.3 Seam servlet filters subsection Context
management for custom servlets discusses web:context-filter
url-pattern=/whatever/*/.
It reads The context filter expects to find the conversation id of any
conversation context in a request parameter named
conversationId.
Sure, I could do it with a Servlet. But then I'd have to figure out how to do
everything else from a servlet that I already know how to do with .seam,
.xhtml, .page.xml, security, exceptions, etc.
I have a byte array in the property of a component. Obviously accessible from
within an action.
Thanks for both useful answers.
I solved the problem per http://wiki.java.net/bin/view/Projects/FaceletsFAQ by
adding to web.xml an entry
!-- prevent XHTML comments from being rendered (by Facelets) --
| context-param
| param-namefacelets.SKIP_COMMENTS/param-name
|
If you say what it isn't, also say what it is:
### Eclipse Workspace Patch 1.0
| #P jboss-seam
| Index: doc/reference/en/modules/conversations.xml
| ===
| RCS file:
A question then is:
What's the different behavior then with the back-button in the browser,
different for propagation none versus end.
Seam supposedly (and as far as I have seen) is quite gracious about using the
browser back button and then continuing to work from there.
But isn't that
Much of the last question is answered in Seam reference 7.1.2. Seam and the
back button.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4028557#4028557
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4028557
!ATTLIST page login-required (true|false) #IMPLIED instead of false fixes
the problem on my machine.
The bigger problem though would be people who don't change the DTD e.g. from
1.2 to either 1.2.1 or 1.3 and still get the false instead of recognizing it
isn't defined. So a login-required
JBSEAM-1009 is about (if switched on) explicitly setting login-required (and
restrict) per page or per wildcard in a way that allows a specific page to be
less restricted than a * site wide wildcard. For each (login-required and
restrict) it picks the most specific page where it is defined and
Exactly, I agree with
anonymous wrote : A missing login-required should be interpreted as null, and
delegate to the more general widcard.
And that's where dom4j and the existing DTD are messing with us. Because there
isn't a way to tell the login-required isn't there. Dom4j insists on saying
It also works fine (I think to remember) without DTD listed in any page.xml,
because then dom4j doesn't say it is false when in fact it isn't there.
One could say that's a bad library, that returns different results for an
attribute value whether the DTD is mentioned in the XML or not. Though
Am I seeing that correctly:
If a property is primitive type boolean, then EntityQuery cannot tell that I
don't want to search for it in a specific query (from a form at a list view),
it would always search either for false or true, but never both.
The workaround is to define the property of
title was supposed to be still not enough
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4027599#4027599
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4027599
___
jboss-user
Come to think of it, how about a
s:selectBooleanCheckbox
that allows Boolean.TRUE, Boolean.FALSE and ... null !
Any hopes?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4027603#4027603
Reply to the post :
Just downloaded Last Updated on Safari: 2007/03/10, Updated: 3/10/2007
5:08:38 AM. That's after Dr. Yuan has submitted the final files. Let's hope
it is the final version.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4027765#4027765
Reply to the post :
Then how about two different names, e.g. s:hasPermission with only two
parameters and s:hasPermissionFor with three parameters.
I mean, s:hasPermission with null as 3rd parameter is getting old quickly.
Plus, I don't think there is enough discussion in the reference documentation
about what
Not 100% confirmed, but I think I got a reproducible case:
Don't have a login-required for a page, but for the page have a s:hasRole or
s:hasPermission that consequentially throws a different exception than what you
probably have been expecting.
Meanwhile though ... I'm having a heck of a time
Trying to answer Gavin's question how I get this.
To be clear, the NPE is gone with actualFlushMode not being null any more.
For completeness of record let's mention I'm now running the 2nd patch of
JBSEAM-1009 on a build we did from a CVS pull on Friday.
When starting up the server and having
s:hasPermission with only two parameters could be more readable in page.xml
files.
Is it rocket science, impossible or just a question whether someone bothers to
implement that shorter signature?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4027403#4027403
The double slashes are still showing up in the Address field of the browser.
Now I think they show up after a login redirect.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4026146#4026146
Reply to the post :
I see in UserPrincipal.java a
ServletRequest servletRequest = Lifecycle.getServletRequest();
I am trying the same in a Seam component
@Name(tricky)
| public class Tricky {
of mine where I'd ultimately like to get to the headers.
Problem is when I'm having a page action calling an action in
Calls to changeFlushMode that get passed a null flushMode from a null
actualFlushMode?
I haven't changed anything that seems related, but upgrade to a build we make
from CVS.
In class ManagedPersistenceContect method setEntityManagerFlushMode() throws a
NullPointerException.
I dont think you
Importantly to my well being in put in that
private FlushModeType actualFlushMode = FlushModeType.AUTO;
and now I'm running without crashes.
When I'm out of trouble for the afternoon I'll look again.
One hint how I got there might be: Page action returns outcome, navigation
rule makes it
I know I've suggested the exact wording, but my consciousness will bug me if I
don't mention the following. If the fix instead of
private FlushModeType actualFlushMode = FlushModeType.AUTO;
would write to the same effect
private FlushModeType actualFlushMode = flushMode;
then it would be
Maybe I'll find out I misconfigured something, but about the same time I
updated to newest version from CVS I started getting a lot of double slashes as
in
http://127.0.0.1:8080//myproject/whatever.seam
That was a couple of days ago.
View the original post :
Found the trigger of the double slashes: I used a render instead of a
redirect in a navigation rule.
Still me thinks it shouldn't cause double slashes.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4026029#4026029
Reply to the post :
Have a wildcard login-required=true.
Have a page specific login-required=false.
It appears not to be effective.
Why do I need it? Because I want different login depending on which part of
the site. One part is for mobile devices. Very different. So in the
login-view-id I point to where in
I've missed that already once, can you please explain where the inheritance of
login-required happens?
I can't see it in package core class Pages or in package pages class Page.
I am looking at where there are references to (uses of) Page methods
isLoginRequired and setLoginRequired.
I am
Found it in Pages method enterPage in the for loop over getPageStack.
One could argue whether a specific setting for a page should be allowed to
override a wildcard setting.
Admittedly, the way it is many people will feel safer.
View the original post :
Gavin's answer wasn't on my screen. Sorry. Left desk, came back and finished
typing ten minutes later...
Thanks for pointer!
Still trying to figure my original problem to allow login to go across multiple
pages without going into a loop on then violating login-required=true.
View the
Consequentially registration of new users for which obviously
login-required=true doesn't work.
So as it is that prevents us from having a
page view-id=* scheme=http login-required=true
because we cannot have a subsection of the site then that allows registration.
I'd rather do a search for
How about only allowing login-required=false to override if set specifically
for one page?
That means keep it as it is now, unless an explicitely set
login-required=false for a specific page, not a wildcard, is in effect?
Then even in a site that requires login everywhere else one could still
Here is a beginning patch, is this something I should continue or drop?
### Eclipse Workspace Patch 1.0
| #P jboss-seam
| Index: src/main/org/jboss/seam/core/Pages.java
| ===
| RCS file:
doc/reference/en/modules/events.xml probably should say something else but
JSFadn
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4025652#4025652
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4025652
I've coded this out, hopefully about as elegant as one can in that sections of
code ;) Changed three source files.
Should I make a JIRA and submit the diffs for review?
Point is that I want to be able to have a whole directory or all of a site to
default e.g. to begin-conversation join=true /
And if you have under a wildcard page, e.g.
page view-id=/somedir/*
| begin-conversation join=true/
| /page
a more specific page without begin-conversation, e.g.
page view-id=/somedir/specific.xhtml
| param name=specificId value=#{specificHome.id} /
| /page
does the specific page
Thanks for pointing that out!
Looks like it is working, as far as I have tested it. That's neat.
There was no mention in the reference documentation, so I didn't even think it
was possible.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4025270#4025270
Reply
How long then will that image be available for downloading by the browser, e.g.
if I give it a byte array?
Let's say some browser instance somewhere for whatever reason comes back four
minutes later to get that image at a URL.
View the original post :
Been working on this for a while, so this isn't an aimless question.
Face to face I'd ask: What do you want to hear first, the purpose, or the
question(s)? Let's have the question(s) first.
Questions:
In 6.3. Starting conversations with GET requests it says There is also an
end-conversation
Luckily no one has answered yet. Can't believe I was so confused about this.
I am looking at 6.1 Seam's conversation model and at JEE5 Tutorial's JavaServer
Faces Standard Request-Response Life Cycle again and at my own pages.
I'll be back, I hope, reporting what finally works for us.
View
I think my trip down confusion road started when we used s:link instead of
h:outputLink for menu items that shouldn't have propagate the current
conversation.
Moral of the story: For your general purpose links to anything, stuff that
isn't meant to propagate a conversation, don't use an
You know the wordings:
s:conversationPropagation type=join /
begin-conversation join=true /
s:link view=/some.xhtml propagation=true /
I'm not 100% sure whether there is a great way to rename them, but that was a
hurdle in making sense of the examples.
I'm not sure just writing a textbook on
Noticing new .jar files in seam-gen generated code. Good, but having a moment
of worry here.
Where is a statement I can show a client that says something like whatever
libraries are within the Seam distribution are safe to use in commerical
projects, i.e. at least Apache License or something
That's good enough for my peace of mind, a good faith effort. At least I've
confirmed you're not knowingly or intentionally (or recklessly) inserting
commerical libraries. Common sense told me that's what you do, but I couldn't
find it in writing.
View the original post :
Seam-gen in faces-config.xml now has a comment
!-- Disabled when using Ajax4JSF --
| !--
|
view-handlerorg.jboss.seam.ui.facelet.SeamFaceletViewHandler/view-handler
| --
Glad there is a comment, but the missing view-handler confuses. I thought the
view-handler
Found it in web.xml.
Comment in faces-config.xml could have mentioned that.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4024462#4024462
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4024462
I'm very carefully re-reading 6.1. Seam's conversation model, cross-reading
JEE5 tutorial section The Life Cycle of a JavaServer Faces Page.
6.1 bullet 2 makes a difference between long-running conversation context and
temporary conversation context.
Then bullet 3, 4 and 5 state whether they
Same kind of problem, using JBoss 4.0.5.GA. Started when I had a new
application scoped SFSB in Seam.
Very long and in a few minutes recurring stack trace begins with
00:04:03,187 ERROR [SimpleStatefulCache] problem passivation thread
| javax.ejb.EJBException: Could not passivate; failed to
An enum converter is nice, but one step further we'd like to implement a
javax.faces.convert.Converter that for its getAsObject does a query. In
contrast, the getAsString was easy.
Would be nice to use an @In EntityManager entityManager.
Question: What kind of component (with what
Trying to understand my car's engine.
What was the reason for null:
A) Because it wasn't a Seam component (lacking @Name) the @In annotation didn't
even get intercepted.
B) Because it wasn't a Seam component (lacking @Name) there wasn't a context to
look up anything (even though an
In section 21.1. Annotations for component definition, @Name, or in Chapter 3.
The contextual component model:
The @Name annotation makes a class, e.g. a session bean or an MDB, a Seam
component. If it is not present then other annotations, e.g. @In, will not
function as expected, e.g.
The brand new @AutoCreate isn't listed yet in Chapter 21. Seam annotations.
Same for @PerNestedConversation.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4022857#4022857
Reply to the post :
The (email?) renderer component isn't listed yet in Chapter 22. Built-in Seam
components.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4022858#4022858
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4022858
Wrote a MDB months ago, used @PersistenceContext and @EJB to inject. Inside
the MDB via one of those @EJB got a stateless bean and called a method in it
(to do the actual task). That stateless bean also used @PersistenceContext,
@Resource and @EJB.
Then I wanted to make better use of Seam,
Discussed previously, but as Pete says he doesn't have that problem, here to
clearly state how it happens:
Have a Home object, e.g. CarHome extends EntityHome, named carHome. Have a
factory (as recommended by reference document) in it named car.
Have a page that as parameter sets carHome.id.
From an implementation point of view it is logical.
From the point of view of who is the intended audience, probably people
looking for an easy way of coding, the advice in the reference doc to use that
factory too easily leads to surprising results. Throwing a curveball?
View the original
Reference documentation (jms.xml) shows in 17.1.1. Asynchronous methods an
apparently incorrect
@IntervalDuration Date interval
when it should be
@IntervalDuration Long interval
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4019304#4019304
Reply to the post
17.2.2. Sending messages in an example reads
paymentQueueSender.publish
which isn't possible, it has to be
paymentQueueSender.send
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4019338#4019338
Reply to the post :
According to reference documentation 3.1.10. Concurrency model I'd think a
session scoped component doesn't need it, only an application scoped component
can benefit from it.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4019505#4019505
Reply to the post :
MyFaces 1.1.5 has a release date of Feb 16th 2007, Seam 1.1.7 appears to be
scheduled for Feb 20th 2007.
I'm asking because MyFaces 1.1.5 supposedly does a few things better in regards
to portlets.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4018732#4018732
Chapter 4.2. Configuring components via components.xml reads Sometimes we want
to reuse the same components.xml file with minor changes during both deployment
and testing. Seam lets you place wildcards of the form @wildcard@ in the
components.xml file which can be replaced either by your Ant
While I didn't look close enough to determine whether there are other problems,
from my own experience I know sooner or later you could run into a problem with
that factory being invoked only once in a conversation, and hence your factory
made instance not being the same as the one home uses.
Building from CVS...
Reference documentation chapter on remoting still tells to use
SeamRemotingServlet.
I get class not found, obviously. Removed it from web.xml, but then remoting
doesn't work. Now trying to keep up with the changes from JBSEAM-790, looking
at configuration chapter.
Pete,
To get the problem I saw you need to do this as I got to do when I started from
a seam-generated project a couple weeks ago (things changed in seam-gen since,
I think now there is join instead of begin):
From a list view (with query) go to create new entity page with a propagation
Not sure about all the details now, but the problem was real. I clearly had it
display in the view fields from the factory made instance and from the
home.instance, and they were two separate instances. I showed the screen to a
colleague. Since I've stopped using the factory made instance I
Jarkko,
You have mentioned in a past posting you got it to work. Can you share a
working project?
If your project is confidential, I'd suggest make a super simple table, e.g.
(Oracle example)
CREATE TABLE THINGS
| (
|ID VARCHAR(30) PRIMARY KEY not null,
|TITLE VARCHAR(100) not
Can't get it to work. Anyone success running any Seam (xhtml, not jsp) in a
portal?
In the end supposed to run in Liferay, but even success in JBoss Portal would
be nice.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4015895#4015895
Reply to the post :
1 - 100 of 138 matches
Mail list logo
