any news on that ? I also plan to use it and my first tests faild as yours
although other tomahawk components work without problems ...
thx
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3930582#3930582
Reply to the post :
unfortunatelly it did not fork ...
I tried both
@EJB(beanName=CurrencyServiceSessionBean)
protected ContractService contractService
as well as
@EJB(beanName=CurrencyService)
protected ContractService contractService
end up in the same exception ...
View the original post :
yes - its within an ear-file (see message 3:23 AM). To be more exact its part
of a SEAM implementation. Maybe I can write a small patch within the booking
example of SEAM - but I am not sure if I can reproduce it there ...
So please tell me first, that ears should work and I will try to make a
I was able to reproduce the problem - and delivered a patch for seams booking
example - for simplicity and file-size
http://jira.jboss.com/jira/browse/EJBTHREE-476
hope that helps
thx
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3930414#3930414
Reply to
I have disabled my RemoteIntercface for testing purposes - thought there might
be the problem !
Now I have just a local interface ...
Might it be that I deploy within a ear-file ? I somewhere read that this causes
troubles. But all my classes are in one jar file within the ear-file ...
View
sorry - didn't answer your question ...
yes - its the local interface
...
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3929689#3929689
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3929689
I have a stateful seam component and want to inject a stateless SessionBean but
at deployment I get the following exception. It seams as if I have got a
problem with jndi names, but have no clue what's wrong.
(without @EJB I can deploy).
The error tells me already the right class - but what does
sorry - wasn't sure if it depends also on seam - because I thought the simple
@EJB would work ...
by the way - I have been able to access the SessionBeen using standard lookup
facilities -- which means my services are working correctly - only I don't
know what's wrong with @EJB
here is the
I have a stateful sessionbean and want to inject a stateless SessionBean using
@EJB-injection, but at deployment I get the following exception. It seams as if
I have got a problem with jndi names, but have no clue what's wrong.
(without @EJB I can deploy).
The error tells me already the right
is there anywhere a simple example to have a look at ?
thx
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3929256#3929256
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3929256
I have a stateful session bean managing a seam-conversation injecting several
JavaBeans with ScopeType=CONVERSATION. It must somehow depend on this
combination because I could never reproduce this with the booking-example. I am
using the login-files from the booking example so I should be
found that stupid bug - to my shame - it was a copy-past error.
For all who do the same stupid thing:
copied LoggedInInterceptor into my project. This class returns login as the
navigation-case - which was renamed in my project. Thus the login-page was not
found and lead to this exception ...
oh yes - thank you I was already in doubt about my english ;-)
what you say is exactly what I tried to express and I have already tested this
approach in the very beginning - but this is not working !
| ...
|
| @In(value=myBean, required=false)
| protected MyBean
ok - here is some results from testing ...
case 1
anonymous wrote :
| @In(required=false)
| +
| @Factory
|
throws no exception, but initial value is not set !
case 2
anonymous wrote :
| @In(required=false) @Out
| +
| @Factory
|
throws an exception, telling me the out-value
maybe the question is stupid, but how can I predefine a beans value to show it
the first time a page is called as a default-value
I tried the folowing but without success:
| @Name(myBean)
| @Scope(ScopeType.CONVERSATION)
| public class MyBean {
|
| private String
tried to do it but that doesn't work. I thought the @Factory specifies that the
method of the component is used to initialize the value of the named context
variable, when the context variable has no value -- which means myBean == null
(please correct me if I am wrong). But myBean is already
just tried inputSuggestAjax - nearly-works, but get nullpointerexception when
calling remote-method.
I believe it is because seam manages its objects invisible for jsf - thus the
ControllerBean bean is not found by the ajax-implementation.
somewhere in the forum there is a tip from Gavin how
No - that won't work !
(1) I need the injection of myBean, because it holds the values of the form. If
I remove the @In-annotation I have no access to the beanValues filled from the
jsf-form within my controller !
(2) Assume you have a @Valid annotation for your bean for childvalidation. If
sorry again, but still the problem is not solved !
(1) In seam-examples the @Factory method is always used with @DataModel - that
works perfect - but there is no example where you want to set values of a
injected bean !
(2) Adding a @Create in the bean is possible, but it changes the
you can deploy a so called exploded ear file - just unzip the ear file and
deploy it as a directory with the same name as the zipped ear-file !
then you can directly make changes in your jsp/jsf/html/... files - but don't
forget to move your changes back into your development-tree - because its
I haven't tried it for over a year now! Maybe its fixed already. The problem
was: when redeploying several times a huge ear-file you get this nasty
OutOfMemoryException - tried everithing with Xms,Xmx, PermSpace etc. but
nothing helped. So in the ide it had the effect that also eclipse-memory
as far as i know there is a running jira entry for the OutOfMemoryProblems
JBAS-1319. If this on is fixed - I assume also the ide will have no problems
any more ...
I will try it as soon as i have a little bit more time
cheers - for all the good things we get from jboss-group !!!
View the
ahh - forgot to update the forum - i added the patch to jira-135, give me
feedback if the patch itself works ... you need the latest cvs and can then use
the @IfInvalid-patch, that also includes the validate-patch ... at least it
worked for me ;-)
View the original post :
nevertheless you are right - I firstly also thought we can put it into the
HibernateValidator - but that is wrong ! Hibernate has no idea about the
@IfInvalid-annotation - thus it can not be handled there ...
Thats why I added a separate SeamClassValidator that is managing the combined
anonymous wrote : Your patch mix and match Seam and Validator notions.
I don't understand what you mean ...
anonymous wrote : But it is doable to filter the validation mechanism by
passing a list of specific path to test.
|
Does it mean you will more or less take over the loop via the list
any idea is welcome - currently i don't see a simpler solution, but I think
functionality like that is needed as the example shows ...
consider we have 100 buttons in the frontend - do we really need 100
Controllers in the serverside - just for validation ?
As I said - any better idea than
well it's done - I made a patch now using jira-135 patch from Marvin van
Schalkwyk who implemented a plugabble factory for custom validations ...
I tried to derive from hibernates ClassValidator but without success - too many
private variables and procedures ...
Thus created a
you are right - sometimes its better and easier to have a controller for each
button, but sometimes not !
What if you want the actions to interact on shared variables ? So you would
have to introduce a number of interfaces and classes for a simple interaction
of two business-actions ...
I
cheers - great idea - i would also love to have this flexibility ...
what you suggest is to setup validation-groups that can individually be
triggerd with the @IfInvalid annotation.
I had a look at the sources, and what I saw is, that this change would not only
be part of seam but also reflect
yes, looks nice but regarding sources - seam is just using the @IfInvalid
annotation to trigger the hibernate-validation. Unfortunatelly all the loops
take place in the hibernate-code where all @Valid flags are processed - there
our new nice @IfInvalid-syntax is not known ;-)
Gavin - you are
I had the same troubles, but I am not sure if it is really a seam problem or
more a faclets problem !
If you have a look at the faclets documentation there is a sentence telling you
that templates are loaded relativly - meaning it will be loaded relativly from
the directory where you are == so
I have created a page with two forms. Both form buttons are calling two
actionMethods in the same statefull session bean on the server. The stateful
session bean injects two entities with the @In and @Valid statement for
childbeanvalidation.
Here I try to reduce my case for simplicity ...
sorry - simplified too much - I lost the @IfInvalid-annotations ;-)
here is the code again ...
| @Stateful
| @Name(myController)
| @Interceptors(SeamInterceptor.class)
| public class MyController {
|
| // this entity will be set from form-1
|
you are right - security in financial area is always designed like that, that
the web-tier must be (physically) seperated from the business-tier. running
jboss as well as tomcat + business-tier in the same security-zone is usually
not allowed. Usuallay the web-tier should also not have direct
Hmmm - I just know this security policy from several different banks I worked
for - may be there is also different approaches.
In other words it is not important whether we think if the security is better
or not - there are banks that believe in that way of security. So we should
take that into
the same happens when you remove e.g. the entry
| loginUser=Username
|
from the store.properties in the dvd-store-demo
again i get an exception instead of a warning that the resource-entry is
missing ...
Is it a problem of seam, jsf or faclets ? It seems to be in the renderkit of
yes they are ! if I insert the message-key into the properties file I see the
correct message
...
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3924755#3924755
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3924755
woud be great - I think that will solve my problem - see other thread
anonymous wrote : help customizing resourcebundle
what happens if one of the property-entries is missing ? Do you get an
exception or a usefull error-handling ?
View the original post :
I know the mistake ! I have removed a property-file-entry for
internationalization. The point is that, there shouln't be that exception, but
a smooth error-handling - like e.g.:
missing key entry: UserName as it is e.g. in the issue-tracker-demo of seam.
If you remove any entry from the
Is there a way to configure MessageResource instances with desired
characteristics ?
e.g. in struts there is a MessageResourceFactory where a special instance of a
resourceBundle can be given to the web-fontend perhaps to handle missing keys
more elegantly than throwing a
Tested it with issue-tracker example: I just removed the message-entry home and
get a nice errorMessage on the screen:
MISSING: Home :MISSING
afterwards I put the same 2 lines into the booking example:
f:loadBundle basename=messages var=msg/
| ...
| h1h:outputText value=#{msg.Home}//h1
41 matches
Mail list logo