[JBoss-user] [Installation Configuration] - Re: loader repository problem

2004-07-22 Thread [EMAIL PROTECTED]
The call-by-value element was not being read correctly. This is simply a shortcut for 
specifying the call by value invoker interceptor stack. This example from the 
testsuite shows the custom call-by-value-jrmp invoker-proxy-binding that serializes 
calls between components:


  | ?xml version=1.0 encoding=UTF-8?
  | 
  | jboss
  |enterprise-beans
  |   session
  |  ejb-nameCalleeSessionBean/ejb-name
  |  jndi-nameejbcts2/CalleeSessionHome/jndi-name
  |  invoker-bindings
  | invoker
  |
invoker-proxy-binding-namecall-by-value-jrmp/invoker-proxy-binding-name
  | /invoker
  |  /invoker-bindings
  |   /session
  |/enterprise-beans
  | 
  |invoker-proxy-bindings
  |   invoker-proxy-binding
  |  namecall-by-value-jrmp/name
  |  invoker-mbeanjboss:service=invoker,type=jrmp/invoker-mbean
  |  proxy-factoryorg.jboss.proxy.ejb.ProxyFactory/proxy-factory
  |  proxy-factory-config
  |client-interceptors
  |   home
  |  interceptororg.jboss.proxy.ejb.HomeInterceptor/interceptor
  |  interceptororg.jboss.proxy.SecurityInterceptor/interceptor
  |  interceptororg.jboss.proxy.TransactionInterceptor/interceptor
  |  
interceptororg.jboss.invocation.ByValueInvokerInterceptor/interceptor
  |   /home
  |   bean
  |  
interceptororg.jboss.proxy.ejb.StatelessSessionInterceptor/interceptor
  |  interceptororg.jboss.proxy.SecurityInterceptor/interceptor
  |  interceptororg.jboss.proxy.TransactionInterceptor/interceptor
  |  
interceptororg.jboss.invocation.ByValueInvokerInterceptor/interceptor
  |   /bean
  |/client-interceptors
  |  /proxy-factory-config
  |   /invoker-proxy-binding
  |/invoker-proxy-bindings
  | 
  | /jboss
  | 
  | 

View the original post : 
http://www.jboss.org/index.html?module=bbop=viewtopicp=3842904#3842904

Reply to the post : 
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3842904


---
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721alloc_id=10040op=click
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user


[JBoss-user] [Installation Configuration] - Re: loader repository problem

2004-07-21 Thread wtff
Thanks a lot for your support. Meanwhile I figured out the reason for the exception: 
there was a j2ee.jar somewhere within a subdirectory of my ejb-archive. I thought that 
jboss would only grap jar files located at the root level directory of a jar or ear...

Isolating deployments from one another works well now.

Thanks as well for the artical you posted. 
Yes, I have the need to let several isolated deployments talk to one another.
I tested the approach from the artical and it worked, however, I'm not satisfied with 
the approach proposed there.
I would have thought that one could achieve the same with the following packaging 
structure for the scenario of invoking an EJB in scoped ear A from within a scoped ear 
B:

scoped ear A
  Implementation class of EJB ONE
  Interface classes of EJB ONE

scoped ear B
  other EJBs, Wars..
  Interface classes of EJB ONE
 
However this doesn work.
I also tried setting the call-by-value field to true within the EJB jar but it still 
didn't work.

Even with the approach mentioned in the artical, I wonder how this sort of bean 
communication works in clustered environments?

Isn't there a way to configure JBoss to handle Bean invocations without needing to 
instantiate classes for his own use? The only classes to be shares by applications are 
the interface classes.
If Jboss created Dynamic Proxy classes for all ejb interface classes for all ejbs 
referenced from ejb-ref or ejb-local ref elements within a scoped ear and then let 
these proxy classes speak to the bean proxy class registered within the JNDI context, 
it should be possible to completely prevent classloading issues because the JBoss 
proxy classes could be made to communicate with another using a loosely coupled 
serialization mechanism - at least as a special case for cross communication between 
isolated deployment units.

If this cannot be made to work, we would have to switch towards XML communication 
between different deployment units, but it would be much nicer if this could be done 
transparently.

View the original post : 
http://www.jboss.org/index.html?module=bbop=viewtopicp=3842858#3842858

Reply to the post : 
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3842858


---
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721alloc_id=10040op=click
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user


[JBoss-user] [Installation Configuration] - Re: loader repository problem

2004-07-15 Thread wtff
well, the warning about only the root deployer being allowed to set the 
loader-repository goes away, but the error remains. Stack trace looks the same to me, 
here are the first lines:

2004-07-15 12:41:41,498 INFO  [org.jboss.deployment.EARDeployer] Init J2EE 
application: file:/blabla/jboss325/server/default/deploy/apps/test3.ear/
2004-07-15 12:41:41,998 INFO  [org.jboss.ejb.EjbModule] Deploying Test
2004-07-15 12:41:42,217 ERROR [org.jboss.ejb.StatelessSessionContainer] Initialization 
failed jboss.j2ee:jndiName=java%3aejb/Test,service=EJB
java.lang.ClassCastException
at 
org.jboss.ejb.plugins.local.BaseLocalProxyFactory.getEJBLocalHome(BaseLocalProxyFactory.java:210)
at org.jboss.ejb.Container.createService(Container.java:581)
at 
org.jboss.ejb.StatelessSessionContainer.createService(StatelessSessionContainer.java:133)
at 
org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:237)


Let me also mention the following:

- if the EAR only contains a war archive and the bean is its own top-level deployment 
unit, setting a loader-repository within the EAR does not cause the error. However, I 
would like to have EARs containing EJBs and having their own loader-rep.

