It has been a passion of mine, but never had the time to dedicate effort.
This project should make things easier.
Hope that there will be a SDK to create own characters.
Take a look at it and consider to perk for it.
Friday, December 27, 2013
Wednesday, December 11, 2013
JBoss 7.1.1 + GeoServer 2.2.5: logging
To enable correct logging of GeoServer in a JBoss 7.1.1 installation we'll need to modify the previously defined jboss-deployment-structure.xml
Than you need to set the following jvm-option in the host.xml file: GEOSERVER_LOG_LOCATION
<jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.1">
<deployment>
<exclusions>
<module name="org.apache.log4j" />
<module name="org.slf4j" />
</exclusions>
<dependencies>
<system>
<paths>
<path name="com/sun/imageio/spi"/>
<path name="com/sun/imageio/plugins/common"/>
</paths>
</system>
<module name="com.oracle" />
<module name="org.jboss.ironjacamar.jdbcadapters" />
</dependencies>
</deployment>
</jboss-deployment-structure>
Than you need to set the following jvm-option in the host.xml file: GEOSERVER_LOG_LOCATION
<server name="geo1" group="geo-server-group" auto-start="true">
<jvm name="default">
<heap size="128m" max-size="512m"/>
<jvm-options>
<option value="-DGEOSERVER_DATA_DIR=/home/jbossas/geoserver_data,-DGEOSERVER_LOG_LOCATION=/var/log/jboss-as/geoserver.log"/>
</jvm-options>
</jvm>
</server>
In the example you also see that is possible to define a data dir in the same way.Friday, November 29, 2013
PHP library for calling WSO2 API manager publisher
My need is to create an application that manages the creation of API from a single central point (a PHP site).
The WSO2 API manager has some interesting REST API that can be used to create programmatically an API.
To manage these API better I've developed (still in development) a library that calls the API manager, manage errors and wrap the whole up.
If you need it here is the link to github.
The WSO2 API manager has some interesting REST API that can be used to create programmatically an API.
To manage these API better I've developed (still in development) a library that calls the API manager, manage errors and wrap the whole up.
If you need it here is the link to github.
Tuesday, March 26, 2013
WSO2 Tutorial - BPS
In this tutorial of the WSO2 path I'm working with the BPS version 3.0.0 and WSO2 Developer Studio version 3.0.0.
The objective of this tutorial is to show how to implement a simple process and deploy it in the BPS.
I'll use here a standard default installation of the server (no external DB for process management and so on)
The objective of this tutorial is to show how to implement a simple process and deploy it in the BPS.
I'll use here a standard default installation of the server (no external DB for process management and so on)
Saturday, March 23, 2013
TEIID 8.1 tutorial - Part 15 - Support Update
In this new tutorial of the TEIID series I'll show how to update the original table from the VDB view.
Usually when operating with TEIID designer the "orange" view model proposes just to read/select from the source table.
To be able to Update/Insert/Delete from the original table we must enable the "Support Update" checkbox as shown in the figure below.

In the video I'll show the whole procedure.
Usually when operating with TEIID designer the "orange" view model proposes just to read/select from the source table.
To be able to Update/Insert/Delete from the original table we must enable the "Support Update" checkbox as shown in the figure below.

