Today I finally came around implementing list support for what is my Hello World of learning Android, a Twitter client called Zwitscher.
Main screen looks like this:
You can see support for lists as first class citizens.
Zwitscher is still in a very early stage and of course contains bugs and unimplemented features.
Zwitscher is released as open source - to learn more about it, visit its home page at http://bsd.de/zwitscher/
We have just put a first developer preview of the new RHQ 4 UI online.
This preview is NOT intended FOR PRODUCTION or serious testing, but should rather be seen as an insight on what we are working on.
$ unzip -l bundle.zip
Archive: bundle.zip
Length Date Time Name
-------- ---- ---- ----
1150 07-12-10 16:27 demo.war
948 07-12-10 16:38 deploy.xml
-------- -------
2098 2 files
<?xml version="1.0"?>
<project name="demo" default="main"
xmlns:rhq="antlib:org.rhq.bundle">
<rhq:bundle name="demo" version="1.0"
description="Just some bundle">
<rhq:input-property
name="test.name"
description="Who do we greet?"
required="true"/>
<rhq:deployment-unit name="war">
<rhq:archive name="demo.war">
<rhq:replace>
<rhq:fileset>
<include name="*.jsp"/>
</rhq:fileset>
</rhq:replace>
</rhq:archive>
</rhq:deployment-unit>
</rhq:bundle>
<target name="main"/>
</project>
<rhq:bundle> tag. The bundle has a name of demo and is at version 1.0.<rhq:input-property> tag which defines that the deploy UI should ask for a property test.name which may be used to replace tokens by the users input. This input-property is optional and can show up multiple times.<rhq:deployment-unit> tag, which defines the content to deploy in its embedded <archive> tag - demo.war in our case. And then we have a <rhq:replace> element embedded in this which defines a standard ant fileset that defines files in which token replacements can occur, like .jsp files in our example.modules/helpers/bundleGen/ (actually you can use that to define bundles for RHQ 3)
$ java -jar bundleGen-4.0.0-SNAPSHOT-jar-with-dependencies.jar
Please give the project name[myProject]:
Please give the bundle name: demoBundle
Please specify the bundle version[1.0]:
Please describe your bundle: Just testing
Please give the name (only) of your bundle content file: demo.war
Please give the directory (only) of your bundle content file: /tmp/
Please give a patten of files to replace templates: *.jsp
Jul 14, 2010 9:24:31 AM org.rhq.helpers.bundleGen.BundleGen createFile
INFO: Trying to generate /var/folders/m9/m9pXAK2WHoyq22G2P9J8L++++TI/-Tmp-//bundleGen/deploy.xml
Jul 14, 2010 9:24:31 AM org.rhq.helpers.bundleGen.BundleGen run
INFO: Your bundle is now ready in [/tmp/generatedBundle.zip]
/tmp/generatedBundle.zip in our case.<rhq:input-property> tags so far.basename_lang.xml variants of the input, as you can see here. I am not yet exactly happy with this, as there is no fallback to the default version if a question is not defined.<question> can be repeated to form a List/Set (as it would be needed for the <rhq:input-property> tags).
cd $tmpdir/$driver && /usr/ccs/bin/make install > /dev/null
dladm show-phys shows the interface and ifconfig ni0 plumb is able to use it. After a reboot, networking is working :-)
<plugin name="hadoop"
displayName="hadoopPlugin"
<depends plugin="JMX" useClasses="true"/>
ResourceComponent.start() at the very beginning), you put some additional plugin properties:
public Set<DiscoveredResourceDetails> discoverResources(
ResourceDiscoveryContext context)
throws Exception
{
Configuration pluginConfiguration = context.getDefaultPluginConfiguration();
pluginConfiguration.put(new PropertySimple(
JMXDiscoveryComponent.COMMAND_LINE_CONFIG_PROPERTY,
javaClazz));
pluginConfiguration.put(new PropertySimple(
JMXDiscoveryComponent.CONNECTION_TYPE,
LocalVMTypeDescriptor.class.getName()));
...
jps -l :
$ jps -l
3299 org.apache.hadoop.mapred.TaskTracker
12311
3177 org.apache.hadoop.hdfs.server.namenode.SecondaryNameNode
3037 org.apache.hadoop.hdfs.server.namenode.NameNode
public class HadoopServiceComponent extends JMXServerComponent, ...
public void start(ResourceContext context) throws Exception
{
super.start(context);
...
}
EmsConnection conn = getEmsConnection();
<service name="Root Partition"
class="NagiosMonitorComponent"
discovery="NagiosMonitorDiscovery"
description="root partition service">
<metric property="free_space|plugin_output|.*/ ([\d]+).*"
displayName="Free space" measurementType="dynamic"
units="megabytes" displayType="summary"/>
</service>
<service name="Root Partition"... To obtain those, you can do the following query against mk_livestatus:$ cat service-query
GET services
Columns: display_name
$ nc localhost 6557 < service-query
Root Partition
SSH
...
$
property="free_space|plugin_output|.*/ ([\d]+).*" attribute is used here. It actually consists of three parts separated by a bar (|) symbol:$ cat service-query
GET services
Columns: display_name plugin_output
$ nc localhost 6557 < service-query
Root Partition;DISK OK - free space: / 3611 MB (48% inode=71%)
...
$
.*/ ([\d]+).* to extract the value of 3611.
2010-04-30 14:26:10,601 WARN [org.rhq.enterprise.server.core.plugin.AgentPluginDeploymentScanner] Failed to scan plugin [...../myPlugin-1.0.jar] found on filesystem. Skipping it.
Cause: java.lang.Exception: No version is defined for plugin jar [..../myPlugin-1.0.jar]. A version must be defined either via the MANIFEST.MF [Implementation-Version] attribute or via the plugin descriptor 'version' attribute.<plugin name="myPlugin" version="1.2.3" ... > <plugin>
<artifactId>maven-jar-plugin</artifactId>
<configuration>
<archive>
<manifest>
<addDefaultSpecificationEntries>true</addDefaultSpecificationEntries>
