[Beginner's Corner] - Unable to use remoting services in jboss 5.1.0
by dhaval joshi
dhaval joshi [http://community.jboss.org/people/dhaval0129] created the discussion
"Unable to use remoting services in jboss 5.1.0"
To view the discussion, visit: http://community.jboss.org/message/559378#559378
--------------------------------------------------------------
Hi
My project was eariler deployed on Jboss 4.2.2 and now we are migrating towards jboss 5.1.0, We used Jboss remoting in Jboss 4.2.2 and so we edited Jboss-Service.xml in <JBOSS_HOME>\Server\Default\Conf, In Jboss-Service.xml of Jboss 4.2.2 Remoting Services & Transaction which our application is using. we also edited Remoting Services section in Jboss-service.xml.
but now after we partially migrated to jboss 5.1.0, i could not find Remoting Services section in Jboss-service.xml of 5.1.0. Also lot of other sections like Transaction,Invokers to the JMX-node,Remoting Services and Deployment scanning are missing in Jboss-service.xml of Jboss 5.1.0.
If you compare jboss-service.xml of Jboss 4.2.2 & Jboss 5.1.0 with some code comparator then you can verify this changes which i am seeting.
Can any one let me know how can I Use Remoting & Transaction Services in Jboss 5.1.0 ? and Incase I have to edit this Remoting services section then where should i make changes ?
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/559378#559378]
Start a new discussion in Beginner's Corner at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years, 9 months
[JBoss Remoting Development] - Unable to find Remoting services in Jboss 5.1.0
by dhaval joshi
dhaval joshi [http://community.jboss.org/people/dhaval0129] created the document:
"Unable to find Remoting services in Jboss 5.1.0"
To view the document, visit: http://community.jboss.org/docs/DOC-15756
--------------------------------------------------------------
Hi
My project was eariler deployed on Jboss 4.2.2 and now we are migrating towards jboss 5.1.0, We used Jboss remoting in Jboss 4.2.2 and so we edited Jboss-Service.xml in <JBOSS_HOME>\Server\Default\Conf, In Jboss-Service.xml of Jboss 4.2.2 Remoting Services & Transaction which our application is using. we also edited Remoting Services section in Jboss-service.xml.
but now after we partially migrated to jboss 5.1.0, i could not find Remoting Services section in Jboss-service.xml of 5.1.0. Also lot of other sections like Transaction,Invokers to the JMX-node,Remoting Services and Deployment scanning are missing in Jboss-service.xml of Jboss 5.1.0.
If you compare jboss-service.xml of Jboss 4.2.2 & Jboss 5.1.0 with some code comparator then you can verify this changes which i am seeting.
Can any one let me know how can I Use Remoting & Transaction Services in Jboss 5.1.0 ? and Incase I have to edit this Remoting services section then where should i make changes ?
--------------------------------------------------------------
Comment by going to Community
[http://community.jboss.org/docs/DOC-15756]
Create a new document in JBoss Remoting Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=102&co...]
13 years, 9 months
[JBoss Tools Development] - How to Build JBoss Tools with Maven3
by Nick Boldt
Nick Boldt [http://community.jboss.org/people/nickboldt] modified the document:
"How to Build JBoss Tools with Maven3"
To view the document, visit: http://community.jboss.org/docs/DOC-15513
--------------------------------------------------------------
Current trunk version of JBoss Tools can be built with maven 3 and make it faster and easier for everyone.
+*If you're trying to compile JBoss Tools within Eclipse for plugin development, https://community.jboss.org/wiki/JBossToolsTargetPlatformProvisioningorho... read this to get all the dependencies installed.*+
h2. Prerequisites
1. Java 1.6 SDK
2. Maven 3.beta1
3. About 6 GB of free disk space if you want to run all integration tests for (JBoss AS, Seam and Web Services Tools)
4. subversion client 1.6.X (should work with lower version as well)
h2. Environment Setup
h3. Maven and Java
Make sure your maven 3 is available by default and Java 1.6 is used.
mvn -version
should print out something like
Apache Maven 3.0-beta-2 (r983206; 2010-08-07 07:00:51-0400)
Java version: 1.6.0_18
Java home: /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux" version: "2.6.32.14-127.fc12.i686" arch: "i386" Family: "unix"
h3. Sources
Checkout sources from anonymous SVN like
svn co http://anonsvn.jboss.org/repos/jbosstools/trunk jbosstools-trunk
This will take some time dependent on your bandwidth
h2. Build Strategies
All commands below is assuming that commands are executed in jbosstools-src folder after sources checked out as it suggested above.
There are several strategies to chose from building everything to build particular component or part of it like all plug-ins, all tests, all features, particular plugin/feature.
Target platform and parent pom should be built first like
mvn clean install -f build/parent/pom.xml
If you want to just compile the modules, tests can be skipped by adding system property *-Dmaven.test.skip=true* and you should be able to faster verify compile issues.
h3. Build/Test Everything
Current version cannot be build without local changes because of problem with with drools component, so to go with this scenario you need to remove drools references from pom.xml and site/site.xml. After that to build/test everything use:
mvn clean install
h3. Build/Test Particular Component with Dependencies
For convenience there are aggregator projects defined for each component. It provides a simple way to build/test components with dependencies.
mvn clean install -f build/component/${component.name}.xml
where ${component.name} is component you want to build/test. Currently build/component folder contains aggregator projects for:
1. tests
2. jmx
3. archives
4. as
5. common
6. seam
7. vpe
8. archives
9. as
More are coming soon. To know the order in which to build prerequisite components for your component, see http://anonsvn.jboss.org/repos/jbosstools/trunk/pom.xml http://anonsvn.jboss.org/repos/jbosstools/trunk/pom.xml
h3. Build/Test Single Component
Be aware that to get this work all dependencies for this component must be installed in maven repo. It can be done by build everything first or by build component and its dependencies using aggregated project as it explained above. You can skip tests for this build and then enable them back when you run single component build.
To build single component use pom.xml in component's folder like it is shown below.
mvn clean install -f ${component.name}/pom.xml
where ${component.name} is component's root folder name. For instance to build jmx component use command below
mvn clean install -f jmx/pom.xml
or, if you prefer, you can build a series of components in order (with tests skipped using *-Dmaven.test.skip=true*):
for d in tests jmx archives as; do \
pushd $d; mvn clean install -Dmaven.test.skip=true; popd; \
done
----
h3. Adding a Plugin To An Existing Component
Now that you can build your component, you can easily add a new plugin to that component. Here's how.
0. Make sure your new plugin compiles in your workspace. Ensure your MANIFEST.MF contains all references/includes/requirements you need. Be sure to set the correct Bundle-RequireExecutionEnvironment (eg., JDK5 or JDK6).
1. When you are satisfied, you can commit your new plugin project to SVN.
cd ~/trunk/as/plugins; \
svn add org.jboss.ide.eclipse.as.rse.core; \
svn ci -m "JBIDE-123456 Initial commit of new as.rse.core plugin" org.jboss.ide.eclipse.as.rse.core
2. Next, add a pom.xml file to the root of your new project.
You can use m2eclipse to help w/ this if you have it installed; otherwise copy from another existing plugin project and edit appropriately. The version of the pom should match the version in the manifest.mf. Note that 3.2.0.qualifier (in MANIFEST.MF) is equivalent to 3.2.0-SNAPSHOT in the pom.xml.
3. Build your plugin:
cd ~/trunk/as/plugins/org.jboss.ide.eclipse.as.rse.core; \
mvn3 clean install
4. If your component's new plugin builds successfully, you can commit the pom.xml file, and add a reference to the new plugin (module) in the container pom:
vi ~/trunk/as/plugins/pom.xml
5. To ensure that your plugin is available on the update site, be sure that it is contained in at least one feature's feature.xml.
vi ~/trunk/as/features/org.jboss.ide.eclipse.as.feature/feature.xml
6. Finally, ensure that the feature appears in all three update sites:
vi ~/trunk/as/site/site.xml # (the AS update site)
vi ~/trunk/site/site.xml # (the JBoss Tools update site) and
vi ~/trunk/build/aggregate/site/site.xml # (the JBoss Tools aggregate update site, incl. pi4soa, Teiid, ...)
--------------------------------------------------------------
Comment by going to Community
[http://community.jboss.org/docs/DOC-15513]
Create a new document in JBoss Tools Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=102&co...]
13 years, 9 months
[JBoss Tools Development] - JBoss Tools Target Platform Provisioning (or, how to resolve missing dependencies when compiling JBoss Tools)
by Nick Boldt
Nick Boldt [http://community.jboss.org/people/nickboldt] created the document:
"JBoss Tools Target Platform Provisioning (or, how to resolve missing dependencies when compiling JBoss Tools)"
To view the document, visit: http://community.jboss.org/docs/DOC-15755
--------------------------------------------------------------
*+This document is a work in progress and subject to change.+*
In order to build JBoss Tools in your workspace (or on your local machine, if not in Eclipse), you need to have its dependencies available. There are a number of ways to accomplish this, depending on your needs and how much manual effort you'd like to expend.
*1. Build Parent Pom + Target Platform With Tycho + Maven 3*
Build the parent pom [1] + target platform [2], then build against that with maven3 (commandline) or m2eclipse (and don't use PDE anymore when building in Eclipse)
cd /tmp; \
svn co http://anonsvn.jboss.org/repos/jbosstools/trunk/build/ http://anonsvn.jboss.org/repos/jbosstools/trunk/build; \
cd /tmp/build/parent; \
mvn3 clean install
Then...
cd /tmp; \
svn co http://anonsvn.jboss.org/repos/jbosstools/trunk/tests; http://anonsvn.jboss.org/repos/jbosstools/trunk/tests; \
cd /tmp/tests; \
mvn3 clean install
(etc.)
This is how the Hudson builds run - compile the parent (which compiles the target platform), then build whatever component(s) you then want.
If you have the entire JBoss Tools tree on disk, you can also do multi-component builds even simpler like this:
cd /tmp; \
svn co http://anonsvn.jboss.org/repos/jbosstools/trunk/ http://anonsvn.jboss.org/repos/jbosstools/trunk; \
cd /tmp/trunk/build/component; \
mvn3 clean install -f seam.xml
*2. Load Target Platform in Eclipse*
Attempt to get the target platform file [2] to load in Eclipse, then click 'set as target platform' in the top right corner of the editor when it's open in the Target Platform editor. This should resolve everything in the target, and install it into your Eclipse. When it works. The editor is kinda flaky.
When it completes (and it may take a significant amount of time during which your Eclipse may be unstable / unusable), you should have everything you need to develop JBoss Tools.
*3. Manual Install from Update Sites (p2 Repos)*
Read through either [1] or [2] and install - by hand - what you need from the various update sites against which we install. The sites are listed in two places [1], [2]. The target platform file lists the features/plugins you need to include when installing; the parent pom only lists the update sites. YMMV.
*4. Manually Download and Unpack Runnable Zips*
Pull down the SDKs/runtime zips [3] and dump them into your eclipse's dropins/ folder. This is the way the old "uberbuilder" works, and is deprecated, but should still work.
[1] http://anonsvn.jboss.org/repos/jbosstools/trunk/build/parent/pom.xml http://anonsvn.jboss.org/repos/jbosstools/trunk/build/parent/pom.xml
[2] http://anonsvn.jboss.org/repos/jbosstools/trunk/build/target-platform/e36... http://anonsvn.jboss.org/repos/jbosstools/trunk/build/target-platform/e36...
[3] http://download.jboss.org/jbosstools/requirements/helios/README.txt http://download.jboss.org/jbosstools/requirements/helios/README.txt, http://download.jboss.org/jbosstools/requirements/helios/ http://download.jboss.org/jbosstools/requirements/helios/ (GWT is missing, but the collection should otherwise be complete)
--------------------------------------------------------------
Comment by going to Community
[http://community.jboss.org/docs/DOC-15755]
Create a new document in JBoss Tools Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=102&co...]
13 years, 9 months
Re: [jboss-user] [JBoss Microcontainer Development POJO Server] - Implementing a non-flat deployment for Weld Integration
by Ales Justin
Ales Justin [http://community.jboss.org/people/alesj] replied to the discussion
"Implementing a non-flat deployment for Weld Integration"
To view the discussion, visit: http://community.jboss.org/message/559359#559359
--------------------------------------------------------------
> Roughly speaking, this is how we would fill in the gaps of the TODO mark you added in your getLibraries method:
OK, refactored things a bit, I now have this:
// create an ArchiveInfo with the ClassLoader
ArchiveInfo archiveInfo = new ArchiveInfo(cl);
// finally create the Archive
Archive archive = ArchiveFactory.createArchive(archiveInfo, new ArrayList<EjbDescriptor<?>>());
// ... and the corresponding BDA
ServiceRegistry serviceRegistry = new SimpleServiceRegistry();
// TODO: fill in serviceRegistry? With which services?
libs.add(archive.createBeanDeploymentArchive(serviceRegistry));
// the env
WeldDiscoveryEnvironment environment = archiveInfo.getEnvironment();
// fill in the Weld classes
// the WBDiscoveryVisitor from ArchiveDiscoveryDeployer...
ResourceVisitor visitor = environment.visitor();
Module module = entry.getKey();
for (VirtualFile child : files)
{
URL beansXmlURL = child.getChild(provider.getResourceName()).toURL();
environment.addWeldXmlURL(beansXmlURL);
module.visit(visitor, ClassFilter.INSTANCE, null, child.toURL());
}
It all compiles. :-)
> The other piece of code that we are missing is the part that invokes this, right? At some point we need to fill in the DefaultDomain Classpath (take a look at ClasspathFactory for more details) with the lib BDAs created by your getLibraries method. As we agreed before, this should be done ideally at the first weld deployment. So, I would simply add a piece of code to ClasspathFactory that calls getLibraries, unless you prefer this call to be performed somewhere else.
OK, I still need to think about this one a bit.
> I think that the best way to check everything is working ok is adding a Weld jar to jboss lib prior to start up and make sure that a BDA is being created for it. Other than that, I don't have any use cases :-).
Yup, I'll create a simple test for this -- probably (until we do have a *real* CDI lib present) I'll have to create a new server config for it.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/559359#559359]
Start a new discussion in JBoss Microcontainer Development POJO Server at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years, 9 months