- on the one hand, what I understand from the (purchased) jboss documentation is that 
setting the loader-rep within the jboss-app descriptor sets this loader for all 
subcomponents within this ear. On the other hand the jboss-web and jboss descriptors 
also allow for the specification of a loader-rep, so I tried to play around with this 
feature as well. 

- when I download jboss3.2.5, extract it and start it without having made any 
modification to it, it would also give me a warning about only root deployers being 
allowed to set a loader-rep:
2004-07-15 12:47:29,643 INFO  [org.apache.catalina.startup.Catalina] Server startup in 
110 ms
2004-07-15 12:47:29,768 WARN  [org.jboss.deployment.DeploymentInfo] Only the root 
deployment can set the loader repository, ingoring config=null
2004-07-15 12:47:29,783 INFO  [org.jboss.web.tomcat.tc5.TomcatDeployer] deploy, 
ctxPath=/invoker, 
warUrl=file:/blabla/jboss325/server/default/deploy/management/http-invoker.sar/invoker.war/

- I'm no novice to J2EE. The company I'm working for is using Jboss to run several 
EARs covering all of J2EE: JMS, JCA, JDBC, all EJB types etc.
Now I'm trying to investigate four features that are becoming more and more crucial to 
us:
   - we need to be able to isolate the EARs from one another 
   - we need to be able to specify alternative deployment descriptors within
 the application.ear archive
   - we need to be able to reload an EJB without having to reload all other deployment 
units that depend on it. 
   - we would like to be able to deploy several different 
 ejb-implementation-classes for the same ejb-home and 
 ejb-object interface

However, I can get NONE of the above usecases to work. No matter how hard or how long 
I try. 

I know that the JBoss group offers commercial support. What my team needs whout be to 
submit detailed descriptions of the above use-cases to a JBoss support agent and get 
back one simple hello-world example application per use-case, showcasing that the 
JBoss server is actually capable of fullfilling the specified requirements of the 
respective use-case.

View the original post : 
http://www.jboss.org/index.html?module=bbop=viewtopicp=3842196#3842196

Reply to the post : 
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3842196


---
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721alloc_id=10040op=click
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user


[JBoss-user] [Installation Configuration] - Re: loader repository problem

2004-07-15 Thread jae77
you should definately read this wiki page: 
http://www.jboss.org/wiki/Wiki.jsp?page=HotDeployClassCastExceptions

some of the information contained w/in will be relevant to you. can you send me the 
ear you're working w/ (jgangemi at yahoo dot com) and i'll take a look at it locally. 

also, are you planning on having any of these isolated ears communicate w/ each other? 

View the original post : 
http://www.jboss.org/index.html?module=bbop=viewtopicp=3842249#3842249

Reply to the post : 
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3842249


---
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721alloc_id=10040op=click
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user


[JBoss-user] [Installation Configuration] - Re: loader repository problem

2004-07-14 Thread wtff
the descriptor fragments above are not being display correctly.
Second try:

---
  | 
  | application.xml
  | 
  | application
  | display-nameTest Application/display-name
  | module
  | ejbtest.jar/ejb
  | /module
  | /application
  | 
  | ---
  | jboss-app.xml
  | 
  | jboss-app
  | loader-repositorywhatever:loader=test/loader-repository
  | /jboss-app
  | 
  | ---
  | ejb-jar.xml
  | 
  | ejb-jar
  | description-/description
  | display-nameTest Component/display-name 
  | enterprise-beans
  | session
  | description-/description
  | display-nameTest Component/display-name
  | ejb-nameTest/ejb-name
  | local-hometest.TestHome/local-home
  | localtest.Test/local
  | ejb-classtest.TestEJB/ejb-class
  | session-typeStateless/session-type
  | transaction-typeContainer/transaction-type
  | /session
  | /enterprise-beans
  | /ejb-jar
  | 
  | ---
  | jboss.xml
  | 
  | jboss
  | loader-repositorywhatever:loader=test/loader-repository
  | /jboss
  | 
  | ---

View the original post : 
http://www.jboss.org/index.html?module=bbop=viewtopicp=3842070#3842070

Reply to the post : 
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3842070


---
This SF.Net email sponsored by Black Hat Briefings  Training.
Attend Black Hat Briefings  Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user


[JBoss-user] [Installation Configuration] - Re: loader repository problem

2004-07-14 Thread jae77
look at the error message that was thrown w/ the exception.

you only define the loader-repository tag inside the jboss-app.xml file. you need to 
remove that entry from the jboss.xml file that is packaged w/ your ejb. 

View the original post : 
http://www.jboss.org/index.html?module=bbop=viewtopicp=3842084#3842084

Reply to the post : 
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3842084


---
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721alloc_id=10040op=click
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user


[JBoss-user] [Installation Configuration] - Re: loader repository problem

2004-07-14 Thread wtff
thanks for your reply, but I tried this as well and it doesn't work either.

If I leave the jboss file out nothing changes.

that is what is puzzling me so hard. I've created the smallest possible application 
which runs perfectly and just  by adding the loader-repository fragment to the 
jboss-app.xml I can make it crash during deployment. 


View the original post : 
http://www.jboss.org/index.html?module=bbop=viewtopicp=3842092#3842092

Reply to the post : 
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3842092


---
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721alloc_id=10040op=click
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user


[JBoss-user] [Installation Configuration] - Re: loader repository problem

2004-07-14 Thread jae77
what is the new error that you get? if you removed the jboss.xml file and you aren't 
duplicating the load-repository definition anywhere else, i would think you'd also be 
getting a new error.

View the original post : 
http://www.jboss.org/index.html?module=bbop=viewtopicp=3842108#3842108

Reply to the post : 
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3842108


---
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721alloc_id=10040op=click
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user