[JBoss Tools (users)] - Re: This IDE won't update?
by avbentem
I'm with alexg79: unofficial roadmaps are appreciated!
> [...] That was fixed a long ago in the CVS
The JBoss IDE feature.xml can be found here. I'm not sure what version alexg79 refers to though (see also the Feature manifest help).
Note that JBoss IDE 2.0.0 Beta 2 cannot be installed into an Eclipse 3.3 milestone using the JBoss update site, yielding the errors below. See JBIDE-471.
JST Common Core (1.5.1.v200608082030--0842282_363739) requires feature "org.eclipse.platform (3.2.0)", or equivalent.
JST Server Core (1.5.1.v200608082030--2PD88P8UBJx787) requires feature "org.eclipse.platform (3.2.0)", or equivalent.
JST Web Core (1.5.1.v200608082030--87cMN7NRVeVWXd) requires feature "org.eclipse.platform (3.2.0)", or equivalent.
JST Enterprise Core (1.5.1.v200609051533--2PD88P8YAGDADJ) requires feature "org.eclipse.platform (3.2.0)", or equivalent.
JST Enterprise UI (1.5.1.v200608082030-pEBq_haA1H4sJf6) requires feature "org.eclipse.platform (3.2.0)", or equivalent.
WST Server Core (1.5.1.v200608082030------1G955G5L7D) requires feature "org.eclipse.rcp (3.2.0)", or equivalent.
WST XML Core (1.5.1.v200608082030--3YIAAYAjGLENFH) requires feature "org.eclipse.rcp (3.2.0)", or equivalent.
WST Web Services Core (1.5.1.v200608082030--4hNDDhDvGTJSLf) requires feature "org.eclipse.platform (3.2.0)", or equivalent.
WST Web Core (1.5.1.v200608082030--4hNDDhDvKRFXQM) requires feature "org.eclipse.platform (3.2.0)", or equivalent.
WST Relational Database Core (1.5.1.v200608082030--3YIAAYAeEKFTFU) requires feature "org.eclipse.platform (3.2.0)", or equivalent.
WST Relational Database Adapters (1.5.1.v200608082030--Cq0bcpdJw4teC8) requires feature "org.eclipse.platform (3.2.0)", or equivalent.
JBossIDE JBossAS Adapter Feature (1.0.0.Beta2) requires plug-in "org.eclipse.ui.workbench.texteditor (3.2.0)", or equivalent.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4040194#4040194
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4040194
19 years
[JBoss Messaging] - [BisocketServerInvoker] unrecognized listener ID: ...
by Smurfs
I've migrated a MDB from JBossMQ to JBoss Messaging which works as expected, however I am getting 'unrecognised listener ID' warning each time it fires, and also when the JBoss server instance shuts down. Here's an excerpt from the server output:
| ...
| 14:26:40,328 WARN [BisocketServerInvoker] unrecognized listener ID: a00h-citaru-f0we4a0g-1-f0we6jfw-1s
| 14:28:39,609 WARN [BisocketServerInvoker] unrecognized listener ID: a00h-citaru-f0we4a0g-1-f0we940c-1y
| 14:30:39,046 WARN [BisocketServerInvoker] unrecognized listener ID: a00h-citaru-f0we4a0g-1-f0webol9-25
| 14:31:22,218 INFO [Server] Runtime shutdown hook called, forceHalt: true
| 14:31:22,234 INFO [Server] JBoss SHUTDOWN: Undeploying all packages
| 14:31:22,234 INFO [TomcatDeployer] undeploy, ctxPath=/, warUrl=.../tmp/deploy/tmp34832fcs.ear-contents/fcs-exp.war/
| 14:31:22,265 WARN [BisocketServerInvoker] unrecognized listener ID: a00h-citaru-f0we4a0g-1-f0we5fbg-t
| 14:31:22,281 WARN [BisocketServerInvoker] unrecognized listener ID: a00h-citaru-f0we4a0g-1-f0we5ebu-h
| 14:31:22,281 WARN [BisocketServerInvoker] unrecognized listener ID: a00h-citaru-f0we4a0g-1-f0we5f8u-q
| 14:31:22,296 WARN [BisocketServerInvoker] unrecognized listener ID: a00h-citaru-f0we4a0g-1-f0we5ebf-f
| 14:31:22,343 INFO [SessionFactoryImpl] closing
| ...
|
It does not appear to affect the operation of the MDB so I'm not too concerned at the moment, however I would like to get rid of the warnings if possible so could someone advise if I've missed a configuration setting (or something else?).
Thanks in advance
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4040192#4040192
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4040192
19 years
[Management, JMX/JBoss] - Re: getting a Controller
by alesj
There is a jsr88-service.xml:
| <server>
| <mbean code="org.jboss.deployment.services.DeploymentManagerService"
| name="jboss.management.local:type=JSR88DeploymentManager,name=DefaultManager">
| <!-- The DeploymentContext attachment types that identify each deployment
| type
| -->
| <attribute name="EarDeployerType">org.jboss.deployment.J2eeApplicationMetaData</attribute>
| <attribute name="EjbDeployerType">org.jboss.metadata.ApplicationMetaData</attribute>
| <attribute name="Ejb3DeployerType">org.jboss.ejb3.Ejb3Deployment</attribute>
| <attribute name="RarDeployerType">org.jboss.resource.metadata.ConnectorMetaData</attribute>
| <attribute name="WarDeployerType">org.jboss.metadata.WebMetaData</attribute>
| <attribute name="CarDeployerType">org.jboss.ejb3.metamodel.ApplicationClientDD</attribute>
| <!-- The MainDeployer to process deployments -->
| <attribute name="MainDeployer"><inject bean="MainDeployer" /></attribute>
| <attribute name="UploadDir">${jboss.server.temp.dir}/jsr88</attribute>
| <!-- If false, the an existing deployment may exist in the upload dir -->
| <attribute name="FailOnCollision">false</attribute>
| <!-- If false, the deployment is retained in the upload dir -->
| <attribute name="DeleteOnUndeploy">false</attribute>
| </mbean>
| </server>
|
You can just add
| <attribute name="kernel"><inject bean="jboss.kernel:service=Kernel"/></attribute>
|
and get an underlying Kernel instance.
>From there you get Controller. ;-)
Or get it directly
| <attribute name="controller"><inject bean="jboss.kernel:service=KernelController"/></attribute>
|
Of course, both need new setter in DeploymentManagerService + instance ref. :-)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4040184#4040184
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4040184
19 years