hi alesj ..
if i post you a properly logfile ...
and provide you some excerpts of the code ..
would you be able to help me solving the problem ..
fact for me is:
1. my spring package gets properly deployed during deployment..
implementing the ApplicationContextAware interface in my
My fault .. sorry ..
forgot to add this magic line:
@Interceptors(SpringLifecycleInterceptor.class)
greetings and thanks for your patience
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4062905#4062905
Reply to the post :
:-)
Initially I've used AOP interceptor defined in ejb3-interceptors-aop.xml (or
some similar name).
So I didn't have to worry about setting this EJB3 style interceptor.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4062908#4062908
Reply to the post :
sorry .. badly explained ..
tow scenarios:
1. the target bean is directly embedded into the jboss-spring.xml looking like:
bean id=catalogService class=foo.bar.service.DefaultCatalogService\
everything works fine here ... of course .. as its the described way ..
2. the bean is referenced
I understand a bit more ...
Weird, don't know what the deal is with the proxy.
You can still try separating the catalog beans with parent-child architecture.
This is supported by SpringDeployer - see the instructions for setting this
hierarchy.
View the original post :
thanks for the help alesj ...
I was setting up a prototype to investigate if a spring application which
resides and runs in a catalina container could be easily moved and embedded
into a plain jboss application server .
Development and testing of services in tomcat environment is faster and
loumaus wrote :
| Anyways .. thanks for your help and congrats for this impressive approach
to embed spring into jboss
|
NP. Thanks for trying it out.
Be sure to check out the impressive features we have installed for you with new
Microcontainer 2.x - new Spring-int module and a lot lot
well .. still not giving it up ..
my jboss-spring.xml looks like the following
| beans
| ..
| ..
| bean id=catalogDao class=foo.bar.dao.DefaultCatalogDao /
|
| bean id=catalogService
class=foo.bar.service.DefaultCatalogService
| property name=catalogDao
loumaus wrote :
|
| | property name=catalogDao ref=catalogDao/
| |
|
What about if you change to this:
| property name=catalogDaoref local=catalogDao/property
|
Since this is _not_ a SpringDeployer problem, it's a plain Spring problem.
View the original post :
mmmhhh
| bean id=catalogService
class=foo.bar.service.DefaultCatalogService
| property name=catalogDao
| ref local=catalogDao/
| /property
| /bean
|
does not work as well ..
I already removed the autowire=byType attribute as
What happens?
I don't see what is this catalogBean that 'solved' the problem?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4061096#4061096
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4061096
11 matches
Mail list logo
