A conversation typically lasts longer than the lifetime of a thread, and indeed
the same conversation can be carried through different threads (on different
requests), so I'd say no.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3937835#3937835
Reply to the
You could start with a generic DAO pattern that is just a thin wrapper around
an entity manager, something like the following:
| public interface GenericDao
| {
| public T extends BaseEntity void save (T entity);
|
| public T extends BaseEntity void delete (T entity);
|
|
Can't you do:
@Length (min = 1, max = 500, message = Email address must be between 1 and 500
characters long.)
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3928898#3928898
Reply to the post :
Hi,
I'm looking specifically for examples of usage for wstools and JSR-181. (I
noticed most of the wiki examples still use wscompile.)
Thanks...
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3928079#3928079
Reply to the post :
The way I understand it, this can be handled completely within SEAM. The @Valid
annotation is specific to the Hibernate validator. However, the @IfInvalid is
all SEAM. My variation on the idea is to change @IfInvalid as follows
| @Stateful
| @Name(myController)
|
You're example won't work, because validation is applied to all the fields
marked @Valid.
You might be able to trick it out by setting the field value to null if you
don't want it validated. However, you have to do this *before* the
pressButtonXXX methods are invoked by SEAM, which is tricky.
You might have some luck with the CVS branch. I personally haven't tried.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3926106#3926106
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3926106
What is the table named TERMINE? Does it have relationships with PATH or
PATHTERM?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3925630#3925630
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3925630
What's wrong with using Generic DAOs?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3925463#3925463
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3925463
---
This SF.net
JBossWS is supposed to feature this, but it's not yet ready. Check the JBossWS
forums.
If you're feeling daring, you might have some luck with the latest CVS
source...
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3923986#3923986
Reply to the post :
By the way, webservices with annotations is not a Seam related issue, rather a
JBossWS/EJB3 issue...
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3923987#3923987
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3923987
I have an EAR file set up as follows:
- jar with entity and session beans, annotated with Seam/EJB3. Also has
WsServlet class, which is a regular Hello World servlet, but looks up an SLSB.
- war file that uses Seam/JSF
- another war file that just has a web.xml that defines WsServlet
When I make
[EMAIL PROTECTED] wrote : Enter this in JIRA, and I'll see if this
restriction can meaningfully be relaxed.
Done:
http://jira.jboss.com/jira/browse/JBSEAM-137
I see how this can get tricky... in general, it would be great to have certain
Seam-related annotations (such as @Name, @Scope, @Role/s
I've been trying to gather some information on how to deploy/use webservices on
JBoss and am rather confused... I'm trying to get web services working with
EJB3.
- I take it that JBossWS is not supported in JBoss 4.0.3SP1, however it
apparently works fine in 4.0.4 RC1.
- From the Wiki, there
I've downloaded and installed 4.0.4 RC1 using the graphical installer using the
EJB3 profile. Then following the Wiki, I installed JBossWS. I get this problem
after starting JBoss:
| 19:02:11,406 INFO [Server] Core system initialized
| 19:02:13,171 INFO [Log4jService$URLWatchTimerTask]
http://docs.jboss.com/seam/reference/en/html/index.html
(See chapter 5.4 for relevant text.)
Note that Seam works with JSF, so this doesn't address your problem if you are
required to use Struts.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3922941#3922941
On #2, use a @Length (min = 1) validator.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3923031#3923031
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3923031
---
This
I don't have any composite ID's (aside from join tables). Actually, I'm using a
Hibernate-generated schema. I will try and do the Seam codegen from my set of
Annotated Pojos as well. I'll see if I can narrow down the problem a bit
more...
View the original post :
The new spec by default does not allow mixed field and method access on an
entity, it's mapped superclass and embedded entities. There is a way around
this, if you really want to do it (check the spec).
Before, the @Entity annotation took an AccessType.FIELD or AccessType.METHOD
attribute.
Hi,
I have a few questions regarding EJB3 and webservices...
1) From what I understand JBossWS supports annotation-based declaration to
expose webservice methods, and this works with JBOSS HEAD. As far as
backporting to JBoss 4.0.4, is issue
http://jira.jboss.com/jira/browse/JBAS-2776 the
Wasn't sure whether to post this in Hibernate Tools or the JBoss IDE forums,
but I think here is the best bet...
I'm checking out the CRUD generation capabilities of JBoss IDE. I have JBoss
IDE 1.5 plugin and Hibernate Tools 3.1.0 beta4. I'm also using the Java 1.5 VM.
I can generate the POJOs
Thanks Gavin...
I switched strategies and decided to get 4.0.4 RC1, and that seems to be
working fine with the Seam example code. I am now porting my old Seam code.
Seems fairly straightforward so far, and really very easy when using Eclipse.
For others who might be attempting to check out
I'm now using a CVS snapshot (from 20060203). I've managed to get all my code
compiling with the new EJB3-RC5 stuff.
Some things I don't quite understand:
- what is seam-jndi.properties used for, and where should it go? (.jar or .ear?)
- I noticed that for seam-booking, jboss-seam.jar is
This is such a basic server-side threading construct, the difficulty in
implementing in EJB shows the immaturity of the standard (IMHO).
From what I understand, however, they might try to get asynchronous EJB3 calls
in the next iteration (3.1) of the spec.
In the meantime, if you don't mind
Hey all,
I checked out the code from CVS using the JBoss_4_0_4_RC1 branch... (with
CVSROOT=:pserver:[EMAIL PROTECTED]:/cvsroot/jboss).
Ran build.sh, and got up to this error:
| configure:
| Overriding previous definition of reference to xdoclet.task.classpath
|
| BUILD FAILED
|
I've got JBoss 4.0.3SP1 from the zip distribution, and I've copied the EJB3
RC5-PFD jars into the server/all directory, as per Bill Burke's doc and ran
using run.sh -c all... so far so good.
Downloaded a Seam CVS snapshot, jboss-seam-CVS20060203.zip... unzipped, built
and deployed the sample
You can most definitely get the annotations via the Class object (then fall
back to the decapitalized className if the annotation parameter is missing).
Or you can dig through the EJB3 source code to find the method used by the
mapping generator.
View the original post :
Hi,
I'm still on JBoss 4.0.3, EJB3 (pre-PFD) and Seam Beta 1... I want to convert
my code and environment to the new stuff. However, I'm reluctant to double my
efforts if the new JBoss and Seam releases are coming in a week or two. What's
the word on this? Thanks!
View the original post :
SunFire,
Nice work. As for taking out the LoggedIn interceptor, I wonder if using a
servlet filter could do the same trick. This at least frees you of using the
@LoggedIn annotation. Another thing is that you don't have to rely on a backing
bean instantiation for the User to make it into the
It's not that simple... there's two security concerns here:
1. Web Security, which restricts access based on URL
2. EJB Security which restricts access to EJBs and methods.
If you're using the JSF/Seam/EJB3 stack simply for web applications, then Web
Security is enough and EJB security is
I haven't actually tried this, but it seems that it should be possible to use
POJOs as seam components without annotating them with @Name and @Scope.
Just a simple:
@In (value = contextName)
SomeClass context Name;
Also, it would be nice to have the field's name used as the default for the
Probably not a good idea to scope SFSB to session. You could create a search
result object (a real POJO, not an Entity Bean, unless you want to persist your
search results which sounds crazy) and put that in the session scope.
View the original post :
I have some wizards which basically null out the appropriate form beans and put
them back in when it's on the right screen.
This doesn't solve your problem though, as you have no idea in advance which
form will get submitted.
Maybe as an alternative, create a @ValidateFor (names = {seamName1,
This could also fold in the @IfInvalid annotation:
@ValidateFor (names = {seamName1, name2}, invalidOutcome = REDISPLAY)
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3912487#3912487
Reply to the post :
Maybe I'm missing something, but it still seems to me that your problem is
easily handled by context variables and view mappings. I assume you are using a
standard MVC architecture?
You are not limited to just failure and success outcomes... and the event
that is fired (the method invocation)
Seems weird...
First of all, it won't be freed up until the session is invalidated or the app
takes it out of the session context. Then, I'm not too sure how it will behave
wrt activation/passivation.
I think the web layer also does its own bit of passivation/activation and
writes objects in
Seam doesn't support multiple nested conversations at this point.
So for now you have two choices:
1. search query in conversation scope, edit on event scope.
2. search query and edit in the same conversation scope.
View the original post :
Typically, persistent entities are placed in a context (application, session,
conversation or event/request) during the InvokeApplication phase.
The render response will then have access to these entities. It may or may not
hit the database to render the page, depending on whether the entities
In/Out takes things in and out of the various contexts (application, session,
conversation and event/request).
The get/set stuff you pointed out does much the same thing but it does it on
your backing bean. So the lifecycle of that variable depends on the backing
bean itself.
In general, I
Just a thought... I do not know enough about the Hibernate internals to
determine if this is a viable solution, but it seems to me that Lazy loading of
detached objects is a concern best addressed by Hibernate itself.
Would it be possible to modify hibernate (at the cache, Proxy, Session or
That problem isn't really handled by the seam layer, but by Hibernate or EJB3.
However, you might find that because you don't have to derive from ActionForms
anymore, your entities (Order, Person, etc.) can be used to hold form data on
the JSF layer, so alot of the glue code goes away...
View
Conversations are closely tied to business logic, and there can be many
different kinds of conversations. For example, a search result conversation
might have a longer timeout than a user registration wizard conversation
does it make sense to have a per-conversation timeout parameter?
View
JIRA issue here:
http://jira.jboss.com/jira/browse/JBSEAM-113
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3911276#3911276
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3911276
I want to start a discussion on security implementation.
The final stumbling block for me in the entire JSF/Facelets/SEAM/EJB3/JBoss
stack is the security aspect. JAAS is a big hairy beast and is probably
overkill for most web applications, and JSF doesn't seem to play well
out-of-the-box with
anonymous wrote : EJB3 interceptors give you the potential to define a
declarative security model on top of any underlying security infrastructure you
like.
Yep. Which is why I thought SEAM (which uses servlet filters and ejb3
interceptors) might be an ideal place to provide an easy to use
Some info on Embeddable EJB3:
http://docs.jboss.org/ejb3/embedded/embedded.html
Be warned that it's still in alpha, so I doubt it'll be production ready in 6
months.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3911300#3911300
Reply to the post :
anonymous wrote : * reverse engeneering tool (from database to Seam webapp !
(CRUD
| operations ) Thank you Max !
Awesome... is there sample code available on this?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3910749#3910749
Reply to the post :
@In(name=currentUser, create = true)
User currentUser;
etcetera...
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3910568#3910568
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3910568
What's the best way to implement the EJB3 equivalent of a non-blocking function
to execute long-running jobs requested by multiple clients? (Normally for J2SE
one could use a singleton object that implements Runnable.)
I know JBoss has extensions that allow a client to make asynchronous calls
Are these not available in the standard distributions?
My jboss-ejb3.jar has these:
org/jboss/ejb3/mdb/ActivationSpec.class
org/jboss/ejb3/mdb/ConsumerContainer$1.class
org/jboss/ejb3/mdb/ConsumerContainer$ExceptionListenerImpl.class
org/jboss/ejb3/mdb/ConsumerContainer$MessageListenerImpl.class
Apologies...
It's just that I'm using EJB3, but I really haven't seen much info on EJB3
style usage of MDBs (i.e., avoiding xml config descriptors) on the EJB3 Forums
and Wiki, so I thought this might be the proper forum.
View the original post :
I'm relatively new to EJB, esp. MDBs.
I looked at Bill Burke's Consumer/Producer example, and noticed that status is
held in static public fields of a SLSB (TestStatusBean), which is looked up
by the client via JNDI.
Is there a cleaner pattern to do this that can also work for multiple client
I was more interested in controlling the flow of application logic, but if
you're saying JMX can help me out with that, I guess I'll look into it.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3907736#3907736
Reply to the post :
The annotations seem to get rid of alot of XML that I see with EJB2.1 based
security configuration examples. I have a few additional questions...
1. Would the client code be much different if it was a web app (war file
running in JBoss)?
2. As for the conf/login-config.xml, it looks like I can
Probably the best you can do is to obfuscate the code. They can still reverse
engineer it, but it would be much harder. (Hopefully, to the point where it'd
be much easier for them to code it from scratch than to re-use your code.)
View the original post :
One more newbie question :)
4. Does JAAS (or some other JBoss security mechanism) allow for owner
permissions, like if I am a Customer, I can only modify my Address, etc.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3907206#3907206
Reply to the post :
Can anyone point to any examples on how to use the JAAS framework with EJB3?
Preferably using RDBMS backed authentication...
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3907124#3907124
Reply to the post :
I'm seeing this problem on 4.0.3SP1 with PostgreSQL 8 and HSQL as well.
I'm not sure if it's a Hibernate issue or a JBoss classloading issue.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3904728#3904728
Reply to the post :
58 matches
Mail list logo
