JSR181/JSR224 Support

[jcrume]

When does JBoss intend to start work on these two JSR's for J2EE 5? Any information or early peeks would be great!

Thanks!

Jim

[thomas.diesler]

Yes, the JBossWS rewrite is all about that. For status and roadmap, checkout

http://jira.jboss.com/jira/browse/JBWS

[jcrume]

Sweet! Is there anything to download to start trying some of this stuff out?

Thanks!

Jim

[thomas.diesler]

cvs co jboss-head
cd jboss-head
build/build.sh

cd jboss-head/webservice
ant deploy-jbossws
run.sh

cd jboss-head/webservice/test
ant tests

[jcrume]

Is this a build of JBoss 4.0.1, and can I run the EJB 3.0 project modules with it? As you can see, I'm trying to get to an implementation of J2EE 5.

Thanks!

Jim

[jason.greene]

Yes head is JBoss 5, which will be a J2EE 1.5 implementation, so it contains ejb3. This is a development branch, so dont expect stability or completeness.

There is also a preview release of ejb3 you can get from the download page.

Thanks,
-Jason

[jcrume]

Thanks, Jason. I will download it and build it!

I've actually been using the ejb 3.0 previews, and stabilit asn't been bad at all! But I understand the nature of development branches. If I find any problems, I'll just look at the filed bugs first, then file one if it hasn't been yet.

THere is also a JBossWS 2.0 Alpha activity out there that I believe has the J2EE 5 web services standard implemented in it. I'm fairly new to JBoss, and I guess I'm having a little trouble following the roadmap.

Any information is appreciated!

Thanks!

Jim

[thomas.diesler]

I'm having a little trouble following the roadmap.

We all have ;-)

It good to have you look at our new stuff.

[jcrume]

I have downloaded jboss-head using cvs. I am running windows, so I run build\build.bat and nothing sems to happen, or if does, it is REALLY FAST. Any ideas?

[jcrume]

I figured it out. The instructions say to cd to the jboss-head dir, then run build/build.sh. Since this is windows, first of all you run build.bat. Second of all, you have to cd to the build dir for it to work.

Sorry for the false alarm.

Jim

[jcrume]

OK, I've successfully built JBoss 5. When it startes up, it gets a warning, and a stack trace to go along with it. It appears to be an old friend from 4.0.1RC1 where if you didn't remove remoting, you got this. I have looked, and the old remoting-service.xml is not there, so I'm not sure if or how I shold remove remoting. Any ideas? Thanks! Jim

Following is the warning and the first part of the stack trace:
07:49:44,130 WARN [Connector] Error registering invoker org.jboss.remoting.tran
sport.socket.SocketServerInvoker@1be8711 with MBeanServer.
javax.management.InstanceAlreadyExistsException: jboss.remoting:service=invoker,
transport=socket already registered.
at org.jboss.mx.server.registry.BasicMBeanRegistry.add(BasicMBeanRegistr
y.java:755)
at org.jboss.mx.server.registry.BasicMBeanRegistry.registerMBean(BasicMB
eanRegistry.java:211)
at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:144)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractIntercept
or.java:121)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelM
BeanOperationInterceptor.java:131)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:246)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
at org.jboss.mx.server.MBeanServerImpl$3.run(MBeanServerImpl.java:1407)
at java.security.AccessController.doPrivileged(Native Method)
at org.jboss.mx.server.MBeanServerImpl.registerMBean(MBeanServerImpl.jav
a:1402)
at org.jboss.mx.server.MBeanServerImpl.registerMBean(MBeanServerImpl.jav
a:361)
at org.jboss.remoting.transport.Connector.start(Connector.java:246)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:144)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractIntercept
or.java:121)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelM
BeanOperationInterceptor.java:131)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)

[rimmeraj]

This is only a warning. It has been fixed in CVS head branch

[jcrume]

Unless it was fixed today..... My download of the jboss-head is from last evening around 9PM est.... But understood, it is just a warning, and I should be able to work with it.

Jim

[rimmeraj]

Check remoting/src/main/org/jboss/remoting/transport/Connector.java you need version 1.26

[jason.greene]

anonymous cvs lags at least 4 hours behind current head

-Jason