You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "David Jencks (JIRA)" <de...@geronimo.apache.org> on 2005/01/26 07:44:17 UTC
[jira] Created: (GERONIMO-552) Put the gbeandatas in a deployment context in a queriable container and use queries to resolve links
Put the gbeandatas in a deployment context in a queriable container and use queries to resolve links
----------------------------------------------------------------------------------------------------
Key: GERONIMO-552
URL: http://issues.apache.org/jira/browse/GERONIMO-552
Project: Apache Geronimo
Type: Improvement
Components: deployment
Versions: 1.0-M3
Reporter: David Jencks
Assigned to: David Jencks
GBeans in a DeploymentContext should be kept in a queriable registry like the BasicGBeanRegistry, but for GBeanData rather thand GBeanInstance. ejb-links, resource-links, gbean-links, etc should be resolved by querying this registry rather than more special purpose tracking. This should simplify RefContext considerably. This feature is needed so that if the mail gbean is deployed in a j2ee module (such as an app client) it can be used in that same module.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
Deployment Failed
Posted by Earathou Berdin <eb...@exist.com>.
Hi! I followed the steps in deploying the sample from:
http://www-128.ibm.com/developerworks/opensource/library/os-ag-deploy/
but I encounter errors like:
Deployment failed
Server reports: Unable to create GBean from class EchoServer
org.apache.geronimo.deployment.DeploymentException: Unable to create
GBean from
class EchoServer
at
org.apache.geronimo.deployment.service.GBeanBuilder.<init>(GBeanBuild
er.java:54)
at
org.apache.geronimo.deployment.service.GBeanHelper.addGbean(GBeanHelp
er.java:31)
at
org.apache.geronimo.deployment.service.ServiceConfigBuilder.buildConf
iguration(ServiceConfigBuilder.java:116)
at
org.apache.geronimo.deployment.service.ServiceConfigBuilder$$FastClas
sByCGLIB$$9f173be6.invoke(<generated>)
at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:87)
at
org.apache.geronimo.gbean.jmx.FastMethodInvoker.invoke(FastMethodInvo
ker.java:38)
at
org.apache.geronimo.gbean.jmx.GBeanMBeanOperation.invoke(GBeanMBeanOp
eration.java:142)
at
org.apache.geronimo.gbean.jmx.GBeanMBean.invoke(GBeanMBean.java:823)
at
org.apache.geronimo.gbean.jmx.RawInvoker.invoke(RawInvoker.java:89)
at
org.apache.geronimo.gbean.jmx.RawOperationInvoker.invoke(RawOperation
Invoker.java:34)
at
org.apache.geronimo.gbean.jmx.CGLibMethodInterceptor.intercept(CGLibM
ethodInterceptor.java:112)
at
org.apache.geronimo.deployment.ConfigurationBuilder$$EnhancerByCGLIB$
$7a1ca0ae.buildConfiguration(<generated>)
at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:174)
at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:60)
at
org.apache.geronimo.deployment.Deployer$$FastClassByCGLIB$$734a235d.i
nvoke(<generated>)
at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:87)
at
org.apache.geronimo.gbean.jmx.FastMethodInvoker.invoke(FastMethodInvo
ker.java:38)
at
org.apache.geronimo.gbean.jmx.GBeanMBeanOperation.invoke(GBeanMBeanOp
eration.java:142)
at
org.apache.geronimo.gbean.jmx.GBeanMBean.invoke(GBeanMBean.java:844)
at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(Unknown
Source)
at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(Unknown Source)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(Unknown
Source)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(Unknown Source)
at org.apache.geronimo.kernel.Kernel.invoke(Kernel.java:288)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.sun.jmx.mbeanserver.StandardMetaDataImpl.invoke(Unknown
Source)
at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(Unknown Source)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(Unknown
Source)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(Unknown Source)
at
javax.management.remote.rmi.RMIConnectionImpl.doOperation(Unknown Sou
rce)
at
javax.management.remote.rmi.RMIConnectionImpl.access$100(Unknown Sour
ce)
at
javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run
(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at
javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(U
nknown Source)
at javax.management.remote.rmi.RMIConnectionImpl.invoke(Unknown
Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
at sun.rmi.transport.Transport$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source)
at
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown Sour
ce)
at java.lang.Thread.run(Unknown Source)
Caused by: org.apache.geronimo.gbean.InvalidConfigurationException:
Could not lo
ad class EchoServer
at
org.apache.geronimo.gbean.GBeanInfo.getGBeanInfo(GBeanInfo.java:51)
at
org.apache.geronimo.deployment.service.GBeanBuilder.<init>(GBeanBuild
er.java:52)
... 48 more
Caused by: java.lang.ClassNotFoundException: EchoServer
at java.net.URLClassLoader$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at
org.apache.geronimo.gbean.GBeanInfo.getGBeanInfo(GBeanInfo.java:49)
... 49 more
[jira] Closed: (GERONIMO-552) Put the gbeandatas in a deployment context in a queriable container and use queries to resolve links
Posted by "David Jencks (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-552?page=all ]
David Jencks closed GERONIMO-552:
---------------------------------
Resolution: Fixed
EJB refs implemented via querying
geronimo:
Sending trunk/modules/assembly/src/plan/j2ee-deployer-plan.xml
Sending trunk/modules/assembly/src/plan/j2ee-runtime-deployer-plan.xml
Sending trunk/modules/client-builder/src/java/org/apache/geronimo/client/builder/AppClientModuleBuilder.java
Sending trunk/modules/connector-builder/src/test/org/apache/geronimo/connector/deployment/ConnectorModuleBuilderTest.java
Sending trunk/modules/j2ee/src/java/org/apache/geronimo/j2ee/j2eeobjectnames/NameFactory.java
Sending trunk/modules/j2ee-builder/src/java/org/apache/geronimo/j2ee/deployment/EARContext.java
Sending trunk/modules/j2ee-builder/src/java/org/apache/geronimo/j2ee/deployment/EJBReferenceBuilder.java
Sending trunk/modules/j2ee-builder/src/java/org/apache/geronimo/j2ee/deployment/RefContext.java
Sending trunk/modules/j2ee-builder/src/java/org/apache/geronimo/j2ee/deployment/UnavailableEJBReferenceBuilder.java
Sending trunk/modules/j2ee-builder/src/test/org/apache/geronimo/j2ee/deployment/EJBRefContextTest.java
Sending trunk/modules/j2ee-builder/src/test/org/apache/geronimo/j2ee/deployment/MockEJBConfigBuilder.java
Sending trunk/modules/jetty-builder/src/java/org/apache/geronimo/jetty/deployment/JettyModuleBuilder.java
Sending trunk/modules/jetty-builder/src/test/org/apache/geronimo/jetty/deployment/JettyModuleBuilderTest.java
Sending trunk/modules/naming-builder/src/java/org/apache/geronimo/naming/deployment/ENCConfigBuilder.java
Sending trunk/modules/tomcat-builder/src/java/org/apache/geronimo/tomcat/deployment/TomcatModuleBuilder.java
Sending trunk/modules/tomcat-builder/src/test/org/apache/geronimo/tomcat/deployment/TomcatModuleBuilderTest.java
Transmitting file data ................
Committed revision 231154.
also missed files:
Adding modules/j2ee-builder/src/java/org/apache/geronimo/j2ee/deployment/NamingContext.java
Adding modules/j2ee-builder/src/test/org/apache/geronimo/j2ee/deployment/MockNamingContext.java
Transmitting file data ..
Committed revision 231155.
openejb:
Checking in modules/assembly/src/plan/j2ee-deployer-plan.xml;
new revision: 1.48; previous revision: 1.47
Checking in modules/core/src/java/org/openejb/GenericEJBContainer.java;
new revision: 1.52; previous revision: 1.51
Checking in modules/core/src/java/org/openejb/proxy/EJBProxyReference.java;
new revision: 1.2; previous revision: 1.1
Checking in modules/openejb-builder/src/java/org/openejb/deployment/AbstractContainerBuilder.java;
new revision: 1.15; previous revision: 1.14
Checking in modules/openejb-builder/src/java/org/openejb/deployment/EntityBuilder.java;
new revision: 1.20; previous revision: 1.19
Checking in modules/openejb-builder/src/java/org/openejb/deployment/MdbBuilder.java;
new revision: 1.24; previous revision: 1.23
Checking in modules/openejb-builder/src/java/org/openejb/deployment/OpenEJBModuleBuilder.java;
new revision: 1.50; previous revision: 1.49
Checking in modules/openejb-builder/src/java/org/openejb/deployment/OpenEJBReferenceBuilder.java;
initial revision: 1.1
Checking in modules/openejb-builder/src/java/org/openejb/deployment/RemoteEJBReferenceBuilder.java;
new revision: 1.6; previous revision: 1.5
Checking in modules/openejb-builder/src/java/org/openejb/deployment/SessionBuilder.java;
new revision: 1.31; previous revision: 1.30
Checking in modules/openejb-builder/src/test/org/openejb/deployment/AbstractDeploymentTest.java;
new revision: 1.8; previous revision: 1.7
Checking in modules/openejb-builder/src/test/org/openejb/deployment/DeploymentTestContants.java;
new revision: 1.10; previous revision: 1.9
Checking in modules/openejb-builder/src/test/org/openejb/deployment/DeploymentTestSuite.java;
new revision: 1.13; previous revision: 1.12
Checking in modules/openejb-builder/src/test/org/openejb/deployment/slsb/BasicStatelessContainerTest.java;
new revision: 1.9; previous revision: 1.8
> Put the gbeandatas in a deployment context in a queriable container and use queries to resolve links
> ----------------------------------------------------------------------------------------------------
>
> Key: GERONIMO-552
> URL: http://issues.apache.org/jira/browse/GERONIMO-552
> Project: Geronimo
> Type: Improvement
> Components: deployment
> Versions: 1.0-M3
> Reporter: David Jencks
> Assignee: David Jencks
> Fix For: 1.0-M5
>
> GBeans in a DeploymentContext should be kept in a queriable registry like the BasicGBeanRegistry, but for GBeanData rather thand GBeanInstance. ejb-links, resource-links, gbean-links, etc should be resolved by querying this registry rather than more special purpose tracking. This should simplify RefContext considerably. This feature is needed so that if the mail gbean is deployed in a j2ee module (such as an app client) it can be used in that same module.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-552) Put the gbeandatas in a deployment context in a queriable container and use queries to resolve links
Posted by "David Jencks (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-552?page=all ]
David Jencks updated GERONIMO-552:
----------------------------------
Fix Version: 1.0-M5
Environment:
> Put the gbeandatas in a deployment context in a queriable container and use queries to resolve links
> ----------------------------------------------------------------------------------------------------
>
> Key: GERONIMO-552
> URL: http://issues.apache.org/jira/browse/GERONIMO-552
> Project: Geronimo
> Type: Improvement
> Components: deployment
> Versions: 1.0-M3
> Reporter: David Jencks
> Assignee: David Jencks
> Fix For: 1.0-M5
>
> GBeans in a DeploymentContext should be kept in a queriable registry like the BasicGBeanRegistry, but for GBeanData rather thand GBeanInstance. ejb-links, resource-links, gbean-links, etc should be resolved by querying this registry rather than more special purpose tracking. This should simplify RefContext considerably. This feature is needed so that if the mail gbean is deployed in a j2ee module (such as an app client) it can be used in that same module.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-552) Put the gbeandatas in a deployment context in a queriable container and use queries to resolve links
Posted by "David Jencks (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-552?page=comments#action_58077 ]
David Jencks commented on GERONIMO-552:
---------------------------------------
revision 126472 adds the gbeandata registry and queries against it for resource refs and gbean links.
> Put the gbeandatas in a deployment context in a queriable container and use queries to resolve links
> ----------------------------------------------------------------------------------------------------
>
> Key: GERONIMO-552
> URL: http://issues.apache.org/jira/browse/GERONIMO-552
> Project: Apache Geronimo
> Type: Improvement
> Components: deployment
> Versions: 1.0-M3
> Reporter: David Jencks
> Assignee: David Jencks
>
> GBeans in a DeploymentContext should be kept in a queriable registry like the BasicGBeanRegistry, but for GBeanData rather thand GBeanInstance. ejb-links, resource-links, gbean-links, etc should be resolved by querying this registry rather than more special purpose tracking. This should simplify RefContext considerably. This feature is needed so that if the mail gbean is deployed in a j2ee module (such as an app client) it can be used in that same module.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-552) Put the gbeandatas in a deployment context in a queriable container and use queries to resolve links
Posted by "David Jencks (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-552?page=comments#action_12316183 ]
David Jencks commented on GERONIMO-552:
---------------------------------------
the handling of resource gbeans could be improved. With the last patch "dummy" gbeans are put into the deployment context just so their names are known. Later they are replaced by the real gbean datas. We have all the info we need to create the real gbean data when we create the dummies: we can just fill in the attributes later.
> Put the gbeandatas in a deployment context in a queriable container and use queries to resolve links
> ----------------------------------------------------------------------------------------------------
>
> Key: GERONIMO-552
> URL: http://issues.apache.org/jira/browse/GERONIMO-552
> Project: Geronimo
> Type: Improvement
> Components: deployment
> Versions: 1.0-M3
> Reporter: David Jencks
> Assignee: David Jencks
> Fix For: 1.0-M5
>
> GBeans in a DeploymentContext should be kept in a queriable registry like the BasicGBeanRegistry, but for GBeanData rather thand GBeanInstance. ejb-links, resource-links, gbean-links, etc should be resolved by querying this registry rather than more special purpose tracking. This should simplify RefContext considerably. This feature is needed so that if the mail gbean is deployed in a j2ee module (such as an app client) it can be used in that same module.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-552) Put the gbeandatas in a deployment context in a queriable container and use queries to resolve links
Posted by "David Jencks (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-552?page=comments#action_12316181 ]
David Jencks commented on GERONIMO-552:
---------------------------------------
Done for all resource related gbeans:
Sending modules/connector-builder/src/java/org/apache/geronimo/connector/deployment/ConnectorModuleBuilder.java
Sending modules/connector-builder/src/test/org/apache/geronimo/connector/deployment/ConnectorModuleBuilderTest.java
Sending modules/deployment/src/java/org/apache/geronimo/deployment/DeploymentContext.java
Sending modules/j2ee-builder/src/java/org/apache/geronimo/j2ee/deployment/RefContext.java
Sending modules/j2ee-builder/src/java/org/apache/geronimo/j2ee/deployment/ResourceReferenceBuilder.java
Sending modules/j2ee-builder/src/test/org/apache/geronimo/j2ee/deployment/EJBRefContextTest.java
Sending modules/j2ee-builder/src/test/org/apache/geronimo/j2ee/deployment/MockConnectorConfigBuilder.java
Sending modules/jetty-builder/src/test/org/apache/geronimo/jetty/deployment/JettyModuleBuilderTest.java
Sending modules/naming-builder/src/java/org/apache/geronimo/naming/deployment/ENCConfigBuilder.java
Sending modules/tomcat-builder/src/test/org/apache/geronimo/tomcat/deployment/TomcatModuleBuilderTest.java
Transmitting file data ..........
Committed revision 219818.
also openejb:
Checking in modules/openejb-builder/src/java/org/openejb/deployment/MdbBuilder.java;
new revision: 1.21; previous revision: 1.20
Checking in modules/openejb-builder/src/java/org/openejb/deployment/OpenEJBModuleBuilder.java;
new revision: 1.46; previous revision: 1.45
Checking in modules/openejb-builder/src/test/org/openejb/deployment/DeploymentTestContants.java;
new revision: 1.9; previous revision: 1.8
> Put the gbeandatas in a deployment context in a queriable container and use queries to resolve links
> ----------------------------------------------------------------------------------------------------
>
> Key: GERONIMO-552
> URL: http://issues.apache.org/jira/browse/GERONIMO-552
> Project: Geronimo
> Type: Improvement
> Components: deployment
> Versions: 1.0-M3
> Reporter: David Jencks
> Assignee: David Jencks
>
> GBeans in a DeploymentContext should be kept in a queriable registry like the BasicGBeanRegistry, but for GBeanData rather thand GBeanInstance. ejb-links, resource-links, gbean-links, etc should be resolved by querying this registry rather than more special purpose tracking. This should simplify RefContext considerably. This feature is needed so that if the mail gbean is deployed in a j2ee module (such as an app client) it can be used in that same module.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira