[JBoss Web Services] - JavaEE 5 annotated Webservice-EJB fails in JBoss AS 6
by Rainer Flicker
Rainer Flicker [http://community.jboss.org/people/rflicker] created the discussion
"JavaEE 5 annotated Webservice-EJB fails in JBoss AS 6"
To view the discussion, visit: http://community.jboss.org/message/604383#604383
--------------------------------------------------------------
Hi,
i have a JavaEE 5 annotated Webservice-EJB (works with JBoss AS 5.1, Glassfish 2.1 and Websphere 7),
which fails in JBoss AS 6 with:
Caused by: java.lang.LinkageError: loader constraint violation in interface itable initialization: when resolving method "$Proxy248.setElementType(Ljavax/xml/namespace/QName;)V" the class loader (instance of org/jboss/classloader/spi/base/BaseClassLoader) of the current class, $Proxy248, and the class loader (instance of org/jboss/classloader/spi/base/BaseClassLoader) for interface javax/wsdl/extensions/ExtensibilityElement have different Class objects for the type javax/xml/namespace/QName used in the signature
at java.lang.Class.getDeclaredConstructors0(Native Method) [:1.6.0_25]
at java.lang.Class.privateGetDeclaredConstructors(Class.java:2389) [:1.6.0_25]
at java.lang.Class.getConstructor0(Class.java:2699) [:1.6.0_25]
at java.lang.Class.getConstructor(Class.java:1657) [:1.6.0_25]
at java.lang.reflect.Proxy.newProxyInstance(Proxy.java:587) [:1.6.0_25]
at org.apache.cxf.tools.util.SOAPBindingUtil.getProxy(SOAPBindingUtil.java:87) [:2.3.1]
at org.apache.cxf.tools.util.SOAPBindingUtil.getSoapBinding(SOAPBindingUtil.java:274) [:2.3.1]
at org.apache.cxf.tools.util.SOAPBindingUtil.createSoapBinding(SOAPBindingUtil.java:426) [:2.3.1]
at org.apache.cxf.binding.soap.SoapBindingFactory.createSoapBinding(SoapBindingFactory.java:213) [:2.3.1]
at org.apache.cxf.binding.soap.SoapBindingFactory.createBindingInfo(SoapBindingFactory.java:198) [:2.3.1]
at org.apache.cxf.binding.AbstractBindingFactory.createBindingInfo(AbstractBindingFactory.java:97) [:2.3.1]
at org.apache.cxf.frontend.AbstractWSDLBasedEndpointFactory.createBindingInfo(AbstractWSDLBasedEndpointFactory.java:339) [:2.3.1]
at org.apache.cxf.jaxws.JaxWsServerFactoryBean.createBindingInfo(JaxWsServerFactoryBean.java:166) [:2.3.1]
at org.apache.cxf.frontend.AbstractWSDLBasedEndpointFactory.createEndpointInfo(AbstractWSDLBasedEndpointFactory.java:251) [:2.3.1]
at org.apache.cxf.frontend.AbstractWSDLBasedEndpointFactory.createEndpoint(AbstractWSDLBasedEndpointFactory.java:147) [:2.3.1]
at org.apache.cxf.frontend.ServerFactoryBean.create(ServerFactoryBean.java:148) [:2.3.1]
at org.apache.cxf.jaxws.JaxWsServerFactoryBean.create(JaxWsServerFactoryBean.java:183) [:2.3.1]
at org.apache.cxf.jaxws.EndpointImpl.getServer(EndpointImpl.java:407) [:2.3.1]
at org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:314) [:2.3.1]
at org.jboss.wsf.stack.cxf.deployment.EndpointImpl.doPublish(EndpointImpl.java:62) [:3.4.1.GA]
at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:238) [:2.3.1]
at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:481) [:2.3.1]
at org.jboss.wsf.stack.cxf.configuration.NonSpringBusHolder.configure(NonSpringBusHolder.java:112) [:3.4.1.GA]
at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.start(BusDeploymentAspect.java:110) [:3.4.1.GA]
at org.jboss.webservices.integration.deployers.WSDeploymentAspectDeployer.internalDeploy(WSDeploymentAspectDeployer.java:123) [:6.0.0.Final]
at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:55) [:2.2.0.GA]
at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:179) [:2.2.0.GA]
... 44 more
Webservice-EJB:
@Stateless
@WebService(name = "TestReportService",
serviceName = "AsmsWebservice",
targetNamespace= " http://webservice.asms.airsight.de http://webservice.asms.airsight.de")
@SOAPBinding(style = SOAPBinding.Style.DOCUMENT,
use = SOAPBinding.Use.LITERAL,
parameterStyle = SOAPBinding.ParameterStyle.WRAPPED)
public class TestReportService implements TestReportServiceRemote, Serializable {
@PersistenceContext
private EntityManager em;
@WebMethod(action = "createFullTestReport")
@WebResult(name="successful")
public boolean createFullTestReport(
@WebParam(name="name") String name,
@WebParam(name="id") Long id,
@WebParam(name="feedback") Boolean feedback,
@WebParam(name="altitude") Double altitude) { return true; }
}
@Remote
public interface TestReportServiceRemote { public boolean createFullTestReport(String name, Long id, Boolean feedback, Double altitude);}
standard-jaxws-endpoint-config.xml:
<jaxws-config xmlns="urn:jboss:jaxws-config:2.0"
xmlns:xsi=" http://www.w3.org/2001/XMLSchema-instance http://www.w3.org/2001/XMLSchema-instance"
xmlns:javaee=" http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee"
xsi:schemaLocation="urn:jboss:jaxws-config:2.0 jaxws-config_2_0.xsd">
<endpoint-config>
<config-name>Seam WebService Endpoint</config-name>
<pre-handler-chains>
<javaee:handler-chain>
<javaee:protocol-bindings>##SOAP11_HTTP</javaee:protocol-bindings>
<javaee:handler>
<javaee:handler-name>SOAP Request Handler</javaee:handler-name>
<javaee:handler-class>org.jboss.seam.webservice.SOAPRequestHandler</javaee:handler-class>
</javaee:handler>
</javaee:handler-chain>
</pre-handler-chains>
</endpoint-config>
</jaxws-config>
The "standard-jaxws-endpoint-config.xml" is necessary for Seam, as described here
http://docs.jboss.org/seam/2.2.2.Final/reference/en-US/html/webservices.html http://docs.jboss.org/seam/2.2.2.Final/reference/en-US/html/webservices.html (Section 24.1)
Environment:
JBoss AS 6.0.0.Final
JBoss Seam 2.2.2 Final
Oracle JDK 1.6.25
Windows XP SP3
I have created a jira issue
https://issues.jboss.org/browse/JBAS-9275 https://issues.jboss.org/browse/JBAS-9275
and was advised to start a discussion here.
JBoss AS 6 uses as Web Services Stack CXF Server 3.4.1.GA, and classpath is
java.class.path: C:\Programme\Java\jdk1.6\lib\tools.jar;C:\programs\jboss-6.0.0.Final\bin\run.jar
java.library.path: C:\programs\jboss-6.0.0.Final\bin\native;C:\programs\jboss-6.0.0.Final\bin;C:\Programme\Java\jdk1.6\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS
sun.boot.class.path: C:\programs\jboss-6.0.0.Final\lib\endorsed\activation.jar;C:\programs\jboss-6.0.0.Final\lib\endorsed\jboss-annotations-api_1.1_spec.jar;C:\programs\jboss-6.0.0.Final\lib\endorsed\jboss-jaxb-api_2.2_spec.jar;C:\programs\jboss-6.0.0.Final\lib\endorsed\jboss-jaxws-api_2.2_spec.jar;C:\programs\jboss-6.0.0.Final\lib\endorsed\jbossws-cxf-factories.jar;C:\programs\jboss-6.0.0.Final\lib\endorsed\stax-api.jar;C:\Programme\Java\jdk1.6\jre\lib\resources.jar;C:\Programme\Java\jdk1.6\jre\lib\rt.jar;C:\Programme\Java\jdk1.6\jre\lib\sunrsasign.jar;C:\Programme\Java\jdk1.6\jre\lib\jsse.jar;C:\Programme\Java\jdk1.6\jre\lib\jce.jar;C:\Programme\Java\jdk1.6\jre\lib\charsets.jar;C:\Programme\Java\jdk1.6\jre\lib\modules\jdk.boot.jar;C:\Programme\Java\jdk1.6\jre\classes
sun.boot.library.path: C:\Programme\Java\jdk1.6\jre\bin
The application is deployed as ear-file (not exploded) with following structure:
app.ear
- META-INF
- app.war
- WEB-INF
- lib
jboss-seam-debug-2.2.2.Final.jar
jboss-seam-jul-2.2.2.Final.jar
jboss-seam-ui-2.2.2.Final.jar
- app.jar
- jboss-seam-2.2.2.Final.jar
- lib
antisamy-1.4.4.jar
backport-util-concurrent-3.1.jar
base64-2.3.7.jar
batik-css-1.7.jar
batik-ext-1.7.jar
batik-util-1.7.jar
commons-beanutils-1.8.3.jar
commons-codec-1.4.jar
commons-digester-1.8.1.jar
commons-httpclient-3.1.jar
commons-lang-2.4.jar
ehcache-core-2.4.2.jar
ical4j-1.0.jar
itext-2.1.7.jar
jasperreports-4.0.1.jar
jasperreports-fonts-4.0.1.jar
jboss-el-1.0_02.CR5.jar
jbpm-jpdl-3.2.3.jar
jcommon-1.0.16.jar
jericho-html-3.1.jar
jfreechart-1.0.13.jar
lucene-analyzers-2.4.1.jar
lucene-core-2.4.1.jar
metadata-extractor-2.4.0-beta1.jar
nekohtml-1.9.14.jar
poi-3.7.jar
poi-ooxml-3.7.jar
poi-ooxml-schemas-3.7.jar
richfaces-api-3.3.3.Final.jar
richfaces-impl-3.3.3.Final.jar
richfaces-ui-3.3.3.Final.jar
simplecaptcha-1.1.1.jar
spring-beans-2.5.5.jar
spring-core-2.5.5.jar
stax-api-1.0.1.jar
xml-apis-ext-1.3.04.jar
xmlbeans-2.3.0.jar
xpp3_min-1.1.4c.jar
xstream-1.3.1.jar
Any ideas?
Thank you for your help.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/604383#604383]
Start a new discussion in JBoss Web Services at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years, 1 month
[Javassist] - running tattletale on solaris
by Aleksandar Kostadinov
Aleksandar Kostadinov [http://community.jboss.org/people/akostadinov] created the discussion
"running tattletale on solaris"
To view the discussion, visit: http://community.jboss.org/message/605093#605093
--------------------------------------------------------------
Hello,
it's strange but trying to run tattletale on one solaris 10 sparc machine we have fails with:
bash-3.00# java -Djava.ext.dirs=`pwd` -jar tattletale-1.1.2.Final.jar share/tomcat5 ttt_tomcat5
Exception in thread "main" java.lang.NoClassDefFoundError: javassist/NotFoundException
at org.jboss.tattletale.Main.execute(Main.java:512)
at org.jboss.tattletale.Main.main(Main.java:1429)
Caused by: java.lang.ClassNotFoundException: javassist.NotFoundException
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at sun.misc.Launcher$ExtClassLoader.findClass(Launcher.java:229)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
... 2 more
It makes no difference how I put javassist on the classpath (although it should be picked up automatically anyways). I have no problems running tattletale on the RHEL machines I have tried. I'm using sun jdk 1.6.0_24 on the solaris.
Any ideas what can be wrong?
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/605093#605093]
Start a new discussion in Javassist at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years, 1 month
[EJB3] - Problem using: 6 Final JBoss, EJB3 (MDB), CMT, EclipseLink, PostgreSQL
by Yumer Lopez
Yumer Lopez [http://community.jboss.org/people/ylopez] created the discussion
"Problem using: 6 Final JBoss, EJB3 (MDB), CMT, EclipseLink, PostgreSQL"
To view the discussion, visit: http://community.jboss.org/message/605050#605050
--------------------------------------------------------------
Hi, I'm new using Jboss.
I have a JEE application using MDB to consume messages from a queue. When the message arrives, it activates a routine to keep a record in the database. The databasemanager I'm using is PostgreSQL 8.4. I use to deploy the application the IDE Eclipse, this is what I get when I deploy the application:
server.log
========================================================================================================
17:26:37,566 INFO [org.jboss.jpa.mcint.beans.metadata.plugins.PersistenceUnitValueMetaData] iDependOn persistence.unit:unitName=jboss-ejb3-timerservice-mk2.jar#timerdb
17:26:37,575 INFO [org.jboss.jpa.deployment.PersistenceUnitDeployment] Starting persistence unit persistence.unit:unitName=jboss-ejb3-timerservice-mk2.jar#timerdb
17:26:37,880 INFO [org.hibernate.annotations.common.Version] Hibernate Commons Annotations 3.2.0.Final
17:26:37,896 INFO [org.hibernate.cfg.Environment] Hibernate 3.6.0.Final
17:26:37,901 INFO [org.hibernate.cfg.Environment] hibernate.properties not found
17:26:37,907 INFO [org.hibernate.cfg.Environment] Bytecode provider name : javassist
17:26:37,913 INFO [org.hibernate.cfg.Environment] using JDK 1.4 java.sql.Timestamp handling
17:26:38,043 INFO [org.hibernate.ejb.Version] Hibernate EntityManager 3.6.0.Final
17:26:38,075 INFO [org.hibernate.ejb.Ejb3Configuration] Processing PersistenceUnitInfo [
name: timerdb
...]
17:26:38,090 WARN [org.hibernate.ejb.Ejb3Configuration] Persistence provider caller does not implement the EJB3 spec correctly.PersistenceUnitInfo.getNewTempClassLoader() is null.
17:26:38,192 INFO [org.hibernate.cfg.AnnotationBinder] Binding entity from annotated class: org.jboss.ejb3.timerservice.mk2.persistence.TimerEntity
17:26:38,237 INFO [org.hibernate.cfg.annotations.EntityBinder] Bind entity org.jboss.ejb3.timerservice.mk2.persistence.TimerEntity on table timer
17:26:38,291 INFO [org.hibernate.cfg.AnnotationBinder] Binding entity from annotated class: org.jboss.ejb3.timerservice.mk2.persistence.TimeoutMethod
17:26:38,294 INFO [org.hibernate.cfg.annotations.EntityBinder] Bind entity org.jboss.ejb3.timerservice.mk2.persistence.TimeoutMethod on table timeout_method
17:26:38,326 INFO [org.hibernate.cfg.AnnotationBinder] Binding entity from annotated class: org.jboss.ejb3.timerservice.mk2.persistence.CalendarTimerEntity
17:26:38,328 INFO [org.hibernate.cfg.annotations.EntityBinder] Bind entity org.jboss.ejb3.timerservice.mk2.persistence.CalendarTimerEntity on table calendar_timer
17:26:38,367 INFO [org.hibernate.validator.Version] Hibernate Validator 3.1.0.GA
17:26:38,417 INFO [org.hibernate.validator.util.Version] Hibernate Validator 4.1.0.Final
17:26:38,430 INFO [org.hibernate.validator.engine.resolver.DefaultTraversableResolver] Instantiated an instance of org.hibernate.validator.engine.resolver.JPATraversableResolver.
17:26:38,598 INFO [org.hibernate.validator.engine.resolver.DefaultTraversableResolver] Instantiated an instance of org.hibernate.validator.engine.resolver.JPATraversableResolver.
17:26:38,603 INFO [org.hibernate.validator.engine.resolver.DefaultTraversableResolver] Instantiated an instance of org.hibernate.validator.engine.resolver.JPATraversableResolver.
17:26:38,610 INFO [org.hibernate.cfg.search.HibernateSearchEventListenerRegister] Unable to find org.hibernate.search.event.FullTextIndexEventListener on the classpath. Hibernate Search is not enabled.
17:26:38,627 INFO [org.hibernate.connection.ConnectionProviderFactory] Initializing connection provider: org.hibernate.ejb.connection.InjectedDataSourceConnectionProvider
17:26:38,634 INFO [org.hibernate.ejb.connection.InjectedDataSourceConnectionProvider] Using provided datasource
17:26:38,640 INFO [org.hibernate.cfg.SettingsFactory] Database ->
name : HSQL Database Engine
version : 1.8.0
major : 1
minor : 8
17:26:38,640 INFO [org.hibernate.cfg.SettingsFactory] Driver ->
name : HSQL Database Engine Driver
version : 1.8.0
major : 1
minor : 8
17:26:38,709 INFO [org.hibernate.dialect.Dialect] Using dialect: org.hibernate.dialect.HSQLDialect
17:26:38,742 INFO [org.hibernate.engine.jdbc.JdbcSupportLoader] Disabling contextual LOB creation as JDBC driver reported JDBC version [3] less than 4
17:26:38,744 INFO [org.hibernate.transaction.TransactionFactoryFactory] Transaction strategy: org.hibernate.ejb.transaction.JoinableCMTTransactionFactory
17:26:38,748 INFO [org.hibernate.transaction.TransactionManagerLookupFactory] instantiating TransactionManagerLookup: org.hibernate.transaction.JBossTransactionManagerLookup
17:26:38,751 INFO [org.hibernate.transaction.TransactionManagerLookupFactory] instantiated TransactionManagerLookup
17:26:38,751 INFO [org.hibernate.cfg.SettingsFactory] Automatic flush during beforeCompletion(): disabled
17:26:38,752 INFO [org.hibernate.cfg.SettingsFactory] Automatic session close at end of transaction: disabled
17:26:38,752 INFO [org.hibernate.cfg.SettingsFactory] JDBC batch size: 15
17:26:38,752 INFO [org.hibernate.cfg.SettingsFactory] JDBC batch updates for versioned data: disabled
17:26:38,753 INFO [org.hibernate.cfg.SettingsFactory] Scrollable result sets: enabled
17:26:38,754 INFO [org.hibernate.cfg.SettingsFactory] JDBC3 getGeneratedKeys(): disabled
17:26:38,754 INFO [org.hibernate.cfg.SettingsFactory] Connection release mode: auto
17:26:38,756 INFO [org.hibernate.cfg.SettingsFactory] Default batch fetch size: 1
17:26:38,756 INFO [org.hibernate.cfg.SettingsFactory] Generate SQL with comments: disabled
17:26:38,756 INFO [org.hibernate.cfg.SettingsFactory] Order SQL updates by primary key: disabled
17:26:38,756 INFO [org.hibernate.cfg.SettingsFactory] Order SQL inserts for batching: disabled
17:26:38,756 INFO [org.hibernate.cfg.SettingsFactory] Query translator: org.hibernate.hql.ast.ASTQueryTranslatorFactory
17:26:38,762 INFO [org.hibernate.hql.ast.ASTQueryTranslatorFactory] Using ASTQueryTranslatorFactory
17:26:38,762 INFO [org.hibernate.cfg.SettingsFactory] Query language substitutions: {}
17:26:38,762 INFO [org.hibernate.cfg.SettingsFactory] JPA-QL strict compliance: enabled
17:26:38,762 INFO [org.hibernate.cfg.SettingsFactory] Second-level cache: enabled
17:26:38,762 INFO [org.hibernate.cfg.SettingsFactory] Query cache: disabled
17:26:38,764 INFO [org.hibernate.cfg.SettingsFactory] Cache region factory : org.hibernate.cache.impl.bridge.RegionFactoryCacheProviderBridge
17:26:38,772 INFO [org.hibernate.cache.impl.bridge.RegionFactoryCacheProviderBridge] Cache provider: org.hibernate.cache.HashtableCacheProvider
17:26:38,775 INFO [org.hibernate.cfg.SettingsFactory] Optimize cache for minimal puts: disabled
17:26:38,775 INFO [org.hibernate.cfg.SettingsFactory] Cache region prefix: persistence.unit:unitName=jboss-ejb3-timerservice-mk2.jar#timerdb
17:26:38,775 INFO [org.hibernate.cfg.SettingsFactory] Structured second-level cache entries: disabled
17:26:38,784 INFO [org.hibernate.cfg.SettingsFactory] Statistics: disabled
17:26:38,784 INFO [org.hibernate.cfg.SettingsFactory] Deleted entity synthetic identifier rollback: disabled
17:26:38,784 INFO [org.hibernate.cfg.SettingsFactory] Default entity-mode: pojo
17:26:38,784 INFO [org.hibernate.cfg.SettingsFactory] Named query checking : enabled
17:26:38,784 INFO [org.hibernate.cfg.SettingsFactory] Check Nullability in Core (should be disabled when Bean Validation is on): disabled
17:26:38,815 INFO [org.hibernate.impl.SessionFactoryImpl] building session factory
17:26:39,055 INFO [org.hibernate.impl.SessionFactoryObjectFactory] Factory name: persistence.unit:unitName=jboss-ejb3-timerservice-mk2.jar#timerdb
17:26:39,057 INFO [org.hibernate.util.NamingHelper] JNDI InitialContext properties:{java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory, java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces}
17:26:39,060 INFO [org.hibernate.impl.SessionFactoryObjectFactory] Bound factory to JNDI name: persistence.unit:unitName=jboss-ejb3-timerservice-mk2.jar#timerdb
17:26:39,060 WARN [org.hibernate.impl.SessionFactoryObjectFactory] InitialContext did not implement EventContext
17:26:39,068 INFO [org.hibernate.tool.hbm2ddl.SchemaUpdate] Running hbm2ddl schema update
17:26:39,069 INFO [org.hibernate.tool.hbm2ddl.SchemaUpdate] fetching database metadata
17:26:39,070 INFO [org.hibernate.tool.hbm2ddl.SchemaUpdate] updating schema
17:26:39,072 INFO [org.hibernate.validator.engine.resolver.DefaultTraversableResolver] Instantiated an instance of org.hibernate.validator.engine.resolver.JPATraversableResolver.
17:26:39,096 INFO [org.hibernate.tool.hbm2ddl.TableMetadata] table found: PUBLIC.TIMEOUTMETHOD_METHODPARAMS
17:26:39,097 INFO [org.hibernate.tool.hbm2ddl.TableMetadata] columns: [methodparams, timeoutmethod_id]
17:26:39,097 INFO [org.hibernate.tool.hbm2ddl.TableMetadata] foreign keys: [fkf294c964b7de2d8a]
17:26:39,097 INFO [org.hibernate.tool.hbm2ddl.TableMetadata] indexes: [sys_idx_55]
17:26:39,110 INFO [org.hibernate.tool.hbm2ddl.TableMetadata] table found: PUBLIC.CALENDAR_TIMER
17:26:39,111 INFO [org.hibernate.tool.hbm2ddl.TableMetadata] columns: [scheduleexprtimezone, scheduleexprsecond, autotimer, scheduleexprstartdate, scheduleexprminute, scheduleexprhour, timeoutmethod_id, id, scheduleexprdayofmonth, scheduleexprenddate, scheduleexprmonth, scheduleexprdayofweek, scheduleexpryear]
17:26:39,111 INFO [org.hibernate.tool.hbm2ddl.TableMetadata] foreign keys: [fk2b697f04b7de2d8a, fk2b697f04e6e6ef93]
17:26:39,111 INFO [org.hibernate.tool.hbm2ddl.TableMetadata] indexes: [sys_idx_57, sys_idx_49, sys_idx_59]
17:26:39,122 INFO [org.hibernate.tool.hbm2ddl.TableMetadata] table found: PUBLIC.TIMEOUT_METHOD
17:26:39,122 INFO [org.hibernate.tool.hbm2ddl.TableMetadata] columns: [id, methodname, declaringclass]
17:26:39,122 INFO [org.hibernate.tool.hbm2ddl.TableMetadata] foreign keys: []
17:26:39,122 INFO [org.hibernate.tool.hbm2ddl.TableMetadata] indexes: [sys_idx_51]
17:26:39,136 INFO [org.hibernate.tool.hbm2ddl.TableMetadata] table found: PUBLIC.TIMER
17:26:39,136 INFO [org.hibernate.tool.hbm2ddl.TableMetadata] columns: [id, previousrun, initialdate, repeatinterval, timedobjectid, timerstate, nextdate, info]
17:26:39,136 INFO [org.hibernate.tool.hbm2ddl.TableMetadata] foreign keys: []
17:26:39,136 INFO [org.hibernate.tool.hbm2ddl.TableMetadata] indexes: [sys_idx_53]
17:26:39,138 INFO [org.hibernate.tool.hbm2ddl.SchemaUpdate] schema update complete
17:26:39,142 INFO [org.hibernate.util.NamingHelper] JNDI InitialContext properties:{java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory, java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces}
17:26:39,206 INFO [org.jboss.ejb3.deployers.Ejb3DependenciesDeployer] Encountered deployment AbstractVFSDeploymentContext@1890779401{vfs:///home/yumer/EclipseProjects/.metadata/.plugins/org.jboss.ide.eclipse.as.core/JBoss_6.0_Runtime_Server1305132052402/deploy/JBoss-EJB%20MDB%20Tutorial.jar}
17:26:39,207 INFO [org.jboss.ejb3.deployers.Ejb3DependenciesDeployer] Encountered deployment AbstractVFSDeploymentContext@1890779401{vfs:///home/yumer/EclipseProjects/.metadata/.plugins/org.jboss.ide.eclipse.as.core/JBoss_6.0_Runtime_Server1305132052402/deploy/JBoss-EJB%20MDB%20Tutorial.jar}
17:26:39,226 INFO [org.jboss.ejb3.instantiator.deployer.BeanInstantiatorDeployerBase] Installed org.jboss.ejb3.instantiator.impl.Ejb31SpecBeanInstantiator@ec3b565 into MC at org.jboss.ejb.bean.instantiator/JBoss-EJB MDB Tutorial/JBoss-EJB MDB Tutorial/MyMDB
17:26:39,233 WARN [org.jboss.ejb3.interceptor.InterceptorInfoRepository] EJBTHREE-1852: InterceptorInfoRepository is deprecated
17:26:39,674 INFO [org.jboss.ejb3.deployers.JBossASKernel] Created KernelDeployment for: JBoss-EJB MDB Tutorial.jar
17:26:39,676 INFO [org.jboss.ejb3.deployers.JBossASKernel] installing bean: jboss.j2ee:jar=JBoss-EJB MDB Tutorial.jar,name=MyMDB,service=EJB3
17:26:39,676 INFO [org.jboss.ejb3.deployers.JBossASKernel] with dependencies:
17:26:39,676 INFO [org.jboss.ejb3.deployers.JBossASKernel] and demands:
17:26:39,676 INFO [org.jboss.ejb3.deployers.JBossASKernel] jboss.ejb:service=EJBTimerService; Required: Described
17:26:39,677 INFO [org.jboss.ejb3.deployers.JBossASKernel] persistence.unit:unitName=JBoss-EJB MDB Tutorial.jar#JPA-prueba; Required: Described
17:26:39,677 INFO [org.jboss.ejb3.deployers.JBossASKernel] jboss-injector:topLevelUnit=JBoss-EJB MDB Tutorial.jar,unit=JBoss-EJB MDB Tutorial.jar,bean=MyMDB; Required: Described
17:26:39,677 INFO [org.jboss.ejb3.deployers.JBossASKernel] jboss-switchboard:appName=JBoss-EJB MDB Tutorial,module=JBoss-EJB MDB Tutorial,name=MyMDB; Required: Create
17:26:39,677 INFO [org.jboss.ejb3.deployers.JBossASKernel] and supplies:
17:26:39,677 INFO [org.jboss.ejb3.deployers.JBossASKernel] jndi:null
17:26:39,677 INFO [org.jboss.ejb3.deployers.JBossASKernel] Class:javax.jms.MessageListener
17:26:39,678 INFO [org.jboss.ejb3.deployers.JBossASKernel] Added bean(jboss.j2ee:jar=JBoss-EJB MDB Tutorial.jar,name=MyMDB,service=EJB3) to KernelDeployment of: JBoss-EJB MDB Tutorial.jar
17:26:39,722 INFO [org.jboss.jpa.deployment.PersistenceUnitDeployment] Starting persistence unit persistence.unit:unitName=JBoss-EJB MDB Tutorial.jar#JPA-prueba
17:26:39,764 INFO [org.jboss.ejb3.EJBContainer] STARTED EJB: com.my.jms.tutorial.MyMDB ejbName: MyMDB
17:26:39,799 WARN [org.jboss.ejb3.TimerServiceContainer] EJBTHREE-2193: using deprecated TimerServiceFactory for restoring timers
========================================================================================================
I want to use CMT, but I get the following error:
Stacktrace:
========================================================================================================
17:32:22,188 INFO [STDOUT] ----------------
17:32:22,188 INFO [STDOUT] Received message :
17:32:22,188 INFO [STDOUT] Hello World
17:32:22,189 INFO [STDOUT] ------D----------
17:32:22,189 ERROR [org.jboss.ejb3.tx2.impl.CMTTxInterceptor] javax.ejb.EJBTransactionRolledbackException:
Exception Description: No transaction is currently active
17:32:22,189 ERROR [org.hornetq.ra.inflow.HornetQMessageHandler] Failed to deliver message: javax.ejb.EJBTransactionRolledbackException:
Exception Description: No transaction is currently active
at org.jboss.ejb3.tx2.impl.CMTTxInterceptor.handleInCallerTx(CMTTxInterceptor.java:148) [:0.0.1]
at org.jboss.ejb3.tx2.impl.CMTTxInterceptor.invokeInCallerTx(CMTTxInterceptor.java:227) [:0.0.1]
at org.jboss.ejb3.tx2.impl.CMTTxInterceptor.required(CMTTxInterceptor.java:353) [:0.0.1]
at org.jboss.ejb3.tx2.impl.CMTTxInterceptor.invoke(CMTTxInterceptor.java:209) [:0.0.1]
at org.jboss.ejb3.tx2.aop.CMTTxInterceptorWrapper.invoke(CMTTxInterceptorWrapper.java:52) [:0.0.1]
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) [jboss-aop.jar:2.2.1.GA]
at org.jboss.ejb3.tx.NullInterceptor.invoke(NullInterceptor.java:42) [:1.0.3]
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) [jboss-aop.jar:2.2.1.GA]
at org.jboss.ejb3.security.Ejb3AuthenticationInterceptorv2.invoke(Ejb3AuthenticationInterceptorv2.java:79) [:1.7.17]
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) [jboss-aop.jar:2.2.1.GA]
at org.jboss.ejb3.BlockContainerShutdownInterceptor.invoke(BlockContainerShutdownInterceptor.java:67) [:1.7.17]
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) [jboss-aop.jar:2.2.1.GA]
at org.jboss.ejb3.core.context.CurrentInvocationContextInterceptor.invoke(CurrentInvocationContextInterceptor.java:47) [:1.7.17]
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) [jboss-aop.jar:2.2.1.GA]
at org.jboss.aspects.currentinvocation.CurrentInvocationInterceptor.invoke(CurrentInvocationInterceptor.java:67) [:1.0.1]
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) [jboss-aop.jar:2.2.1.GA]
at org.jboss.ejb3.interceptor.EJB3TCCLInterceptor.invoke(EJB3TCCLInterceptor.java:86) [:1.7.17]
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) [jboss-aop.jar:2.2.1.GA]
at org.jboss.ejb3.mdb.MessagingContainer.localInvoke(MessagingContainer.java:306) [:1.7.17]
at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.delivery(MessageInflowLocalProxy.java:299) [:1.7.17]
at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:152) [:1.7.17]
at $Proxy191.onMessage(Unknown Source) at org.hornetq.ra.inflow.HornetQMessageHandler.onMessage(HornetQMessageHandler.java:256) [:6.0.0.Final]
at org.hornetq.core.client.impl.ClientConsumerImpl.callOnMessage(ClientConsumerImpl.java:822) [:6.0.0.Final]
at org.hornetq.core.client.impl.ClientConsumerImpl.access$100(ClientConsumerImpl.java:46) [:6.0.0.Final]
at org.hornetq.core.client.impl.ClientConsumerImpl$Runner.run(ClientConsumerImpl.java:940) [:6.0.0.Final]
at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:100) [:6.0.0.Final]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [:1.6.0_18]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [:1.6.0_18]
at java.lang.Thread.run(Thread.java:636) [:1.6.0_18]
Caused by: javax.persistence.TransactionRequiredException:
Exception Description: No transaction is currently active
at org.eclipse.persistence.internal.jpa.transaction.EntityTransactionWrapper.throwCheckTransactionFailedException(EntityTransactionWrapper.java:113) [:2.2.0.v20110202-r8913]
at org.eclipse.persistence.internal.jpa.transaction.EntityTransactionWrapper.checkForTransaction(EntityTransactionWrapper.java:50) [:2.2.0.v20110202-r8913]
at org.eclipse.persistence.internal.jpa.EntityManagerImpl.checkForTransaction(EntityManagerImpl.java:1666) [:2.2.0.v20110202-r8913]
at org.eclipse.persistence.internal.jpa.EntityManagerImpl.joinTransaction(EntityManagerImpl.java:1698) [:2.2.0.v20110202-r8913]
at org.jboss.jpa.deployment.ManagedEntityManagerFactory.getTransactionScopedEntityManager(ManagedEntityManagerFactory.java:190) [:1.0.2-alpha-3]
at org.jboss.jpa.deployment.PersistenceUnitDeployment.getTransactionScopedEntityManager(PersistenceUnitDeployment.java:178) [:1.0.2-alpha-3]
at org.jboss.jpa.impl.tx.TransactionScopedEntityManager.getEntityManager(TransactionScopedEntityManager.java:262) [:2.0.0]
at org.jboss.jpa.impl.tx.TransactionScopedEntityManager.persist(TransactionScopedEntityManager.java:206) [:2.0.0]
at com.my.jms.tutorial.MyMDB.onMessage(MyMDB.java:54) [:]
at sun.reflect.GeneratedMethodAccessor291.invoke(Unknown Source) [:1.6.0_18]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [:1.6.0_18]
at java.lang.reflect.Method.invoke(Method.java:616) [:1.6.0_18]
at org.jboss.aop.joinpoint.MethodInvocation.invokeTarget(MethodInvocation.java:122) [jboss-aop.jar:2.2.1.GA]
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:111) [jboss-aop.jar:2.2.1.GA]
at org.jboss.ejb3.interceptors.container.ContainerMethodInvocationWrapper.invokeNext(ContainerMethodInvocationWrapper.java:72) [:1.1.3]
at org.jboss.ejb3.interceptors.aop.InterceptorSequencer.invoke(InterceptorSequencer.java:76) [:1.1.3]
at org.jboss.ejb3.interceptors.aop.InterceptorSequencer.aroundInvoke(InterceptorSequencer.java:62) [:1.1.3]
at sun.reflect.GeneratedMethodAccessor290.invoke(Unknown Source) [:1.6.0_18]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [:1.6.0_18]
at java.lang.reflect.Method.invoke(Method.java:616) [:1.6.0_18]
at org.jboss.aop.advice.PerJoinpointAdvice.invoke(PerJoinpointAdvice.java:174) [jboss-aop.jar:2.2.1.GA]
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) [jboss-aop.jar:2.2.1.GA]
at org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor.fillMethod(InvocationContextInterceptor.java:74) [:1.1.3]
at org.jboss.aop.advice.org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor_z_fillMethod_6395852.invoke(InvocationContextInterceptor_z_fillMethod_6395852.java) [:]
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) [jboss-aop.jar:2.2.1.GA]
at org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor.setup(InvocationContextInterceptor.java:90) [:1.1.3]
at org.jboss.aop.advice.org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor_z_setup_6395852.invoke(InvocationContextInterceptor_z_setup_6395852.java) [:]
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) [jboss-aop.jar:2.2.1.GA]
at org.jboss.ejb3.async.impl.interceptor.AsynchronousServerInterceptor.invoke(AsynchronousServerInterceptor.java:110) [:1.7.17]
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) [jboss-aop.jar:2.2.1.GA]
at org.jboss.ejb3.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionInterceptor.java:62) [:1.7.17]
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) [jboss-aop.jar:2.2.1.GA]
at org.jboss.ejb3.entity.TransactionScopedEntityManagerInterceptor.invoke(TransactionScopedEntityManagerInterceptor.java:56) [:1.7.17]
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) [jboss-aop.jar:2.2.1.GA]
at org.jboss.ejb3.AllowedOperationsInterceptor.invoke(AllowedOperationsInterceptor.java:47) [:1.7.17]
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) [jboss-aop.jar:2.2.1.GA]
at org.jboss.ejb3.tx.NullInterceptor.invoke(NullInterceptor.java:42) [:1.0.3]
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) [jboss-aop.jar:2.2.1.GA]
at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:68) [:1.7.17]
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) [jboss-aop.jar:2.2.1.GA]
at org.jboss.ejb3.core.context.InvocationContextAdapter.proceed(InvocationContextAdapter.java:70) [:1.7.17]
at org.jboss.ejb3.tx2.impl.CMTTxInterceptor.invokeInCallerTx(CMTTxInterceptor.java:223) [:0.0.1]
... 28 more
========================================================================================================
This is my MBD:
========================================================================================================
package com.my.jms.tutorial;
import com.my.jpa.*;
import javax.ejb.ActivationConfigProperty;
import javax.ejb.MessageDriven;
import javax.ejb.TransactionAttribute;
import javax.ejb.TransactionAttributeType;
import javax.ejb.TransactionManagement;
import javax.ejb.TransactionManagementType;
import javax.jms.JMSException;
import javax.jms.Message;
import javax.jms.MessageListener;
import javax.jms.TextMessage;
import javax.persistence.PersistenceContext;
import javax.persistence.EntityManager;
@MessageDriven(
activationConfig =
{ @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue"),
@ActivationConfigProperty(propertyName="destination", propertyValue="queue/MyQueue"),
@ActivationConfigProperty(propertyName = "user", propertyValue = "guest")
}
)
public class MyMDB implements MessageListener {
@PersistenceContext(unitName = "JPA-prueba") EntityManager em;
public MyMDB() {
}
@TransactionAttribute(TransactionAttributeType.REQUIRED)
public void onMessage(Message message) {
try {
if (!message.getJMSRedelivered()){
System.out.println("----------------");
System.out.println("Received message : ");
if (message instanceof TextMessage) {
try {
System.out.println(((TextMessage) message).getText());
} catch (JMSException e) {
// TODO Auto-generated catch block
e.printStackTrace();
}
}
System.out.println("------D----------");
TemporalSm temporal = new TemporalSm();
temporal.setAni((long) 2414);
temporal.setDnis(3);
temporal.setContent("contenido");
temporal.setContext("contexto");
em.persist(temporal);
System.out.println("Here");
}
} catch (JMSException e) {
// TODO Auto-generated catch block
e.printStackTrace();
}
}
}
========================================================================================================
Jbos it's telling me: "No transaction is currently active" but I'm marking that the transactions are handled by the container (the default). This is logical? Am I doing something wrong?
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/605050#605050]
Start a new discussion in EJB3 at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years, 1 month
[JBoss Tools] - JBoss Tools Milestone for Eclipse 3.7 M6 (Indigo)
by Max Rydahl Andersen
Max Rydahl Andersen [http://community.jboss.org/people/maxandersen] modified the blog post:
"JBoss Tools Milestone for Eclipse 3.7 M6 (Indigo)"
To view the blog post, visit: http://community.jboss.org/community/tools/blog/2011/05/12/jboss-tools-mi...
--------------------------------------------------------------
Eclipse 3.7 is coming out soon and we are happy to deliver the first milestone of JBoss Tools targeting the upcoming Eclipse Indigo release.
http://in.relation.to/service/File/10824 http://in.relation.to/service/File/10824
h4. 3.3.0.M1 (Forge On!)
[ http://www.jboss.org/tools/download Download] [ http://download.jboss.org/jbosstools/updates/development/indigo/ Update Site] [ http://docs.jboss.org/tools/whatsnew/index.html What's New] [ http://docs.jboss.org/tools/movies/ Movies] [ http://docs.jboss.org/tools/3.1.0.GA/ Documentation (not updated yet)] [ http://www.jboss.com/index.html?module=bb&op=viewforum&f=201 Forums] [ http://jira.jboss.com/jira/browse/JBIDE JIRA] [ http://twitter.com/jbosstools Twitter]
This is a development release in its true form which requires Eclipse 3.7 M6 to run.
If you use Eclipse 3.7 M7 things will install, but there have been API changes between M6 and M7 so please follow the installation instructions below very carefully to avoid problems.
h2. Installation
Read this very carefully - if you don't follow this you *will* have problems running this milestone since Eclipse 3.7 M7 is not compatible with Eclipse 3.7 M6.
1. Download & http://http://www.eclipse.org/downloads/packages/eclipse-ide-java-ee-deve... Install Eclipse 3.7 M6a (Indigo) JEE bundle.
2. Run and add this URL to Eclipse's list of available update sites: http://download.jboss.org/jbosstools/updates/development/indigo http://download.jboss.org/jbosstools/updates/development/indigo
3. Disable all other URL's except that URL and this
http://download.jboss.org/jbosstools/updates/indigo/M6/ http://download.jboss.org/jbosstools/updates/indigo/M6/
4. Now go and install the JBoss Tools components you want from the JBoss Tools updatesite
Step #3 is the important one - this prevents P2 from overriding your M6 installation with M7 updates.
https://issues.jboss.org/browse/JBIDE-8907 This Jira explains the details for this with screenshots if the above text is causing problems.
h2. New & Noteworthy
The biggest change is for this release is definitely the Eclipse 3.7 compatiblity but besides that and a bunch of bugfixes and minor improvements we have more than a few exciting new features in this release.
h3. JBoss AS 7
This release introduces a server adapter which allows you to start/stop/debug and deploy applications to JBoss AS 7 via the file system.
If you haven't tried out JBoss AS 7 now is the time - it starts a in approximate 3 seconds; it's like night and day compared to previous AS versions.
h3. CDI/Seam Solder
The CDI tools have added additional features and bugfixes, but most importantly we now support components based of Seam Solder allowing us to pickup and identify CDI and Seam 3 components that uses the Seam Solder extensions. i.e. we will now honor the Seam Solder annotation @Veto to ignore otherwise valid CDI components. The full list of supported annotations from Seam Solder so far is:
* @Veto
@Requires
@Exact
@MessageLogger
@MessageBundle
@DefaultBean
@Unwraps
@ServiceHandlerType
@FullyQualified
@Resource
In addition to support Seam Solder annotations we also support components defined in Seam Config providng an Seam Config aware XML editor and pickup components defined and configured via XML in additon to annotations.
h3. Forge Tools
Our Forge Tools which are integrating http://seamframework.org/Documentation/SeamForge Seam Forge into the Eclipse IDE is now bundled in JBoss Tools and allows you to use Seam Forge out of the box from inside Eclipse.
Seam Forge is core framework for rapid-application development in a standards-based environment; it provides a command line style shell for rapid scaffolding style development. The special thing about Seam Forge is that the motivation behind it is to support standards such as Java EE, CDI and JPA in addition to common defacto technologies such as git and maven.
In its current release it allows you to easily create CDI based applications based on scaffolding principles as known
from tools like seam-gen, ruby-on-rails, grails etc.
This first release of Forge Tools are focusing on bringing the command shell experience directly available in Eclipse as a console so you can
interact directly with Forge meaning you can execute and run Forge commands directly from IDE and as an extra nice bonus it imports and open projects you have created via the shell. It allows you to use the power of command line shell's together with the visual and integrated developer environment.
Koen made a very nice video of all this in play which I've embedded here below. You can see the details of what is shown in the
http://community.jboss.org/community/tools/blog/2011/05/11/have-your-cake... demo on his blog.
Media Description: Link: http://www.vimeo.com/moogaloop.swf?clip_id=23585936&server=www.vimeo.com&...
h3. Maven
What you might not notice in this demo is that it is using m2e/wtp and the JBoss Tools specific m2e configurators behind the scenes to
automatically have the related plugins for the project automatically configured based on the Maven metadata instead of you having to manually configure and setup the tools.
In upcoming releases of JBoss Tools you will see even tighter integration with Seam Forge and with Maven to make you even more productive in working with JEE 6 based technologies.
h3. ...and more
The http:// new and noteworthy provides a short overview with screenshots of the various improvements made in JBoss Tools extensive plugin set.
h2. Next Steps
This release is mostly to get feedback on any issues found in Eclipse 3.7, and to introduce some of work that we are doing to provide a faster and more developer friendly developer environment than ever before - this includes Forge Tools and AS 7 for now but we will also focus on making tools such as Maven easier and faster to use.
We've already contributed several patches to m2e which makes it up to 5 times faster in importing and updating project configuration - these improvements will be available soon from our nightly build site if you can't wait :)
JBoss Tools 3.3 will also continue to make it easier to configure and install JBoss and other runtimes and frameworks to allow you as developer to focus on the code instead of the configuration - at least upfront.
We also have a few other ideas, but we'll save that for some future blogs :)
Do remember though that we really appreciate feedback on wether the functionallity is helping you, if it is going in the right direction and if you have ideas for improvements or even patches.
We are listing and reacting in both forums, jira, twitter and irc.
Enjoy this milestone - remember to read the installation instructions careful! and...
Have Fun!
--------------------------------------------------------------
Comment by going to Community
[http://community.jboss.org/community/tools/blog/2011/05/12/jboss-tools-mi...]
13 years, 1 month