In the video I'll show the whole procedure.
Friday, March 22, 2013
WSO2 Tutorials
I'll start a new tutorial line dedicated to the WSO2 product suite.
Here is what I'm preparing:
1) Business Process Server - example process and deploy
2) API Manager - publishing of an API and usage from the store
3) API Manager - TEIID SOAP service publishing
More will come.
Here is what I'm preparing:
1) Business Process Server - example process and deploy
2) API Manager - publishing of an API and usage from the store
3) API Manager - TEIID SOAP service publishing
More will come.
Monday, March 18, 2013
GeoServer 2.2.5 + JBoss 7.1.1 and Oracle
As I posted some time ago, I'm using GeoServer version 2.2.5 on a JBoss 7.1.1 installation; now I'm working with an Oracle Database so I've added the Oracle extension. And added it in the "$WAR/WEB-INF/lib/" the jar that is downloaded as a separate package (mind to download the same version for the GeoServer you are using).
I had this problem accessing oracle tables:
The problem is due to a classloading mechanism of the AS.
I had this problem accessing oracle tables:
09:23:34,911 ERROR [org.geoserver.ows] (http--10.20.1.50-8280-17) : java.lang.NoClassDefFoundError: oracle/jdbc/OracleConnection
at org.geotools.data.oracle.OracleDialect.unwrapConnection(OracleDialect.java:544) [gt-jdbc-oracle-8.7.jar:]
at org.geotools.data.oracle.OracleDialect.setGeometryValue(OracleDialect.java:517) [gt-jdbc-oracle-8.7.jar:]
at org.geotools.jdbc.JDBCDataStore.setPreparedFilterValues(JDBCDataStore.java:3168) [gt-jdbc-8.7.jar:]
at org.geotools.jdbc.JDBCDataStore.setPreparedFilterValues(JDBCDataStore.java:3147) [gt-jdbc-8.7.jar:]
at org.geotools.jdbc.JDBCDataStore.selectAggregateSQLPS(JDBCDataStore.java:3372) [gt-jdbc-8.7.jar:]
at org.geotools.jdbc.JDBCDataStore.getAggregateValue(JDBCDataStore.java:1292) [gt-jdbc-8.7.jar:]
at org.geotools.jdbc.JDBCDataStore.getCount(JDBCDataStore.java:1250) [gt-jdbc-8.7.jar:]
at org.geotools.jdbc.JDBCFeatureSource.getCountInternal(JDBCFeatureSource.java:432) [gt-jdbc-8.7.jar:]
at org.geotools.data.store.ContentFeatureSource.getCount(ContentFeatureSource.java:451) [gt-data-8.7.jar:]
at org.geotools.jdbc.JDBCFeatureStore.getCountInternal(JDBCFeatureStore.java:183) [gt-jdbc-8.7.jar:]
at org.geotools.data.store.ContentFeatureSource.getCount(ContentFeatureSource.java:451) [gt-data-8.7.jar:]
at org.geotools.data.store.ContentFeatureCollection.size(ContentFeatureCollection.java:356) [gt-data-8.7.jar:]
at org.geoserver.wms.GetFeatureInfo.execute(GetFeatureInfo.java:297) [wms-2.2.5.jar:2.2.5]
at org.geoserver.wms.GetFeatureInfo.execute(GetFeatureInfo.java:168) [wms-2.2.5.jar:2.2.5]
at org.geoserver.wms.GetFeatureInfo.run(GetFeatureInfo.java:117) [wms-2.2.5.jar:2.2.5]
at org.geoserver.wms.DefaultWebMapService.getFeatureInfo(DefaultWebMapService.java:374) [wms-2.2.5.jar:2.2.5]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.6.0_25]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [rt.jar:1.6.0_25]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [rt.jar:1.6.0_25]
at java.lang.reflect.Method.invoke(Method.java:597) [rt.jar:1.6.0_25]
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:318) [spring-aop-3.1.1.RELEASE.jar:3.1.1.RELEASE]
The problem is due to a classloading mechanism of the AS.
Friday, March 08, 2013
TEIID 8.1 tutorial - Part 10 - TEIID SOAP service + WSO2 + SoapUI
In this tutorial I'll be publishing the book SOAP web service using the API manager from WSO2.
To demonstrate that it works I'll be using as usual SoapUI
The API Manager is composed of two components the Publisher and the Store.
Obviously I need to start from the publisher and create the API: you ger the WSDL endpoint from the JBoss consolle in the webservices TAB.
The API start as CREATED so I need to set into PUBLISHED state.
The API is ready to be used, so is turn of the Store where is quite easy to subscribe to the API.
The main idea is that I'm a developer that uses some of the API published on the Store and I can have different applications that make use of the API and can register to use them with different "Tier" levels that means how much requests I can issue in a given time.
To demonstrate that it works I'll be using as usual SoapUI
The API Manager is composed of two components the Publisher and the Store.
Obviously I need to start from the publisher and create the API: you ger the WSDL endpoint from the JBoss consolle in the webservices TAB.
The API start as CREATED so I need to set into PUBLISHED state.
The API is ready to be used, so is turn of the Store where is quite easy to subscribe to the API.
The main idea is that I'm a developer that uses some of the API published on the Store and I can have different applications that make use of the API and can register to use them with different "Tier" levels that means how much requests I can issue in a given time.
Etichette:
open source,
SoapUI,
software,
teiid,
WSO2 API Manager
Subscribe to:
Posts (Atom)