When do you mean the transaction has gone sour? after the exception? This is
expected - you need a new transaction at this point.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4129942#4129942
Reply to the post :
I've been using Interceptors for this kind of work. However one can only define
EJB3 interceptors at the class level.
What I do is a workaround, which I find rather nasty, but since I haven't
thought of another way yet and this works, I'll point it out.
I define an annotation which has
Yep, it works now.
Thanks for fix!
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4126349#4126349
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4126349
___
jboss-user mailing list
Ok, there's obviously a misunderstanding as to what is considered to be a
protected page. Rather than drag this out, I've modified the filter to
authenticate every request, regardless of whether there's any security
restrictions on the page or not. Hopefully this should now work for you.
I think the use case is slightly different. The way I enabled the HTTP basic
auth is based on the reference doc by editing the components.xml file:
| web:authentication-filter url-pattern=*.seam auth-type=basic
realm=My App/
|
All pages are protected already with the url-pattern
[EMAIL PROTECTED] wrote : This should be fixed in CVS now, please let me know
if there's any further issues with HTTP authentication.
Has this been tested? Because when I look at the code in the latest trunk, I
didn't see any code that would fix the second problem I mentioned (see the
Problem
The authentication should be triggered when calling/accessing a restricted Seam
component, doing the chain.doFilter() call. It can't happen in the filter as
not all contexts exist at that point in time.
View the original post :
[EMAIL PROTECTED] wrote : The authentication should be triggered when
calling/accessing a restricted Seam component, doing the chain.doFilter() call.
It can't happen in the filter as not all contexts exist at that point in time.
My point might not be right as I am not as familiar to the
If you're invoking a restricted method and the credentials are set (which is
what the AuthenticationFilter does) then a silent login will automatically
occur, with no need to explicitly call Identity.authenticate(). Digest
authentication is a special case, with a special type of authenticator.
[EMAIL PROTECTED] wrote : If you're invoking a restricted method and the
credentials are set (which is what the AuthenticationFilter does) then a silent
login will automatically occur, with no need to explicitly call
Identity.authenticate(). Digest authentication is a special case, with a
When I say protected, I mean that either:
a) login-required=true is set in pages.xml
b) A element is specified in pages.xml
or
c) A component method is annotated with @Restrict
As for the silent authentication, look at Identity.hasRole() and
Identity.checkPermission(), both of these methods
Bah, my xml-tags got stripped out of my response. Replace b) with:
b) A restrict element is specified in pages.xml
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4125384#4125384
Reply to the post :
Try this :D STOP USING RHDS RC1. I had allot of hassle with that thing to.
Download Eclipse WTP and JBOss TOOLS.. good luck
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4125385#4125385
Reply to the post :
As promised, the JIRA issue:
http://jira.jboss.com/jira/browse/JBSEAM-2558
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4124924#4124924
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4124924
This should be fixed in CVS now, please let me know if there's any further
issues with HTTP authentication.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4124982#4124982
Reply to the post :
Try logging out from a s:link like
| s:link action=#{identity.logout}X/s:link
|
as I guess you are using an h: or ice: component now?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4123354#4123354
Reply to the post :
Never tried, but you can place a s:link around an graphicsItem etc so I don't
see why not.
I don't know the root of the issue, just quoting people that know more ;-)
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4123381#4123381
Reply to the post :
Hmm. Is there a possibility to include the logout button in a dynamic
ice:menuBar?
And another question: Is this conversation scope so essential that a Seam app
can't live without it? For my app session and page scope are sufficient. Do I
have to use this conversation scope?
View the original
That, or then
| s:conversationId/
|
which is probably the most seamish solution
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4123390#4123390
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4123390
Well, s:button should work also. Or the other components if you propagate this
conversation parameters manually as suggested by Judy G in
http://www.icefaces.org/JForum/posts/list/6298.page
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4123357#4123357
Reply
OK. Thanks. It's working with s:link now.
But perhaps you know how to propagate the current conversation id?
ice:menuItem value=#{messages.logout} action=#{identity.logout}
| f:param name=??? value=??? /
| /ice:menuItem
I think the name would be cid or whatever I configured in
ice:menuItem value=#{messages.logout} action=#{identity.logout}
| s:conversationId /
| /ice:menuItem
does not work ... :(
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4123393#4123393
Reply to the post :
which values did you insert? can you post your components.xml?
thanks and best regards
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4119456#4119456
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4119456
Try putting @BypassInterceptors on your @Remove method rms.csvListAction.
Please don't bump.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4114418#4114418
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4114418
My problem is resolved. Thanks Pete
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4114488#4114488
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4114488
___
jboss-user mailing list
[EMAIL PROTECTED] wrote : Post some info about the logout action.
This is my logout button:
s:button value=Logout styleClass=button view=/login.xhtml
| action=#{identity.logout}
rendered=#{identity.loggedIn}/
This is my authenticator:
| @Stateless
|
Please file a jira issue so we can investigate
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4113974#4113974
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4113974
___
jboss-user
Thanks Pete. will do.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4113999#4113999
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4113999
___
jboss-user mailing list
Pete, what is this problem? Please help mee, thanks.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4114043#4114043
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4114043
___
Post some info about the logout action.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4113390#4113390
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4113390
___
jboss-user mailing
Please help me???
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4113257#4113257
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4113257
___
jboss-user mailing list
Try changing the top one to ScopeType.SESSION as they have in the booking
example
@Stateful
| @Name(hotelSearch)
| @Scope(ScopeType.SESSION)
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4113273#4113273
Reply to the post :
I had a look at the code for AuthenticationFilter.processBasicAuth(). It
actually looks like Identity is not being found in the context:
private void processBasicAuth(HttpServletRequest request,
| HttpServletResponse response, FilterChain chain)
| throws IOException,
Explicitly flush the PC in the INVOKE APPLICATION and catch the exceptions
there.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4107464#4107464
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4107464
I am using Seam in JSF layer + tx (SeamPhaseListener) and Persistence context
management. Spring in the middle layer. and JPA for persistence.
My problem is:
new JSF request, seam starts tx, jsf layer calls spring, which calls JPA daos.
Jpa dao executes several statements, the call returns
thank you! i'll give it a try...
cheers,
sven
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4107091#4107091
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4107091
___
jboss-user
Please file an issue in JIRA
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4105045#4105045
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4105045
___
jboss-user mailing list
Added JIRA: http://jira.jboss.org/jira/browse/JBSEAM-2255
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4105270#4105270
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4105270
___
So you are using a Session? Not JPA? You need to enumerate your config if you
are off the standard EJB3-with-Seam when you start your posts
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4104546#4104546
Reply to the post :
Do you have a larger stack trace that you can post? You may have compilation
errors in your rules.
Cheers,
Damian.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4104254#4104254
Reply to the post :
Hi, Pete,
I've got the following case. A method (no conversation) will be called to
delete a row in the database. The backing bean method returns without error,
because the flush is not occured at this time. Later the SeamPhaseListener
commits the first tx, which flushes the persistence
AFAIK (though I see some Spring stuff in there so I'm no longer sure) that a tx
commit doesn't cause the PC to be flushed. As I've mentioned to you on another
thread the flush occurs when you manually call flush() - which you may do or at
container invoked method boundaries.
View the original
The default flush mode of hibernate persistence context is transaction, which
means a flush will occur
1) when flush is called manually
2) when tx commits
3) when a query must be executed, which may require a flush
For conversation I chose to manually flush the session, so that I can also
Normally flush occurs when flush() is explicitly called or at
container-called-method boundaries.
What do you want to do in your user defined exception handler?
You can also stay on the current view by omitting the redirect element.
View the original post :
Hi Pete,
This is just the session timeout when the user is not using the application for
a period of time and then trying to use the application;
Apperciate your feedback;
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4101566#4101566
Reply to the post :
You are going to have to use your debugger to find out what that NPE in
Facelets is trying to reference.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4101629#4101629
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4101629
maybe it's a bug?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4101520#4101520
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4101520
___
jboss-user mailing list
The param tag within a redirect refers to http request parameters, not
parameters for the given message.
I'm not sure how to do what you're trying to do, except to simply use
| error.fileUpload = maximum allowed size
#{org.jboss.seam.web.multipartFilter.maxRequestSize/1000} kB. please
What's this timeout?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4101212#4101212
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4101212
___
jboss-user mailing list
When i now try to deploy my application, i now get
| ould not expand entry null into destination
I:\glassfish\domains\domain1\applications\j2ee-apps\seam-facelets\sesam-facelets-war_war
| java.io.IOException: Error expanding archive
What version of Seam?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4100554#4100554
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4100554
___
jboss-user mailing list
I am using 2.0.0.CR2 version of seam.
But i found out my problem.
I had a typo in application.xml which said sesam-facelets-war instead of
seam-facelets.
Had to look at the first line of the stack trace carefully to see that
happening.
Apologies for the trouble caused.. And thanks for the
You should place all the ear libraries in a lib directory in your deployed ear
for JBoss AS 4.2 rather than declaring in application.xml
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4100594#4100594
Reply to the post :
1) Seam should be declared as an ejb module, not a jar module
2) Include jboss-archive-browsing.jar and jboss-common-core.jar in your ear
lib/ directory.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4100178#4100178
Reply to the post :
Thanks!
I included these two jars and changed the seam declaration from jar module to
ejb module.
But i get a different exception now.
| SMGT0007: Self Management Rules service is enabled
| Application server startup complete.
| Exception occured in J2EEC
After a bit of googling, came across this bug
https://glassfish.dev.java.net/issues/show_bug.cgi?id=3386
And this one:
http://jira.jboss.org/jira/browse/JBSEAM-1590
Looks like an autodeployment issue in glassfish.
View the original post :
That's unfortunately a known bug (see
http://www.jboss.com/index.html?module=bbop=viewtopict=105236start=0),
though I don't know if anyone's created a JIRA report yet.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4097487#4097487
Reply to the post :
In that thread I just posted the link to the JIRA issue; I'd recommend voting
for and watching it.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4097602#4097602
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4097602
ok
I voted for this issue, however, if this is a bug, I think they should have
fixed it in version 2
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4097691#4097691
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4097691
I've added
@In(create=true) and the exception isn't thrown, but the object person injecte
seems to be null.
Seems that when the injection is done, the entity person is not created
correctly.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4090317#4090317
damatrix wrote : I read that using the ManagedPersistenceContext configured
in components.xml and injected in your code does not throw
LazyInitializationException (hope i got that right :-) ). I was quite surprised
to find this exception being thrown.
This is correct. The first issue I
and theres one more :
15:02:29,031 ERROR [[/mgr2]] Exception sending context initialized event to
listener instance of class
org.jboss.web.jsf.integration.config.JBossJSFConfigureListener
| java.lang.NoClassDefFoundError: javax/el/ELResolver
I Guess its because of jboss-el.jar and
ive added :
jboss-el.jar and jboss-el-api.jar
to application.xml and referenced to my ear project dependencies and i still
get the error :/
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4087629#4087629
Reply to the post :
Do any of the examples targeted platforms match your deployment platform? If
so, just imitate them. If not, then post what's different. (I probably don't
know enough to help you debug your problem, but maybe others can, if you post
enough information)
View the original post :
My Platform is the most standard platform ever i think - JBoss AS 4.2.1.
The thing im trying to achieve is Eclipse J2EE project wich is built from a
scratch with eclipse without using Seam-gen.
My project its just plain JSF page so it cant be source of a problem.
As of now there are no EJB's.
Here they are. i totally dont understand why it dosent work - all seems to be
pretty standard seam stuff and all is ok according to documentation
ahh and seam version is 2.0B1.
EAR Project Descriptor :
application.xml :
?xml version=1.0 encoding=UTF-8?
| application
If I were you, I'd create a blank seam-gen app, and verify that it deploys ok.
And then, file by file, transform it until it looks like your project. Then
either you'll find where the problem is, or if the problem mystically doesn't
show itself, you'll have a working project.
View the
Btw, when pasting files to the forum, I'd recommend trimming the excessively
long lines. It makes it hard to read the rest of the forum because you have to
scroll horizontally all the time.
Good luck with your project!
View the original post :
thats what i did lat time... ill give it another try tomorrow.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4087688#4087688
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4087688
Okay !
2 things to sory out !
the cause of a problem was actually a documentation bug !
anonymous wrote : You must include jboss-seam.jar, jboss-el.jar and
jboss-el-api.jar in the EAR classpath. Make sure you reference all of these
JARs from application.xml.
Default seam-gen Project does not
Shane
Thanks for the tip, it worked. I added method in Authenticator class as below:
public boolean isLocked() {
...
return boolean;
}
and then added following page navigation rule
navigation from-action=#{identity.login}
rule if=#{not identity.loggedIn and authenticator.locked}
redirect
Authentication is performed within the context of a JAAS login, so we are
restricted by the contract of the LoginModule.login() method, which specifies
that only a LoginException be thrown if authentication fails. Unfortunately,
LoginException only allows a message to be specified and no
i Was right - hard inserting values from .properities file solved the problem.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4086408#4086408
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4086408
The requestaction again :)
| package cz.bpsolutions.mis.request;
|
| import java.io.Serializable;
| import java.util.ArrayList;
| import java.util.Calendar;
| import java.util.Collection;
| import java.util.Date;
| import java.util.List;
|
| import javax.ejb.Remove;
|
RequestHistory.java
| package cz.bpsolutions.ims.actions.historyservice;
|
| import java.util.Date;
|
| import javax.ejb.Remove;
| import javax.ejb.Stateful;
| import javax.persistence.EntityManager;
| import javax.persistence.PersistenceContext;
| import
try s:selectItem.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4082082#4082082
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4082082
___
jboss-user mailing list
I forgot, the problem is solved I used :
| h:selectManyCheckbox value=#{ReportManager.reportSelected}
layout=pageDirection
| s:selectItems value=#{reports} var=rep
label=#{rep.descReport}/
| /h:selectManyCheckbox
|
|
thanks
Forgot to mention the second sort of exception that happens occasionally in
console :
14:40:19,468 ERROR [SimpleStatefulCache] problem passivation thread
| javax.ejb.EJBException: Could not passivate; failed to save state
| at
And, yet another one, coming again from background process (sorry for
overflooding the thread with these long stack traces)
15:18:32,890 ERROR [SimpleStatefulCache] problem passivation thread
| javax.ejb.EJBException: Could not passivate; failed to save state
| at
You have to remove the EcheancePret from the EcheancePrets collection in Pret
before you can delete it.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4080648#4080648
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4080648
Are you really occasionally getting a NoClassDefFoundError exception?
Have you included the jbpm jar? It has to be either in a /lib directory inside
your ear, or in the root of the ear with a declaration for the jar in
application.xml
Are you using jbpm in your application?
View the original
Also notice that the code that is causing this to happen is:
anonymous wrote : 14:26:04,765 ERROR [STDERR] at
org.jboss.ejb3.cache.simple.SimpleStatefulCache.passivate(SimpleStatefulCache.java:196)
| 14:26:04,765 ERROR [STDERR] at
anonymous wrote : (check that it is declared on the session bean business
interface)
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4079956#4079956
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4079956
wise_guybg,
thank you for your reply.
No, my application does not use jbpm. Earlier I have deployed application with
jbpm, keeping to all rules, and it worked well. But now I have undeployed it.
Exception occurs without any user action , just appears in console in
background.
View the
There is no var attribute on f:selectItems. You are getting confused between
f:selectItems and s:selectItems
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4077680#4077680
Reply to the post :
Yes I made this misstacke. But after correction there is no change. To resolv
this problem I tried anything, but I'am still block.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4077688#4077688
Reply to the post :
So post what is *now* not working
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4077701#4077701
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4077701
___
jboss-user mailing list
| h:selectManyCheckbox value=#{reports}
| f:selectItems value=#{reporte}/
| /h:selectManyCheckbox
|
That's the code in my jsf page. The Bean and the entity page are the same.
View the original post :
You need to read up on how selectitems works in JSF as what you have is wrong.
You should consider using s:selectItems - take a look at the UI example.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4077706#4077706
Reply to the post :
Ok but I don't understand the difference between f:selectItems and
s:selectitems.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4077713#4077713
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4077713
and where do you outject or bind contactel under that exact name?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4076623#4076623
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4076623
I thought @DataModelSelection doesn't need to have @Out. However I added :
anonymous wrote :
| @DataModelSelection(conts)
| @In (required = false) @Out(required = false)
| Contact contactel = new Contact();
|
And I have the same Exception.
View the original post :
I was referring to contactel. Aren't you outjecting it as conts? Or am I
misunderstanding something?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4076633#4076633
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4076633
I'm not outjectiing as conts, conts is here because DataModelSelection must
be attach to a Datamode, and I have two Datamodel. Otherwise, I deleted the
DataModelSelection annotation and I have the same problem.
View the original post :
OK. But still it complains that it can't find contactel. Would
| h:inputText value=#{ContactManager.contactel.lastName}/
|
work?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4076638#4076638
Reply to the post :
I try your solution but it's the same thing
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4076642#4076642
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4076642
___
jboss-user
You want
@DataModelSelection(conts) @Out(required = false) Contact contactel;
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4076684#4076684
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4076684
If this is a question yes I want that.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4076707#4076707
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4076707
___
jboss-user mailing
However I try with your code but it change nothing .
(I'm french so my english is not perfect)
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4076714#4076714
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4076714
Are you in a long running conversation when contactel is null?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4076716#4076716
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4076716
1 - 100 of 278 matches
Mail list logo
