I have created a JIRA Feature Request:
https://jira.jboss.org/jira/browse/JBSSO-46
Please vote for it :-)
Thanks.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4194878#4194878
Reply to the post :
CR1 - OK:
http://mediatorsystems.com/jboss-federation-server-exploded.ear-CR1.zip
http://mediatorsystems.com/jboss-sso.sar-CR1.zip
CR2 (builded with Java 6) - Fails:
http://mediatorsystems.com/jboss-federation-server-exploded.ear-CR2.zip
http://mediatorsystems.com/jboss-sso.sar-CR2.zip
View
Hi Sohil,
[EMAIL PROTECTED] wrote : Alejandro-
| as a hint, it looks like from the stacktrace, its a Class Not Found issue.
Looks like the Federation server service needs the OpenSAML libraries packaged.
|
You can't expect java.lang.NoClassDefFoundError: org/opensaml/SAMLAttribute is
the
Hi Sohil,
[EMAIL PROTECTED] wrote : msystems-
| 1/ Try to run this on Java5 instead of Java6.I have never run JBoss SSO on
Java6, so I am not sure if there are some ClassLoading issues here that need to
be fixed with a different packaging structure
|
This is a Java 6 problem. When I run
In my world, it looks like JBoss Negotiation should be part of JBoss SSO or
JBoss SSO should integrete with JBoss Negotiation, because JBoss Negotiation
supports SPNEGO Authentication.
Is there any plans for JBoss SSO to support SSO HTTP/SPNEGO Authentication?
View the original post :
[EMAIL PROTECTED] wrote : Yes based on the stack trace looks like the
OpenSAML library does not like Java6 too much from a memory consumption
standpoint. Especially during the phase where SAML xml needs to be produced
from its Object model.
|
| I have no idea what the reason could be. I
I have downloaded and builded
http://anonsvn.jboss.org/repos/jboss-sso/dev/tags/jboss-sso-1.0CR2/ - and it
fails when I'm using it :-(
Environment:
JBoss 4.2.3.GA
JBoss Seam 2.1.1.CR1
Java 6
Everything works fine with CR1.
I have three servers and I choose to start only one of the servers.
It looks like JBoss SSO have been in the developing pipeline for a long time,
i.e. we're still waiting for a G.A. release.
What is the roadmap for JBoss SSO and when will JBoss SSO be ready for a 1.0.GA
release?
I think JBoss SSO is an importent JBoss projekt and we're using JBoss SSO CR1
Hi Sohil,
Thank you for your answer.
/Kenneth
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4194464#4194464
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4194464
___
jboss-user
'Future Roadmap' - JBoss World Berlin:
anonymous wrote :
| Add support for connecting with more Identity Stores
| like Active Directory, Windows Logon, SiteMinder etc
|
When will JBoss SSO support it, e.g. SiteMinder?
And what about the JBoss AS 4.2.2.GA bug:
| persistence:managed-persistence-context name=entityManager
|auto-create=true
|
persistence-unit-jndi-name=java:/maxcontrolEntityManagerFactory /
The persistence component is named 'entityManager'
Yes, it must be an EAR file - here is a little more information :-)
http://www.developer.com/java/ejb/article.php/10931_3670496_1
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4128189#4128189
Reply to the post :
Where is the 'transaction.manager_lookup_class':
| property name=hibernate.transaction.manager_lookup_class
value=org.hibernate.transaction.JBossTransactionManagerLookup/
|
and the 'jta-data-source' looks wrong, try:
|
anonymous wrote :
| as to your first question about
hibernate.transaction_manager_lookup_class... I dont know! where is this xml
configuration set?
In the persistence.xml:
| persistence xmlns=http://java.sun.com/xml/ns/persistence;
|
I guess the name of the EAR file don't equals 'prueba'?
| core:init jndi-pattern=prueba/#{ejbName}/local debug=true /
| ^^
| Should be the name of the EAR file.
|
View the original post :
Create a JIRA (new feature).
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4128111#4128111
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4128111
___
jboss-user mailing list
Or override the evaluateExpression(String expr) method.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4127737#4127737
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4127737
___
Yes it is possible.
Extend the Identity class and override the hasPermission(String name, String
action, Object...arg) method.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4127733#4127733
Reply to the post :
BTW: FlushModeType.MANUAL works only when Hibernate is the underlying
persistence provider - maybe other persistence providers will support this
feature in the future (in my opinion JPA should include FlushModeType.MANUAL at
least in the next version of JPA).
View the original post :
Yes, it's obsolete.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4127878#4127878
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4127878
___
jboss-user mailing list
wchico2 wrote : What about the configuration? When using the Rule engine one
would specify it in the components.xml. I assume I would leave that out and
only specify that I use the basic Seam security despite the application of e.g.
s:hasPermission and such.
Just use the 'normal' Seam
To my knowledge you need to use a Seam-managed persistence context, i.e. @In.
JPA doesn't support FlushModeType.MANUAL, only FlushModeType.AUTO and
FlushModeType.COMMIT.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4128002#4128002
Reply to the post :
kasim wrote : msystems wrote : Use @PersistenceContext if you are using
EJB3 and if you need a new transaction
(@TransactionAttribute(TransactionAttributeType.REQUIRES_NEW) ) - Seam ref:
| |
| | anonymous wrote :
| | | If you are using EJB3 and mark your class or method
anonymous wrote :
| I am using EJB3/JPA persistence and am having trouble with a manually
flushed transaction. Even after a call to em.flush(), the data is not visible
to an external db client -- it seems that even though manually flushed, the
transaction is not committed until after the
Use @PersistenceContext if you are using EJB3 and if you need a new transaction
(@TransactionAttribute(TransactionAttributeType.REQUIRES_NEW) ) - Seam ref:
anonymous wrote :
| If you are using EJB3 and mark your class or method
@TransactionAttribute(REQUIRES_NEW) then the trans-
| action
Rephrasing my last answer :-)
If you need a new transaction and using EJB3 use @PersistenceContext -
otherwise use SMPC for everyting else.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4127257#4127257
Reply to the post :
Yes you can use Acegi instead of Seam security in a Seam application (I have
done it - but now I'm using Seam security).
I used Acegi because Seam security didn't exist in Seam when I started to use
Seam.
I will recommend Seam security because it's a lot easier to use in a Seam
application
BTW: I'm using JBoss 4.2.2.GA and JBoss Seam 2.0.1.GA
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4125766#4125766
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4125766
___
I have a hard time to understand why a seam-managed persistence context (SMPC)
@PersistenceContext behaves differently from a non-managed persistence context
@PersistenceContext.
I know I have to use @In to use the SMPC entitymanger - but it looks like Seam
also changes the behaviour for
http://www.theserverside.com/news/thread.tss?thread_id=48270#246600
BTW: I'm using JBoss Seam and I like it a lot :-)
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4125096#4125096
Reply to the post :
http://www.theserverside.com/news/thread.tss?thread_id=48270
Support JBoss Seam :-)
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4124937#4124937
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4124937
Why not:
| core:resource-loader
| core:bundle-names
| valuebrokerage/value
| valuebundle2/value
| valuebundle3/value
| /core:bundle-names
| /core:resource-loader
|
and you don't need (with above example)
|
EricJava wrote : [EMAIL PROTECTED] wrote : anonymous wrote : If I put just
@Name, it's a POJO, and you're saying it's request scoped?
| |
| | Yes.
|
| Waitaminute, looking at the JBoss Seam book (an official JBoss
publication), by Michael Yuan and Thomas Heute, on page 320:
|
Nope :-)
I like JSF.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4121865#4121865
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4121865
___
jboss-user mailing list
Yes, I have the same problem !
When authenticate fails it is invoked two times - must be a bug?
When authenticate is successful it is invoked one time.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4122046#4122046
Reply to the post :
If you're using IDEA and want IDEA to support JBoss Seam development 100%, then
please vote and/or create a 'New Feature' request.
http://www.jetbrains.net/jira/browse/IDEA/component/10773
Thanks.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4112486#4112486
mirko27 wrote :
| Wouldnt I loose seam management when using @EJB?
|
Yes, you would loose Seam managed transactions.
mirko27 wrote :
| References are there for glassfish, it requires them, doesnt it?
|
Okay, I'm using JBoss AS - I don't have to declare ejb-references :-)
Looks like
Have you tried:
| @EJB
| Facade facadeBean;
|
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4111426#4111426
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4111426
BTW: Why have you declared ejb-references in web.xml?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4111427#4111427
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4111427
___
| package com.mediatorsystems.workoutjournal.service;
|
| import org.jboss.seam.ScopeType;
| import org.jboss.seam.international.LocaleSelector;
| import org.jboss.seam.annotations.*;
| import org.jboss.seam.log.Log;
|
| import javax.ejb.EJB;
| import javax.ejb.Remove;
|
I'm using Seam 2.0.0.CR3.
| /Users/kec/Dev/jboss-4.2.2.GA/bin/shutdown.sh -s jnp://localhost:1099 -S
| 22:56:45,723 INFO [Server] Shutting down the server, blockingShutdown:
false
| 22:56:45,724 INFO [Server] Server exit(0) called
| 22:56:45,725 INFO [Server] Runtime shutdown hook
Congratulations.
Great news.
/Kenneth
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4062261#4062261
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4062261
___
jboss-user mailing
Where can I download the JBoss EL sourcecode?
I can't find it anywhere !
Thanks.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4062653#4062653
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4062653
JIRA created.
http://jira.jboss.org/jira/browse/JBSEAM-1638
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4062757#4062757
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4062757
I really don't know if this problem is a JBoss Seam or/and JBoss Ajax4JSF
or/and JBoss EL issue !
But what I do know, this problem occur only when I'm using JBoss Seam
2.0.0.BETA1 and JBoss Ajax4JSF 1.1.1.
Works fine with JBoss Seam 1.2.1.GA and JBoss Ajax4JSF 1.1.0.
Environment:
JBoss Seam 2.0.0.BETA1 and JBoss Ajax4JSF 1.1.0 have the same problem - as I
mentioned earlier Seam 1.2.1.GA and Ajax4JSF have no problems.
It really looks like an integration issue between Seam 2.0.0.BETA1 and AJax4JSF
!?
View the original post :
[EMAIL PROTECTED] wrote : Oh, this is something I forgot to mention in the
migration guide (Bad on me).
|
| Seam tx management is now enabled by default. You need to use
|
| core:init transaction-management-enabled=false/
|
| to get the old default behavior.
|
| I need to add
I have a stateful session bean with extended persistence context.
Everything works fine with JBoss Seam 1.2.1.GA, but not with JBoss Seam
2.0.0.BETA1 - a 'java.lang.IllegalStateException: Transaction present on server
in Never call' is thrown.
I have two methods with the
I get an unexpected token everytime I'm using s:formattedtext.
Simpel test case:
| s:formattedText value=++a/
|
| 15:57:19,757 ERROR [STDERR] line 1:5: unexpected token: ?
|
'line 1:5' looks a little bit strange, because the '++a' only consist of 3
chars.
Any ideas why I get an
Because it's a RuntimeException I can't tell the user about the problem, e.g.
file is too big. I can only show the user a standard error page :-(
What about a MaxRequestSizeException? If I have MaxRequestSizeException I can
show the user a non-standard error page.
e.g.
| pages
|
[EMAIL PROTECTED] wrote : I cannot reproduce this behavior. If a page action
begins a conversation, everything works just fine for me.
What can I say? Very odd :-)
But now it works fine for me and it also works fine for you, so everybody are
happy :-)
Thanks for your time and help.
View the
An exception is thrown when I hit the database after some time (e.g. 10
minutes):
| 19:23:31,355 ERROR [STDERR] javax.faces.el.EvaluationException:
java.lang.RuntimeException: org.jboss.serial.exception.SerializationException:
Could not create instance of
BTW: This only occurs for 1.2.0 - The EntityManagerProxy don't exist for 1.1.6.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4025565#4025565
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4025565
[EMAIL PROTECTED] wrote : Oooops. Embarrassing bug.
|
| This only happens with @PersistenceContext, right? Not with Seam-managed
PCs, I assume
|
|
At the moment I'm only using @PersistenceContext and @PersistenceContext(type =
PersistenceContextType.EXTENDED).
View the original
[EMAIL PROTECTED] wrote : http://jira.jboss.org/jira/browse/JBSEAM-996
OK - thanks :-)
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4025578#4025578
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4025578
Now it works :-)
Old pages.xml (OK for 1.1.5 and not OK for 1.2.0):
| !DOCTYPE pages PUBLIC -//JBoss/Seam Pages Configuration DTD 1.1//EN
http://jboss.com/products/seam/pages-1.1.dtd;
|
| pages
| page view-id=/xhtml/account/create/agreement.jspx
action=#{accountBean.begin}/
|
The behaviour for pages.xml have changed in 1.2.0 ! Because if I remove
pages.xml everything will work out just fine.
pages.xml:
| !DOCTYPE pages PUBLIC -//JBoss/Seam Pages Configuration DTD 1.1//EN
http://jboss.com/products/seam/pages-1.1.dtd;
|
| pages
| page
holtak wrote : Just loud thinking:
|
| you always get a new (not nested) conversation with seam 1.2PATCH1 and then
@In can`t inject the old instance? And this is not so when you move back to
1.1.5, for some reason...
|
With 1.2.0 and pages.xml I get a new conversation id at each request
Any help please :-)
It's a really big problem for me, that Seam 1.2.0 creates a new instance of
userDomain when an AccountBean method is invoked - for each AccountBean method
call I get a new userDomain instance !
Seam 1.1.5 creates one instance of userDomain and use this instance when an
holtak wrote : What is userDomain? (StatefullBean, StatelessBean,...)
| and what scope is it in? Use debug.seam to check if it is really there
where you want it.
|
| I`ll check the @In (create=true) acting today when I come to coding but
I`ve moved to 1.2PATCH1 from 1.1.5 and don`t have
No comments/help from the people behind JBoss Seam?
It's really strange, because I only replaced the 1.1.5 jar files
(jboss-seam.jar and jboss-seam-ui.jar) with the 1.2.0 files.
Have something changed in the @In @Out behaviour in 1.2.0 or/and in the
bijection implementation?
View the
Ok, I will do some more investigation :-)
User (userDomain):
| @Entity
| @Name(userDomain)
| @Table(name = userx) // user is a reserved word in PostgreSQL
| @Inheritance(strategy = InheritanceType.SINGLE_TABLE)
| @DiscriminatorColumn(name = DISCRIMINATOR, discriminatorType =
| @Stateful
| @Name(accountBean)
| public class AccountBean implements AccountLocal {
| @PersistenceContext
| private EntityManager em;
|
| @In(create = true) @Out
| private User userDomain;
|
| @In(required = false)
| private Locale localeDomain;
I'm using JSF 1.1 RI and the file upload component doesn't work.
It will work just fine if I include the following lines of code in the
FileUpload.decode():
| if (request instanceof HttpServletRequestWrapper) { // Needed for JSF
1.1 RI
| request =
I have two Java Beans, Bean A (scope: session) and Bean B (scope: event). Bean
A is injected
into Bean B. E.g.
Class A {
...
...
...
}
Class B {
protected Object var;
@In(value = ASession, create = true)
void setVar(Object var) {
65 matches
Mail list logo
