Netty 3.1.0.GA released
by Trustin Lee
Hi folks,
Netty 3.1.0.GA, the first major stable release of 3.1 branch, has been
released. A lot of effort has been put into this release for more than
a half year since the previous GA version was released.
The Netty project is an effort to provide an asynchronous, event-driven
network application framework and tools for rapid development of
maintainable, high-performance, high-scalability protocol servers and
clients.
In other words, Netty is a NIO client server framework that enables
quick and easy development of network applications such as protocol
servers and clients. It simplifies and streamlines network programming
such as TCP and UDP socket servers.
Please visit our web site to download it:
* http://www.jboss.org/netty/
As always, your feed back is more than appreciated. Please visit the
discussion forum and leave some comments and questions:
* http://www.jboss.org/netty/community.html
Alternatively, please follow us at Twitter and send a message:
* http://twitter.com/netty_project
Success Stories
===============
Several community members shared his and her success stories with Netty
since its beginning, and their stories were published to the official
web site today.
* Testimonials - http://www.jboss.org/netty/testimonials.html
* Performance Stories - http://www.jboss.org/netty/performance.html
Changes Since 3.0
=================
There were numberless improvements in features, performance, and API
usability. The following is the list of the most noteworthy features:
* Easier large data streaming
* Easier protocol codec unit-testing
* I/O timeout and idle state detection
* Easier and safer application shutdown
* More reliable OutOfMemoryError prevention
* New transports:
* OIO and NIO based UDP transport
* Local transport (a.k.a. in-VM transport)
* HTTP tunneling transport that bypasses a firewall
* New out-of-the-box codecs:
* HTTP client and server
* Various utilities for proprietary protocol implementations
* Integration with various technologies:
* Google Protocol Buffers
* JBoss Microcontainer, OSGi, Guice, and Spring
For the detailed information on each change, please refer to the
previous release announcements: http://tinyurl.com/lfqdrv
Changes Since 3.1.0.CR1
=======================
Comparing to the previous unstable release, 3.1.0.GA is rather a minor
bug fix release overally. Please refer to the full changelog for the
detailed list of fixes and changes: http://tinyurl.com/mxt6ok
Cheers,
Trustin Lee, http://gleamynode.net/
14 years, 9 months
Help: DLQ Message Redirection Problem
by Sheeraz Junejo
Hi,
I am hoping to get some answer from this list(finger crossed). My question is; How to redirect message to default DLQ?.
DLQ here is the one which is created by jBoss when we start it as 'run.bat -b 0.0.0.0 -c all' [Note: I want it to use cluster setup] along with some other queues called A,B,C,D... with two of my queues like RequestQueue and ResponseQueue. When My MDB fail to post message to server it gives an exception where I think by default the message resides in RequestQueue should get redirected to DLQ [jndi: queue/DLQ] where one other MDB is waiting and post message to some other instance of my server.
I have deployed following in my '<Jboss_Home>/server/all/deploy' directory;
1) BrowserWeb.war à Successfully deployed web application which is putting message on queue and fetching messages back from reply queue.
2) Jremote-ra.rar à Successfully deployed resource adapter which provides connectivity to the database server on port '20005' using first connection factory in 'server-ds.xml'. If database server service goes down on port 20005 my primary MDB will give an exception here message should get redirected to jBoss default DLQ and my backup MDB_DLQ should read message from DLQ and will try to use second connection factory which will try to connect on port '20003' where my database server is alive.
Server-ds.xml (Deployment Descriptor uses above resource adaptor)
<?xml version="1.0" encoding="utf-8"?>
<!-- ================================================================================ -->
<!-- -->
<!-- JBoss Server Configuration -->
<!-- -->
<!-- jRemote resource adapter deployment for JBoss, configured for local connection -->
<!-- -->
<!-- ================================================================================ -->
<connection-factories>
<tx-connection-factory>
<jndi-name>jca/t24ConnectionFactory</jndi-name>
<rar-name>jremote-ra.rar</rar-name>
<connection-definition>com.jbase.jremote.JConnectionFactory</connection-definition>
<config-property name="host" type="java.lang.String">10.44.5.138</config-property> -->
<config-property name="port" type="java.lang.Integer">20005</config-property>
<config-property name="allowInput" type="java.lang.Boolean">true</config-property>
<config-property name="compression" type="java.lang.Boolean">true</config-property>
<config-property name="compressionThreshold" type="java.lang.Integer">2048</config-property>
<!--pooling parameters-->
<min-pool-size>1</min-pool-size>
<max-pool-size>10</max-pool-size>
<prefill>true</prefill>
</tx-connection-factory>
<tx-connection-factory>
<jndi-name>jca/t24ConnectionFactory_DLQ</jndi-name>
<rar-name>jremote-ra.rar</rar-name>
<connection-definition>com.jbase.jremote.JConnectionFactory</connection-definition>
<config-property name="host" type="java.lang.String">10.44.5.138</config-property> -->
<config-property name="port" type="java.lang.Integer">20003</config-property>
<config-property name="allowInput" type="java.lang.Boolean">true</config-property>
<config-property name="compression" type="java.lang.Boolean">true</config-property>
<config-property name="compressionThreshold" type="java.lang.Integer">2048</config-property>
<!--pooling parameters
<min-pool-size>1</min-pool-size>-->
<max-pool-size>10</max-pool-size>
<!--<prefill>true</prefill>-->
</tx-connection-factory>
</connection-factories>
Destination-service.xml (For JMS)
<?xml version="1.0" encoding="UTF-8"?>
<!-- $Id: jbossmq-destinations-service.xml 25907 2004-11-16 04:32:39Z ejort $ -->
<!--
| This file defines the default Queues and Topics that JBossMQ
| ships with. The default Queues and Topics are used by the
| JBoss test suite and by the sample jms programs.
|
| You can add other destinations to this file, or you can create other
| *-service.xml files to contain your application's destinations.
-->
<server>
<!-- Destination without a configured SecurityManager or without a
a SecurityConf will default to role guest with read=true, write=true,
create=false.
-->
<mbean code="org.jboss.mq.server.jmx.Queue"
name="jboss.mq.destination:service=Queue,name=t24OFSQueue">
<depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager</depends>
</mbean>
<mbean code="org.jboss.mq.server.jmx.Queue"
name="jboss.mq.destination:service=Queue,name=t24OFSReplyQueue">
<depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager</depends>
</mbean>
</server>
MDB is a jar file contains following xml in META-INF
Ejb-jar.xml
<?xml version="1.0" encoding="UTF-8"?>
<ejb-jar id="EJBJar_OfsMessageMDB" version="2.1" xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/ejb-jar_2_1.xsd">
<display-name>OFSMessage</display-name>
<enterprise-beans>
<message-driven id="MessageDriven_OfsMessageMDB"> <!-- Simple message driven bean-->
<display-name>OFSMessage Bean</display-name>
<ejb-name>OFSMessageMDB</ejb-name>
<ejb-class>com.temenos.ofsmessage.mdb.OFSMessageMDB</ejb-class>
<messaging-type>javax.jms.MessageListener</messaging-type>
<transaction-type>Bean</transaction-type>
<message-destination-type>javax.jms.Queue</message-destination-type>
<activation-config>
<activation-config-property>
<activation-config-property-name>acknowledgeMode</activation-config-property-name>
<activation-config-property-value>Auto-acknowledge</activation-config-property-value>
</activation-config-property>
</activation-config>
<resource-ref id="ResourceRef_jmsQueueConnectionFactory">
<description>T24 Queue Connection Factory</description>
<res-ref-name>jms/jmsConnectionFactory</res-ref-name>
<res-type>javax.jms.QueueConnectionFactory</res-type>
<res-auth>Container</res-auth>
</resource-ref>
<resource-ref id="ResourceRef_t24ConnectionFactory">
<description>T24 JCA Connection Factory</description>
<res-ref-name>jca/t24ConnectionFactory</res-ref-name>
<res-type>com.jbase.jremote.JConnectionFactory</res-type>
<res-auth>Container</res-auth>
</resource-ref>
<resource-ref id="ResourceRef_t24OFSReplyQueue">
<description>OFS reply queue</description>
<res-ref-name>queue/t24OFSReplyQueue</res-ref-name>
<res-type>javax.jms.Queue</res-type>
<res-auth>Container</res-auth>
</resource-ref>
</message-driven>
<message-driven id="MessageDriven_OfsMessageMDB_DLQ">
<display-name>OFSMessage Bean DLQ</display-name> <!--DLQ message driven bean-->
<ejb-name>OFSMessageMDB_DLQ</ejb-name>
<ejb-class>com.temenos.ofsmessage.mdb.OFSMessageMDB</ejb-class>
<messaging-type>javax.jms.MessageListener</messaging-type>
<transaction-type>Bean</transaction-type>
<message-destination-type>javax.jms.Queue</message-destination-type>
<activation-config>
<activation-config-property>
<activation-config-property-name>acknowledgeMode</activation-config-property-name>
<activation-config-property-value>Auto-acknowledge</activation-config-property-value>
</activation-config-property>
</activation-config>
<resource-ref id="ResourceRef_jmsQueueConnectionFactory_DLQ">
<description>T24 Queue Connection Factory</description>
<res-ref-name>jms/jmsConnectionFactory</res-ref-name>
<res-type>javax.jms.QueueConnectionFactory</res-type>
<res-auth>Container</res-auth>
</resource-ref>
<resource-ref id="ResourceRef_t24ConnectionFactory_DLQ">
<description>T24 JCA Connection Factory</description>
<res-ref-name>jca/t24ConnectionFactory</res-ref-name>
<res-type>com.jbase.jremote.JConnectionFactory</res-type>
<res-auth>Container</res-auth>
</resource-ref>
<resource-ref id="ResourceRef_t24OFSReplyQueue_DLQ">
<description>OFS reply queue</description>
<res-ref-name>queue/t24OFSReplyQueue</res-ref-name>
<res-type>javax.jms.Queue</res-type>
<res-auth>Container</res-auth>
</resource-ref>
</message-driven>
</enterprise-beans>
</ejb-jar>
Jboss.xml
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE jboss PUBLIC "-//JBoss//DTD JBOSS 4.0//EN"
"http://www.jboss.org/j2ee/dtd/jboss_4_0.dtd">
<jboss>
<enterprise-beans>
<message-driven>
<ejb-name>OFSMessageMDB</ejb-name>
<destination-jndi-name>queue/t24OFSQueue</destination-jndi-name>
<resource-ref>
<res-ref-name>jms/jmsConnectionFactory</res-ref-name>
<jndi-name>java:/ConnectionFactory</jndi-name>
</resource-ref>
<resource-ref>
<res-ref-name>queue/t24OFSReplyQueue</res-ref-name>
<!-- <res-type>javax.jms.Queue</res-type>
-->
<jndi-name>queue/t24OFSReplyQueue</jndi-name>
</resource-ref>
<resource-ref>
<res-ref-name>jca/t24ConnectionFactory</res-ref-name>
<jndi-name>java:jca/t24ConnectionFactory</jndi-name>
<!-- <res-type>com.jbase.jremote.JConnectionFactory</res-type>
-->
</resource-ref>
</message-driven>
<message-driven>
<ejb-name>OFSMessageMDB_DLQ</ejb-name>
<destination-jndi-name>queue/DLQ</destination-jndi-name> <!-Default DL Queue Refrenece -->
<resource-ref>
<res-ref-name>jms/jmsConnectionFactory</res-ref-name>
<jndi-name>java:/ConnectionFactory</jndi-name>
</resource-ref>
<resource-ref>
<res-ref-name>queue/t24OFSReplyQueue</res-ref-name>
<!--<res-type>javax.jms.Queue</res-type>-->
<jndi-name>queue/t24OFSReplyQueue</jndi-name>
</resource-ref>
<resource-ref>
<res-ref-name>jca/t24ConnectionFactory</res-ref-name>
<jndi-name>java:jca/t24ConnectionFactory_DLQ</jndi-name>
<!--<res-type>com.jbase.jremote.JConnectionFactory</res-type>-->
</resource-ref>
</message-driven>
</enterprise-beans>
</jboss>
Is Something missing in here because I can not see any message redirection to DLQ. If you require any other information about my setup please let me know. Your response and help will be appreciated.
Regards,
--
Sheeraz Junejo
Disclaimer:
If you have received this e-mail in error please notify the sender.
Please note that any views or opinions presented in this e-mail are solely
those of the author and do not necessarily represent those of TEMENOS.
We recommend that you check this e-mail and any attachments against viruses.
TEMENOS accepts no liability for any damage caused by any malicious code
or virus transmitted by this e-mail.
14 years, 9 months
Logging & bootstrap integration branch merged
by David M. Lloyd
I've merged the branch in which I and ALR updated the logging service and
bootstrap, respectively. Here's the gist of the logging changes:
- The log4j-boot.jar hack is gone
- The default log implementation is now jboss-logmanager
- Log4jService is gone
- The boot-time log config is slightly different (see
"system/src/resources/logging.properties")
- Run-time log config now uses SchemaResolverDeployer to deploy
jboss-logging.xml (located in deploy/, not conf/, due to the way the new MC
deployer system works; look in deployers/ for more information about how
the POJO log service works)
- All log messages produced by slf4j, jboss-logging, commons-logging,
log4j, and JDK logging are all properly routed through the log system
As things stand, server startup should be slightly faster than it was
before, though jbossxb parsing of jboss-logging.xml actually slows things
down rather more than I expected, and I haven't checked to see if this
offsets the performance gain. Run-time performance of logging should be
much faster than it was under log4j.
Let the pain & mayhem begin.
- DML
14 years, 9 months
Re: [jboss-dev] [infinispan-dev] Infinispan configuration - all in one solution
by Manik Surtani
Everyone star this! :-)
From what I gather from the comments on the link below, the
blacklisting can be worked around to some degree. Has anyone tried an
alternate JAXB implementation like JBossXB, perhaps using the impl
classes directly rather than the javax interfaces?
On 17 Jul 2009, at 20:03, Adrian Cole wrote:
> By design as far as I can tell: The important jaxb classes are
> restricted.
>
> http://code.google.com/p/googleappengine/issues/detail?id=1267
>
> -A
>
> On Fri, Jul 17, 2009 at 8:56 PM, Emmanuel Bernard <emmanuel(a)hibernate.org
> > wrote:
> You mean JAXB by design or the JAXB implementation you have tried?
>
> On Jul 17, 2009, at 14:47, Adrian Cole wrote:
>
>> The only problem with using jaxb is that it doesn't work in google
>> app engine. Switching to jaxb implies adding another roadblock on
>> the way to gae/j support. This is the only reason I'm not using
>> jaxb for jclouds, even though it would make things simpler.
>>
>> -Adrian
>>
>> On Fri, Jul 17, 2009 at 5:38 PM, Vladimir Blagojevic <vblagoje(a)redhat.com
>> > wrote:
>> On 7/17/09 5:16 PM, Bill Burke wrote:
>> > Wouldn't it be better to write a javadoc-like generator that
>> > introspected for JAXB and Inifispan annotations instead of
>> writing your
>> > own XML parser and schema generator? Or maybe I'm
>> misunderstanding your
>> > post.
>> >
>> > In other words, use JAXB for marshalling/unmarshalling/schema
>> > generation. Use inifinispan javadoc generator for documentation.
>> >
>> I looked around a bit more to see that now in JAXB 2.x we have
>> annotations as well :) If we annotate our configuration beans with
>> JAXB
>> annotations I suppose we can do exactly what you suggest - use JAXB
>> for
>> marshalling/unmarshalling/schema generation and at the same time use
>> those annotation in a custom tool that creates reference
>> documentation.
>> > By creating your own XML parsing you've just complicated the
>> maintenance
>> > problems for future maintainers of infinispan.
>> >
>> I agree.
>>
>> Cheers,
>> Vladimir
>> _______________________________________________
>> infinispan-dev mailing list
>> infinispan-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/infinispan-dev
>>
>> _______________________________________________
>> infinispan-dev mailing list
>> infinispan-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/infinispan-dev
>
>
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/infinispan-dev
--
Manik Surtani
manik(a)jboss.org
Lead, Infinispan
Lead, JBoss Cache
http://www.infinispan.org
http://www.jbosscache.org
14 years, 9 months
Seeking JAXB expert
by Vladimir Blagojevic
Hi,
Does JAXB have a directive that allows mapping of multiple xml elements
from schema to one class C where each attribute from all those xml
elements corresponds to a certain attribute of class C?
Regards,
Vladimir
14 years, 9 months
Broken build Branch_5_x
by Thomas Diesler
[java] Missing:
[java] ----------
[java] 1)
org.jboss.bootstrap:jboss-bootstrap-impl-as:jar:2.0.0-alpha-3
[java]
[java] Try downloading the file manually from the project website.
[java]
[java] Then, install it using the command:
[java] mvn install:install-file
-DgroupId=org.jboss.bootstrap -DartifactId=jboss-bootstrap-impl-as
-Dversion=2.0.0-alpha-3 -Dpackaging=jar -Dfile=/path/to/file
[java]
[java] Alternatively, if you host your own repository you can
deploy the file there:
[java] mvn deploy:deploy-file -DgroupId=org.jboss.bootstrap
-DartifactId=jboss-bootstrap-impl-as -Dversion=2.0.0-alpha-3
-Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
[java]
[java] Path to dependency:
[java] 1) org.jboss.jbossas:jboss-as-thirdparty:pom:5.2.0-SNAPSHOT
[java] 2)
org.jboss.bootstrap:jboss-bootstrap-impl-as:jar:2.0.0-alpha-3
[java]
[java] 2)
org.jboss.bootstrap:jboss-bootstrap-impl-base:jar:2.0.0-alpha-3
[java]
[java] Try downloading the file manually from the project website.
[java]
[java] Then, install it using the command:
[java] mvn install:install-file
-DgroupId=org.jboss.bootstrap -DartifactId=jboss-bootstrap-impl-base
-Dversion=2.0.0-alpha-3 -Dpackaging=jar -Dfile=/path/to/file
[java]
[java] Alternatively, if you host your own repository you can
deploy the file there:
[java] mvn deploy:deploy-file -DgroupId=org.jboss.bootstrap
-DartifactId=jboss-bootstrap-impl-base -Dversion=2.0.0-alpha-3
-Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
[java]
[java] Path to dependency:
[java] 1) org.jboss.jbossas:jboss-as-thirdparty:pom:5.2.0-SNAPSHOT
[java] 2)
org.jboss.bootstrap:jboss-bootstrap-impl-base:jar:2.0.0-alpha-3
[java]
[java] 3)
org.jboss.bootstrap:jboss-bootstrap-impl-mc:jar:2.0.0-alpha-2
[java]
[java] Try downloading the file manually from the project website.
[java]
[java] Then, install it using the command:
[java] mvn install:install-file
-DgroupId=org.jboss.bootstrap -DartifactId=jboss-bootstrap-impl-mc
-Dversion=2.0.0-alpha-2 -Dpackaging=jar -Dfile=/path/to/file
[java]
[java] Alternatively, if you host your own repository you can
deploy the file there:
[java] mvn deploy:deploy-file -DgroupId=org.jboss.bootstrap
-DartifactId=jboss-bootstrap-impl-mc -Dversion=2.0.0-alpha-2
-Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
[java]
[java] Path to dependency:
[java] 1) org.jboss.jbossas:jboss-as-thirdparty:pom:5.2.0-SNAPSHOT
[java] 2)
org.jboss.bootstrap:jboss-bootstrap-impl-mc:jar:2.0.0-alpha-2
[java]
[java] 4) org.jboss.bootstrap:jboss-bootstrap-spi-as:jar:2.0.0-alpha-3
[java]
[java] Try downloading the file manually from the project website.
[java]
[java] Then, install it using the command:
[java] mvn install:install-file
-DgroupId=org.jboss.bootstrap -DartifactId=jboss-bootstrap-spi-as
-Dversion=2.0.0-alpha-3 -Dpackaging=jar -Dfile=/path/to/file
[java]
[java] Alternatively, if you host your own repository you can
deploy the file there:
[java] mvn deploy:deploy-file -DgroupId=org.jboss.bootstrap
-DartifactId=jboss-bootstrap-spi-as -Dversion=2.0.0-alpha-3
-Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
[java]
[java] Path to dependency:
[java] 1) org.jboss.jbossas:jboss-as-thirdparty:pom:5.2.0-SNAPSHOT
[java] 2)
org.jboss.bootstrap:jboss-bootstrap-spi-as:jar:2.0.0-alpha-3
[java]
[java] ----------
[java] 4 required artifacts are missing.
[java]
[java] for artifact:
[java] org.jboss.jbossas:jboss-as-thirdparty:pom:5.2.0-SNAPSHOT
[java]
[java] from the specified remote repositories:
[java] snapshots.jboss.org (http://snapshots.jboss.org/maven2),
[java] central (http://repo1.maven.org/maven2),
[java] repository.jboss.org (http://repository.jboss.org/maven2)
14 years, 9 months
Maven repo aggregation
by Thomas Diesler
Hi Paul,
the issue of maven repo aggregation has poped up again during our MC
conf-calls. There is now a JIRA issue that folks can monitor on the
progress of this.
https://jira.jboss.org/jira/browse/JBBUILD-534
Generally, I'd like to mention again that 'deploy-file' is not good
solution because of
* with the generated POM you loose all info about transitive
dependencies, etc.
* when you preserve/deploy the original POM you also deploy the
dependencies on other repos
* the transitive enclosure of information for
(groupId+artifactId+version+classifier) should be equal independent of
the repo where you get the artifact from
cheers
-thomas
14 years, 9 months
Is it possible to create multiplatform installer for java projects
by mr.vikash
Hi,
I am trying to create multiplatform installer for java projects. Main
motive to create this installer are as follows
1. Install the jboss on system.
2. update the configuration information(eg. database information) submitted
by the user on installer dialoug during installation
process.
3. Read or execute the java class file before installation complete.
4. Start the Jboss services before installation complete
Is any one have any idea, how to create such type of installer.........
Thx in advance.
Vikash Srivastava
--
View this message in context: http://www.nabble.com/Is-it-possible-to-create-multiplatform-installer-fo...
Sent from the JBoss - Dev mailing list archive at Nabble.com.
14 years, 9 months
java.lang.ClassNotFoundException: No ClassLoaders found for: com.iplanet.services.comm.client.AlreadyRegisteredException
by jamerich
Hi,
I am working with JBOSS 4.2.3.GA. I have deployed OpenSSO and Policy agent
in different server instances. They deployed successfully. When i am trying
to access my sample application,
I am getting the below exception.
java.lang.ClassNotFoundException: No ClassLoaders found for:
com.iplanet.services.comm.client.AlreadyRegisteredException
org.jboss.mx.loading.LoadMgr3.beginLoadTask(LoadMgr3.java:212)
org.jboss.mx.loading.RepositoryClassLoader.loadClassImpl(RepositoryClassLoader.java:521)
org.jboss.mx.loading.RepositoryClassLoader.loadClass(RepositoryClassLoader.java:415)
java.lang.ClassLoader.loadClass(ClassLoader.java:252)
java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
com.sun.identity.agents.arch.Manager.<clinit>(Manager.java:643)
com.sun.identity.agents.filter.AmAgentBaseFilter.initializeFilter(AmAgentBaseFilter.java:267)
com.sun.identity.agents.filter.AmAgentBaseFilter.getAmFilterInstance(AmAgentBaseFilter.java:357)
com.sun.identity.agents.filter.AmAgentBaseFilter.doFilter(AmAgentBaseFilter.java:69)
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
Please help me to fix the issue.
Thanks,
Jame
--
View this message in context: http://www.nabble.com/java.lang.ClassNotFoundException%3A-No-ClassLoaders...
Sent from the JBoss - Dev mailing list archive at Nabble.com.
14 years, 9 months
