hi
thanks for the answer. unfortunately i am really new to jboss and therefore have a little difficulty finding my way around so just to make sure I get it right this time. (I've already spent hours trying to figure it all out)
i guess classloading isolation can be enabled like this:
http://wiki.jboss.org/wiki/Wiki.jsp?page=ClassLoadingConfiguration
for jndi lookup
I have to create a seperate entry into the -ds.xml config file and then have to make the appropriate changes to the persistance*.xml files as well as to the jboss-beans.xml file.
in order to not have conflicting uris i have to probably change the context-root element in the application.xml file
am i missing anything?
thank you for your help
stefan
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4086598#4086598
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4086598
Hi guys,
not sure if this is the right place for this post ... but hope so :)
I am trying to run a Scheduler service (org.jboss.varia.scheduler.Scheduler). I copied the example configuration, so everything should be fine. But I get java.lang.ClassNotFoundException: No ClassLoaders found for xxx. I found out that its probably because my class is not visible from outside. My application is generated by SeamGen and has structure as follows:
ear archive (directory)
- jar archive (directory)
- war archive (directory)
Could anybody give me a hint where to place the .xml with configuration of the scheduler service to be able to see the class inside the jar archive? Thanks for help.
Ps: found some "solution" with setting the Isolation attribute to false, but that didnt solve it for me. Thanks.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4086594#4086594
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4086594
I'm using annotations in my EJB3.0 beans without any deployment XML descriptor. I don't want any deployment descriptor for these beans. Deployment descriptor contains only informations about EJB2.1 beans. Should I also put informations about EJB3.0 beans in the deployment descriptor ?
The real problem is that XDoclet does not understand JAVA5 grammar and it cannot generate deployment descriptor for EJB3.0 beans which use JAVA5-specific features like annotations, generecis, enums.
Marcin
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4086588#4086588
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4086588