[Design of POJO Server] - Packed vs. unpacked deployments
by alesj
We have different behavior on unknown archives vs. their exploded representation - e.g. the deployers testsuite for Not(Unpacked)ClientDeploymentUnitTestCase.
NotClientDeploymentUnitTestCase (client1-not.ajar) is only recognized by FileStructure, so no further structure details are known.
Where the NotUnpackedClientDeploymentUnitTestCase (dir unpacked-client1-not.ajar) is recognized by JARStructure and as such eventually pushed to Ejb3ClientDeployer. But this deployer requires only .jar names:
| private String getDeploymentJndiName(DeploymentUnit unit)
| {
| String jndiName;
| String shortName = unit.getSimpleName();
| if(shortName.endsWith(".jar/"))
| jndiName = shortName.substring(0, shortName.length() - 5);
| else if(shortName.endsWith(".jar"))
| jndiName = shortName.substring(0, shortName.length() - 4);
| else
| throw new IllegalStateException("Expected either '.jar' or '.jar/' at the end of " + shortName);
|
| return jndiName;
| }
|
So, in the first case we get empty DeploymentUnit - no children, where the second one is treated as client-app, but fails.
This example (excluding the failure) is a general behavior, and I don't think the user expects its deployments to behave differently, whether they are packed or unpacked.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4110555#4110555
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4110555
18 years, 1 month
[Design of Messaging on JBoss (Messaging/JBoss)] - Re: New to JBOSS / JMS integration
by Maulik.Kayastha
Hi
I would also like to add,
- I aware that all the configuration files are available under deploy/jms folder.
- jbossMQ-service.xml and uil2-service.xml files have great role to do while creating queues and creating ConnectionFactory, respectively.
But I am not able to relate all the things and not able to start with a small example, even I am not able to define QueueConnectionFactory.
I am getting error like,
Exception in thread "main" javax.naming.CommunicationException [Root exception is java.lang.ClassNotFoundException: org.jboss.jms.client.JBossConnectionFactory (no security manager: RMI class loader disabled)]
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:728)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:587)
at javax.naming.InitialContext.lookup(Unknown Source)
at SendRecvClient.setupPTP(SendRecvClient.java:61)
at SendRecvClient.sendRecvAsync(SendRecvClient.java:76)
at SendRecvClient.main(SendRecvClient.java:107)
Caused by: java.lang.ClassNotFoundException: org.jboss.jms.client.JBossConnectionFactory (no security manager: RMI class loader disabled)
at sun.rmi.server.LoaderHandler.loadClass(Unknown Source)
at sun.rmi.server.LoaderHandler.loadClass(Unknown Source)
at java.rmi.server.RMIClassLoader$2.loadClass(Unknown Source)
at java.rmi.server.RMIClassLoader.loadClass(Unknown Source)
at sun.rmi.server.MarshalInputStream.resolveClass(Unknown Source)
at java.io.ObjectInputStream.readNonProxyDesc(Unknown Source)
at java.io.ObjectInputStream.readClassDesc(Unknown Source)
at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
at java.io.ObjectInputStream.readObject0(Unknown Source)
at java.io.ObjectInputStream.readObject(Unknown Source)
at java.rmi.MarshalledObject.get(Unknown Source)
at org.jnp.interfaces.MarshalledValuePair.get(MarshalledValuePair.java:72)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:652)
... 5 more
So Any startup small application along with configuration details is highly appriciated.
Regards,
Maulik
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4110542#4110542
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4110542
18 years, 1 month
[Design of JCA on JBoss] - Re: DeploymentInfo/Template MCF
by vickyk
Yes I figured out this and I added javax.xml.bind.annotation.XmlRootElement annotations in ManagedConnectionFactoryDeploymentGroup as
*/
| @XmlAccessorType(XmlAccessType.NONE)
| @ManagementObject
| @XmlRootElement
| public class ManagedConnectionFactoryDeploymentGroup implements Serializable
After making the changes I am getting some different error
Testcase: testAddDataSource took 3.002 sec
| Caused an ERROR
| Failed to map property: password to managed properties for deployment
| java.lang.IllegalArgumentException: Failed to map property: password to managed properties for deployment
| at org.jboss.profileservice.management.ManagementViewImpl.applyTemplate(ManagementViewImpl.java:588)
| at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:121)
| at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82)
| at org.jboss.profileservice.remoting.ProfileServiceInvocationHandler.invoke(ProfileServiceInvocationHandler.java:56)
| at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:771)
| at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:573)
| at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:373)
| at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:166)
| at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:163)
| at org.jboss.remoting.Client.invoke(Client.java:1634)
| at org.jboss.remoting.Client.invoke(Client.java:548)
| at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:62)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
| at org.jboss.aspects.remoting.MergeMetaDataInterceptor.invoke(MergeMetaDataInterceptor.java:74)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
| at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:65)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
| at AOPProxy$1.applyTemplate(AOPProxy$1.java)
| at org.jboss.test.profileservice.test.ProfileServiceUnitTestCase.testAddDataSource(ProfileServiceUnitTestCase.java:406)
| at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:74)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
| at org.jboss.aspects.remoting.MergeMetaDataInterceptor.invoke(MergeMetaDataInterceptor.java:74)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
| at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:65)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
| at AOPProxy$1.applyTemplate(AOPProxy$1.java)
| at org.jboss.test.profileservice.test.ProfileServiceUnitTestCase.testAddDataSource(ProfileServiceUnitTestCase.java:406)
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4110514#4110514
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4110514
18 years, 1 month