[JBoss Cache] - Migrating JBoss cache in JBoss 5.1.0
by Prabhu Natarajan
Prabhu Natarajan [http://community.jboss.org/people/prabhun] created the discussion
"Migrating JBoss cache in JBoss 5.1.0"
To view the discussion, visit: http://community.jboss.org/message/588771#588771
--------------------------------------------------------------
Hi,
Earlier I have wrongly posted this in Installation and Configuration forum:
I am involved in migrating JBoss AS from 4.2.3 to 5.1.0
We had a JBoss cache version 1.2.4 that is shipped with JBoss 4.2.3. Now when I migrate to JBoss 5.1.0 I got the below error.
org.jboss.deployers.spi.DeploymentException: Error deploying: Cyrus.cache:service=TreeCache,type=Listener
Deployment "vfszip:/E:/apps/jboss-5.1.0.GA/server/all/deploy/listenerservice-1.3.8-tui.ear/" is in error due to the following reason(s): java.lang.NoSuchFieldError: name
Then I realised I need to migrate JBoss cache also which I did [Jboss cache version 3.1.0]. However now I am getting the below error
2011-02-17 17:03:02,824 ERROR /thread/org.jboss.kernel.plugins.dependency.AbstractKernelController org.jboss.kernel.plugins.dependency.AbstractKernelController (ResourceContainer.invoker.nonDaemon-1) Error installing to Create: name=Cyrus.cache:service=TreeCache,type=Listener state=Configured mode=Manual requiredState=Create
org.jboss.cache.config.ConfigurationException: Must call setConfiguration() or setCache() before call to create()
Our setup is as below
We use xdoclet to generate the required artifacts.
xdoclet generates the *jboss-service.xml*. It uses a jboss-service.ent file which is under the nerge directory
jboss-service.ent has the following entries for JBoss 4,
For JBoss 5.1.0 I have changed that as below
In the code no where I could find TreeCache.start() or create(), I think this is handled internally within TreeCache. Thats why just having an entry org.jboss.cache.TreeCache in the jboss-service.xml created and started the Cache ?
However I think this approach will not work with CacheJmxWrapper in JBoss 5.1.0
Do I need to follow the steps provided in section 4.2. JMX-Based Deployment in JBoss AS (JBoss AS 5.x and 4.x) here
http://docs.jboss.org/jbosscache/2.1.0.GA/userguide_en/html_single/index.... http://docs.jboss.org/jbosscache/2.1.0.GA/userguide_en/html_single/index....
to get the cache created and started?
Regards,
Prabhu
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/588771#588771]
Start a new discussion in JBoss Cache at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
15 years, 1 month
[JBoss Web Services] - Problem Installing JBossWS - class not found
by Frank Lawlor
Frank Lawlor [http://community.jboss.org/people/flawlor] created the discussion
"Problem Installing JBossWS - class not found"
To view the discussion, visit: http://community.jboss.org/message/588421#588421
--------------------------------------------------------------
I downloaded jbossws-native-bin-dist and followed the directions to install it into jboss-6.0.0.M2. All seemed to go OK. However, when I started the JBoss server it complained that it could not find org/jboss/wsf/spi/http/HttpServer :
...
14:01:44,948 INFO [JMXKernel] Legacy JMX core initialized
14:01:48,917 ERROR [AbstractKernelController] Error installing to Real: name=vfsfile:/C:/JBoss/jboss-6.0.0.M2/server/default/deployers/jbossws.deployer/ state=PreReal mode=Manual requiredState=Real: org.jboss.deployers.spi.DeploymentException: Error deploying: vfsfile:/C:/JBoss/jboss-6.0.0.M2/server/default/deployers/jbossws.deployer/
at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
at org.jboss.deployers.spi.deployer.helpers.AbstractDeploymentVisitor.deploy(AbstractDeploymentVisitor.java:83)
at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployerWithInput.deploy(AbstractRealDeployerWithInput.java:125)
at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployerWithInput.internalDeploy(AbstractRealDeployerWithInput.java:102)
at org.jboss.deployers.spi.deployer.helpers.AbstractComponentDeployer.internalDeploy(AbstractComponentDeployer.java:78)
at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:55)
at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:179)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1660)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1378)
at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1319)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:378)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:2029)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:1050)
at org.jboss.dependency.plugins.AbstractController.executeOrIncrementStateDirectly(AbstractController.java:1289)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1213)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1107)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:918)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:633)
at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:898)
at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:677)
at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117)
at org.jboss.system.server.profileservice.repository.ProfileDeployAction.install(ProfileDeployAction.java:70)
at org.jboss.system.server.profileservice.repository.AbstractProfileAction.install(AbstractProfileAction.java:53)
at org.jboss.system.server.profileservice.repository.AbstractProfileService.install(AbstractProfileService.java:403)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:378)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:2029)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:1050)
at org.jboss.dependency.plugins.AbstractController.executeOrIncrementStateDirectly(AbstractController.java:1289)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1213)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1107)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:873)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:620)
at org.jboss.system.server.profileservice.repository.AbstractProfileService.registerProfile(AbstractProfileService.java:308)
at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:259)
at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:100)
at org.jboss.bootstrap.impl.base.server.AbstractServer.startBootstraps(AbstractServer.java:860)
at org.jboss.bootstrap.impl.base.server.AbstractServer$StartServerTask.run(AbstractServer.java:441)
at java.lang.Thread.run(Thread.java:619)
*Caused by: java.lang.NoClassDefFoundError: org/jboss/wsf/spi/http/HttpServer*
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClassCond(ClassLoader.java:632)
at java.lang.ClassLoader.defineClass(ClassLoader.java:616)
at org.jboss.classloader.spi.base.BaseClassLoader.access$200(BaseClassLoader.java:70)
at org.jboss.classloader.spi.base.BaseClassLoader$2.run(BaseClassLoader.java:668)
at org.jboss.classloader.spi.base.BaseClassLoader$2.run(BaseClassLoader.java:627)
at java.security.AccessController.doPrivileged(Native Method)
at org.jboss.classloader.spi.base.BaseClassLoader.loadClassLocally(BaseClassLoader.java:626)
at org.jboss.classloader.spi.base.BaseClassLoader.loadClassLocally(BaseClassLoader.java:603)
at org.jboss.classloader.spi.base.BaseDelegateLoader.loadClass(BaseDelegateLoader.java:134)
at org.jboss.classloader.spi.filter.FilteredDelegateLoader.loadClass(FilteredDelegateLoader.java:131)
at org.jboss.classloader.spi.base.ClassLoadingTask$ThreadTask.run(ClassLoadingTask.java:455)
at org.jboss.classloader.spi.base.ClassLoaderManager.nextTask(ClassLoaderManager.java:267)
at org.jboss.classloader.spi.base.ClassLoaderManager.process(ClassLoaderManager.java:166)
at org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:270)
at org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:1129)
at org.jboss.classloader.spi.base.BaseClassLoader.loadClassFromDomain(BaseClassLoader.java:901)
at org.jboss.classloader.spi.base.BaseClassLoader.doLoadClass(BaseClassLoader.java:523)
at org.jboss.classloader.spi.base.BaseClassLoader.loadClass(BaseClassLoader.java:468)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataFactoryVisitor.addComponent(BeanMetaDataFactoryVisitor.java:54)
at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataFactoryVisitor.addComponent(BeanMetaDataFactoryVisitor.java:35)
at org.jboss.deployers.spi.deployer.helpers.AbstractDeploymentVisitor.deploy(AbstractDeploymentVisitor.java:73)
... 36 more
*Caused by: java.lang.ClassNotFoundException: org.jboss.wsf.spi.http.HttpServer*
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 java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:247)
at org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:297)
at org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:1129)
at org.jboss.classloader.spi.base.BaseClassLoader.loadClassFromDomain(BaseClassLoader.java:901)
at org.jboss.classloader.spi.base.BaseClassLoader.doLoadClass(BaseClassLoader.java:523)
at org.jboss.classloader.spi.base.BaseClassLoader.loadClass(BaseClassLoader.java:468)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
... 59 more
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/588421#588421]
Start a new discussion in JBoss Web Services at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
15 years, 1 month
[JBoss Tools] - JBoss Tools 3.2 is Finally here!
by Max Rydahl Andersen
Max Rydahl Andersen [http://community.jboss.org/people/max.andersen%40jboss.com] modified the blog post:
"JBoss Tools 3.2 is Finally here!"
To view the blog post, visit: http://community.jboss.org/community/tools/blog/2011/02/21/jboss-tools-32...
--------------------------------------------------------------
http://in.relation.to/service/File/10824 http://in.relation.to/service/File/10824
h4. 3.2.0
[ http://www.jboss.org/tools/download Download] [ http://download.jboss.org/jbosstools/updates/stable/helios/ Update Site] [ http://marketplace.eclipse.org/content/jboss-tools-1 Market Place] [ http://docs.jboss.org/tools/whatsnew What's New] [ http://docs.jboss.org/tools/3.2.0.Beta1/ Documentation] [ 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]
I'm very happy to be able to announce that we pushed out JBoss Tools 3.2 to the servers shortly before the weekend.
h2. Installation/Upgrade
Existing Eclipse Workspaces used with JBoss Tools 3.1 will work with JBoss Tools 3.2, but do take a backup of your workspace to be on the safe side.
As per tradition the updatesite is now moved over to a stable location
http://download.jboss.org/jbosstools/updates/stable/helios/
To "upgrade" from JBoss Tools 3.1 to JBoss Tools 3.2 you need to install Eclipse 3.6 and add the updatesite. Updating Eclipse major versions via updatesite does sometime work, but we do recommend a clean install to make it all a bit cleaner.
If you don't like messing with updatesites you can also install JBoss Tools 3.2 via Eclipse Marketplace - simply use *Help > Eclipse Marketplace* directly from Eclipse and find JBoss Tools 3.2 (Helios) via the Search facility.
h2. New Features
The following paragraphs outlines the highlights from the JBoss Tools 3.2 release, but I recommend reading the complete
http://docs.jboss.org/tools/whatsnew What's New lists if you want to see all the noticable changes and improvements that have been made since JBoss Tools 3.1.
h3. JSF 2
The Visual Page Editor and our XHTML structured editors now supports JSF 2; especially the notion of composite components which is a new feature of JSF 2 allowing users to much easier define reusable components for their application or framework.
JSF 2 also provides a new standardized approach to load up resources via the classpath and web archives; these are all supported by JBoss Tools making the visual page editor render even more realistically the layout of the page but also code completion, navigation and even quickfixes now benefit from this additional information to make it easy to fix issues and navigate to the linked resources instantly.
h3. Context & Dependency Injection (CDI)
The CDI tooling have received a lot of updates, especially in context of providing validations of all the error handling cases covered by the CDI TCK test suite and a few other hints provided by the Weld CDI Team.
There is also a good set of wizards, code navigations and quickfixes added in this release and I recommend you go read Alexey Kazakov's blog about this feature set.
h3. Visual Page Editor
Besides supporting JSF 2 better in this release various other improvements were done to the Visual Page Editor.
* Templates for jBPM, Spring and Richfaces 4 were added/improved
* DocBook support were made more complete and is now a separately named editor
* A generic "Split-Editor" functionallity were added (can be used with any Eclipse editor)
* The UI were cleaned up to fit better into the Eclipse IDE
h3. Servers, Packaging & Remote Deployment
The biggest new feature for the Application Server integration in JBoss Tools 3.2 is the introduction of Remote Deployment.
Remote Deployment works (more or less) just like the Local deployment except instead of using local file copies we now relay the file transfer to the Eclipse Remote System Explorer API; this then allows you to deploy to systems via SSH, FTP, etc.
This Remote Deployment not only works for the JBoss Application Server adapters but is also provided via the "Deploy Only" server meaning you can use it to deploy any project to any application server or system which supports hotdeployment by scanning their local file system for changes.
We've also improved support for "non-WTP" style projects by enabling you to right click Folders and mark them as Deployable. These deployable folders can then be deployed to any of the Server adapters provided by JBoss Tools, including the Deploy Only server.
The JBoss Server Adapter now also supports the new JBoss 6 and updated versions of JBoss Enterprise Application Platform based servers.
h2. Automatic Runtime Detection
One of the big hassles of any IDE configuration is to identify and configure your various runtimes, such as JBoss Application Server, Seam, jbpm, ESB, Drools, JDK's etc.
We've contributed the installer logic from our JBoss Developer Studio 4 product into the actual JBoss Tools plugins and enhanced it so it can be configured to scan one or more directories at startup for new runtimes; if it detects a new runtime it will ask if it should add it and JBoss Tools will do a default installation of the runtime - freeing you from having to go through the various runtime user interfaces.
This feature is available under Eclipse Preferences in *JBoss Tools > JBoss Tools Runtime Detection*
In the future we plan to add more runtime detections, not just JBoss based ones.
h3. Google GWT (Experimental)
Google's Eclipse plugin for GWT does not provide seamless integration with Eclipse WTP based projects; thus we made an Eclipse Facet that allows you to easily enable Google GWT on your WTP project and not having to use custom wizards and special projects to get started with the Eclipse GWT tooling.
Please note that since Google are not providing stable named features from their updatesite to have Eclipse updatesites work together, it is necessary to install Google GWT plugin manually before trying to use our Google GWT facet.
See http://community.jboss.org/docs/DOC-15593 Andre's article on how to use this Google GWT feature.
h3. DeltaCloud (Experimental)
The tooling for Delta Cloud provides a perspective and a few views to easily interact with systems such as SteamCannon that provide a DeltaCloud API.
This gives you the ability to browse, start & stop virtual machines hosted by cloud service providers such as EC2 and Rackspace.
You can try it out by using https://try.steamcannon.org/deltacloud/api https://try.steamcannon.org/deltacloud/api as the URL for a Delta Cloud connection.
Note, DeltaCloud tooling is marked experimental while the DeltaCloud API and implementations are stabilizing. If needed we will provide an update to support the latest/stable DeltaCoud servers.
h3. Maven
We've continued to expand the support for Maven projects by extending m2eclipse tooling to automatically configure projects based on the dependencies of your project.
Thus now if you import or configure a Maven based project and it uses a standard dependency for either Seam, CDI, JSF, Hibernate or GateIn/Portal the features for these frameworks will now be enabled and configured automagically.
You can control this per framework under Eclipse Preferences via *JBoss Tools > JBoss Maven Integration*
To see an example of this applied, look at http://community.jboss.org/community/tools/blog/2011/01/31/overview-of-co... Snjzana's blog where she illustrate how via Project Examples you can easily get started with the CDI and JSF tooling. This blog works because of the Maven Integration provided here.
h3. Modeshape
Modeshape provides a JCR based view on many different datasources such as file systems, databases, other JCR repositories and even your own services and applications.
The Modeshape tooling provided in JBoss Tools 3.2 gives you a way to easily connect to a Modeshape server, browse it content and checkin/checkout content from and to the Eclipse workspace.
h3. Teiid Designer
The Teiid Designer that is used to visualize model your datamodel and transformations as supported by the Teiid runtime is now included into JBoss Tools.
The Teiid Designer plugins also provides a testbed for testing and exploring your Teiid configured dataservices.
You can read more about Teiid Designer on its http://www.jboss.org/teiiddesigner community page.
h3. BPEL
The BPEL tooling is based on the Eclipse BPEL project but provides a set of bugfixes and features that have not yet made it back to the Eclipse BPEL project, especially in context of supporting deployment to other systems than Tomcat based systems such as Apache ODE. We support the Riftsaw JBoss based BPEL system.
If you want to read about the BPEL feature set and its future (its fixes are being contributed back to Eclipse.org) you can read http://community.jboss.org/community/tools/blog/2011/01/24/bpel-technical... Bob Brodt's blog about this.
h3. WebServices
We've added some much simpler wizards for creating JAX-RS or even JAX-WS webservices to the tooling; but even more interesting is the new Webservice Tester UI which gives you a view to easily query a SOAP or REST based webservice and introspect its result.
Brian Fitzpatrick wrote a http://community.jboss.org/community/tools/blog/2011/02/08/tools-tools-tools couple of http://community.jboss.org/docs/DOC-15778 blogs http://community.jboss.org/docs/DOC-15749 about it, giving you an overview of the new improvements for the WebServices support.
h3. Usage Reporting
When you install a JBoss Tools plugin, on the first startup of Eclipse a dialog will ask if you wish to send anonymous usage data to us. We use that information to see which OS's, system configurations and plugins you are running plus we get to see how fast (or slow) new versions of spreads over the world.
h3. ...and much more...
The above highlights are just a subset of the over 1600 issues fixed and implemented over the last many months thus the best way to get to know it all is to try it out :)
Let us know how it goes and above all,
Have fun!
--------------------------------------------------------------
Comment by going to Community
[http://community.jboss.org/community/tools/blog/2011/02/21/jboss-tools-32...]
15 years, 1 month