[Design of POJO Server] - content of jboss-javaee.jar
by smcgowan＠redhat.com
RE: http://jira.jboss.com/jira/browse/JBAS-4983
jboss-javaee.jar needs to be updated to resolve the inconsistency of classes contained in it for Java Persistence and Java Servlet APIs with those contained in ejb30-persistence.jar and javax.servlet.jar which are also in the server/${config}/lib directories. The jboss-javaee.jar does not currently contain a complete set of EE 5.0 API classes. This exposes a broader question of the intent of the content and the need to eliminate the distribution of duplicate classes in multiple jars. Comments?
Current content includes:
[INFO] JBoss Transaction 1.0.1 API
[INFO] JBoss EJB 3.0 API
[INFO] JBoss Java Servlet 2.5 API
[INFO] JBoss JACC 1.1 API
[INFO] JBoss JavaEE Application Deployment 1.2 API
[INFO] JBoss Java API for XML Registries 1.0
[INFO] JBoss Streaming API for XML 1.0
[INFO] JBoss J2EE Connector Architecture 1.5 API
[INFO] JBoss JMS 1.1 API
[INFO] JBoss Persistence 3.0 API
[INFO] JBoss Java Authentication SPI for Containers 1.0-PR API
The complete API set for JavaEE 5.0 should include:
# EJB 3.0
# Servlet 2.5
# JSP 2.1
# JMS 1.1
# JTA 1.1
# JavaMail 1.4
# JAF 1.1
# Connector 1.5
# Web Services 1.2 (JSR-109)
# JAX RPC 1.1
# JAX WS 2.0 (JSR-224)
# JAXB 2.0 (JSR-222)
# SAAJ 1.3
# JAXR 1.0 (JSR-093)
# JavaEE Mgmt 1.1 (JSR-77)
# JavaEE Deployment 1.2 (JSR-88)
# JACC 1.1 (JSR-115)
# JSTL 1.2 (JSR-52)
# WebSvc Metadata 1.1 (JSR-181)
# JSF 1.2 (JSR-252)
# Common Annotations 1.0 (JSR-250)
# StAX 1.0 (JSR-173)
# Java Persistence 1.0 (JSR-220)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4106849#4106849
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4106849
18 years, 4 months
[Design of JBoss Remoting, Unified Invokers] - One-way messages in Remoting 3
by david.lloyd＠jboss.com
I've been thinking about what Trustin said when we met a number of weeks ago, about one-way messages, delivery guarantee, and how it is implemented.
Trustin's point back then was that a one-way message is actually very similar to a Request. It is simply a Request with no return value, or a return value that is ignored.
Using Requests one can simulate all the desirable delivery guarantee levels. The "fire and forget" model can be done by doing an asynchronous send and just ignoring the returned FutureReply. Delivery guarantee can be done by using a synchronous invocation, and having the remote service just return the reply immediately (before processing the message). And a guaranteed completion can be done just by doing a regular request (but with no reply value).
So I'm thinking that these interfaces should be unified. It will cut down on code and simplify the implementation of services as well.
Thoughts?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4106812#4106812
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4106812
18 years, 4 months
[Design of POJO Server] - Re: Annotation to metadata status
by scott.stark＠jboss.org
I'm seeing this command line compile error that I don't see in eclipse:
| [INFO] ------------------------------------------------------------------------
| [INFO] Compilation failure
|
| /home/svn/JBossHead/projects/metadata/trunk/src/test/java/org/jboss/test/metadata/ejb/JBoss50UnitTestCase.java:[32,26] [deprecation] org.jboss.metadata.ApplicationMetaData in org.jboss.metadata has been deprecated
|
| ...
|
| /home/svn/JBossHead/projects/metadata/trunk/src/test/java/org/jboss/test/metadata/annotation/ejb3/AnnotationEjb3UnitTestCase.java:[533,80] inconvertible types
| found : java.util.Collection<java.lang.Class<?>>
| required: java.util.Collection<java.lang.Class>
|
Eclipse must be less strict in its type cast checking. As a side question, why are there still deprecation warnings on the command line when the AbstractJavaEEEverythingTest has a class level @SuppressWarnings("deprecation")?
| @SuppressWarnings("deprecation")
| public abstract class AbstractEJBEverythingTest extends AbstractJavaEEEverythingTest
| {
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4106811#4106811
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4106811
18 years, 4 months
[Design of POJO Server] - Embbedded - broken - some fixes - still not working
by adrian＠jboss.org
I tried to get the ide test working for embedded inside Eclipse
to understand how Bill's assembly vfs stuff works.
(Aside - the public interface for these classes shouldn't be in org.jboss.vfs.plugins :-)
Problems found so far:
1) Resources from the ejb3 testsuite were leaking into the embeded project.
In particular jndi.properties
2) The ejb3-interceptors-aop.xml is out-of-date
3) The default ejb3 persistence properties was missing
4) jboss-local-jdbc.rar was missing
5) The jca stylesheet was in the wrong place
6) There were many missing jars from the classpath
I've managed to fix all these (at least as they relate to the VFS test in the IDE)
although this shows just how stupid this solution is.
Why do we need to maintain multiple copies of configurations files and implementation
details all over the place. It's an impossible task to keep them in synchronization.
Finally, it's still broken, because Hibernate can't find the entities.
| WARN 21-11 15:44:14,717 (?:?:?) -Unable to find file (ignored): vfs://11956562541581/
| java.lang.RuntimeException: Cannot open stream
| at org.jboss.virtual.plugins.context.vfs.AssembledDirectoryHandler.openStream(AssembledDirectoryHandler.java:117)
| at org.jboss.virtual.VirtualFile.openStream(VirtualFile.java:216)
| at org.jboss.virtual.plugins.vfs.VirtualFileURLConnection.getInputStream(VirtualFileURLConnection.java:117)
| at java.net.URL.openStream(URL.java:1007)
| at org.hibernate.ejb.packaging.InputStreamZippedJarVisitor.doProcessElements(InputStreamZippedJarVisitor.java:33)
| at org.hibernate.ejb.packaging.JarVisitor.getMatchingEntries(JarVisitor.java:240)
| at org.hibernate.ejb.Ejb3Configuration.addScannedEntries(Ejb3Configuration.java:275)
|
It doesn't undertand the virtual file system and assumes its a zipped jar
which it fails to open - obviously.
This behaviour is not pluggable in hibernate. And the choice of how to scan
the jars/filesystem is even in a private method.
A policy decision in a private non-overridable method? :-)
Finally the test itself uses a jboss image in the main src checkout.
Which SVN tells me should be checked in! ;-)
| [ejort@warjort embedded]$ svn status | grep \?
| ? src/main/resources/javase/tmp
| ? src/main/resources/javase/data
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4106793#4106793
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4106793
18 years, 4 months
[Design of JBoss Profiler] - jboss profilers setting LD PATH
by minixman
When i set the LD path on my jboss server i just get an error
[abfo@longmeaelappp2-B:[UAT]bin, 10:05 AM, Wed Nov 21]> ./start-jboss-abfo.sh
jbossInspector
=========================================================================
JBoss Bootstrap Environment
JBOSS_HOME: /apps/abfo//abfo-release/jboss-4.2.1.GA
JAVA: /apps/abfo//jdk1.5.0_10/bin/java
JAVA_OPTS: -Dprogram.name=run.sh -d64 -server -Xmn6g -Xms8g -Xmx8g -XrunjbossInspector:/tmp,include=* -XX:PermSize=256m -XX:MaxPermSize=512m -XX:+UseParallelGC -Xloggc:/tmp/gc.log -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.platform.mbeanserver -Djavax.management.builder.initial=org.jboss.system.server.jmx.MBeanServerBuilderImpl -Dcom.sun.management.jmxremote -Djboss.partition.name=ABFOPartitionUAT -Djboss.hapartition.udpGroup=230.1.2.190 -Djboss.hapartition.mcast_port=45890 -Djboss.webpartition.udpGroup=227.1.2.190 -Djboss.webpartition.mcast_port=45590 -Djboss.ejb3sfsbpartition.udpGroup=228.1.2.190 -Djboss.ejb3sfsbpartition.mcast_port=45690 -Djboss.ejb3entitypartition.udpGroup=229.1.2.190 -Djboss.ejb3entitypartition.mcast_port=45790 -Dtomcat.jvm.route=longmeaelappp2-B -Dabfo.hibernatepartition.name=ABFOHibernateClusterUAT -Dabfo.hibernatepartition.udpGroup=229.1.98.190 -Dabfo.hibernatepartition.udpPort=45990 -Doracle.ds.connection.url=jdbc:oracle:thin:@10.140.50.69:1525:exlink3 -Doracle.ds.username=exlink3 -Doracle.ds.password=exlink3 -Duser.language=en
CLASSPATH: /apps/abfo//abfo-release/jboss-4.2.1.GA/bin/run.jar:/apps/abfo//jdk1.5.0_10/lib/tools.jar
=========================================================================
Error occurred during initialization of VM
Could not find agent library on the library path or in the local directory: jbossInspect
I am using 1.5_10 64BIT
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4106693#4106693
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4106693
18 years, 4 months