[EJB 3.0] - Re: Simplest possible stateless bean
by wolfc
"Renen" wrote : anonymous wrote : Misunderstanding. I was talking about how would you like to code your client, what API did you have in mind?
|
| Now I'm puzzled: could you explain what API choices I have.
|
| If I should RTFM, don't hesitate to say so! But, I think even terse answers will steer my reading.
|
| Thanks for the guidance.
Hehe, currently there is no choice. You have to create an interface to go with your bean and use that interface in your client.
As I gather from your post you expected something different. So I am curious to what you did expect of the EJB 3 implementation? Maybe I misread your post and the 'Refactor'->'Extract Interface...' menu in Eclipse could cut the cake. Or maybe there is an alternative which has been overlooked.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4087123#4087123
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4087123
18 years, 9 months
[Remoting] - Exception with CompressingMarshaller
by rukru
To Use the CompressingMarshaller in the JBoss AS I replaced in ejb3.deployer/WEB-INF/jboss-service.xml the line
<attribute name="InvokerLocator">socket://${jboss.bind.address}:3873</attribute>
|
with
<attribute name="InvokerLocator">socket://${jboss.bind.address}:3873/?marshaller=org.jboss.remoting.marshal.compress.CompressingMarshaller&unmarshaller=org.jboss.remoting.marshal.compress.CompressingUnMarshaller</attribute>
|
But with this setting the following exception occurs with different version numbers that can not read:
10:43:46,934 ERROR [socket.ServerThread] failed
| java.io.IOException: Can not read data for version 72. Supported versions: 1,2,22
| at org.jboss.remoting.transport.socket.ServerThread.versionedRead(ServerThread.java:660)
| at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:530)
| at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:383)
| at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:165)
|
The Exception appears in jboss-4.2.0.GA and in jboss-4.2.1.GA, too. The Server is used by a Application Client with contains the following JBoss Jars:
jbosssx-client.jar
jbossall-client.jar
jboss-ejb3.jar
jboss-ejb3x.jar
jboss-aspect-library-jdk50.jar
jboss-aop-jdk50.jar
Are there any other configuration settings needed, possibly on client side?
Thanks for your help!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4087122#4087122
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4087122
18 years, 9 months
[Microcontainer] - Injecting beans into Unit Tests under 1.02
by jonesn
Hi All.
I'm looking to introduce some injection into my current works Test Suite. They run their apps under JBoss so I thought Microcontainer would be the best fit for them.
I was having a look at MicrocontainerTest and MicrocontainerTestDelegate but I'm not too sure what their envisaged usage is.
What I'm looking to do is inject beans into integration tests, things like Datasources etc. I'm from a Spring background and in the past I would have extended AbstractDependencyInjectionSpringContextTests which would inject beans from the supplied contexts into the tests.
Does Microcontainer offer something similar? If not could someone point me in the direction of an example or the like to show me how Injection into Tests is achieved with Microcontainer?
Thanks for your help.
Nick.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4087121#4087121
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4087121
18 years, 9 months