VPIdata Brasil

Download: http://servicemix.apache.org/downloads/servicemix-4.4.0.html

Principais mudanças:

1. Atualização do Apache Karaf 2.2.4 -
1. Atualização do Pax Web 1.0.7 (componente OSGI para facilitar o deploy de web app).
1. Essa atualização resolve o problema de NullPointerException quando chamava um método removeServlet() sem contexto.  (http://team.ops4j.org/browse/PAXWEB-307).
   Pode parecer bobeira mas o log enchia com esse problema :P
2. Wrapper para bibliotecas de 64 bits!
1. Incrível como isso deu trabalho para descobrir em uma migração de SO (https://issues.apache.org/jira/browse/KARAF-907)
2. Atualização dos componentes:
1. Apache ActiveMq 5.5.1
2. Apache Camel 2.8.3
3. Apache CXF 2.4.4
4. Apache ServiceMix NMR 1.5.0
5. Apache ServiceMix JBI Components 2011.02
3. Melhoria do Help para comandos shell:
1. Muitos iniciantes reclamaram bastante principalmente nas chamadas relacionadas a OSGI e agora melhorou (já vinha desde 4.0):
   https://issues.apache.org/jira/browse/SMX4-221
   https://issues.apache.org/jira/browse/SMX4-219
   https://issues.apache.org/jira/browse/SMX4-220

Mais informações segue o changelog.

Segue o RELEASE-NOTES:

Apache ServiceMix 4.4.0

================================

Overview

——–

 

Apache ServiceMix 4.4.0 is a major release of the OSGi based ServiceMix ESB platform. This release contains many

bugfixes and feature enhancements over the 4.3.0 release. ServiceMix 4.4.0 includes the following major dependency upgrades:

 

- Apache ActiveMQ 5.5.1 (http://activemq.apache.org)

- Apache Camel 2.8.3 (http://camel.apache.org)

- Apache CXF 2.4.4 (http://cxf.apache.org)

- Apache Karaf 2.2.4 (http://karaf.apache.org)

- Apache ServiceMix NMR 1.5.0

- Apache ServiceMix JBI Components 2011.02

 

Changelog

———

 

** Sub-task

* [SMX4-220] – Extend the help command to display usefull help for all commands available

* [SMX4-221] – The option –help on commands doesn’t display good enough help

* [SMX4-721] – Add complete distribution for offline deployments

* [SMX4-884] – Rename existing assembly to apache-servicemix-4.x.0-jbi

* [SMX4-885] – Add a basic distribution for new users

* [SMX4-955] – Add minimal distribution to allow building any ServiceMix-based distribution

 

** Bug

* [SMX4-206] – Apache ServiceMix 4 binary assembly zip file is not valid

* [SMX4-246] – Avoid duplication of config files for NMR and Features assembly build

* [SMX4-458] – Command activemq:list, activemq:browse return null

* [SMX4-461] – Test failures in SMX4 Features’ project on AIX

* [SMX4-480] – Files in deploy folder before initial startup are getting deployed before boot features

* [SMX4-518] – Camel NMR component WSSecurityTest fails

* [SMX4-687] – ServiceMix 4.3.0-fuse-02-00 does not start correctly with fresh unzip on Windows

* [SMX4-737] – Components Not Loading Before Routes

* [SMX4-751] – Property replacement is broken in camel-blueprint examples

* [SMX4-768] – bin/client script missing from Linux distribution

* [SMX4-771] – simple example use out-of-date DocumentFactory

* [SMX4-774] – artchetypes for servicemix-cxf-code-first-osgi-bundle and servicemix-cxf-code-first-osgi-bundle doesn’t work

* [SMX4-780] – omit client script in bin folder

* [SMX4-797] – Create OSGi bundle for RJC (Redis Java Client)

* [SMX4-804] – ensure some bundle could be installed with OBR resolver

* [SMX4-821] – wsdl4j bundle shouldn’t import javax.wsdl as itself export it

* [SMX4-853] – Simple quartz.xml example caue intermittent exception

* [SMX4-867] – the endorsed xml-api jar can’t correctly load org.apache.xpath.jaxp.XPathFactoryImpl class

* [SMX4-869] – Missing class reference in the log:display output

* [SMX4-873] – system bundle should export xerces and xalan package as we already endorse those jar

* [SMX4-897] – reuse woodstox feature but not list seperate bundle

* [SMX4-907] – BOM marker in camel-osgi Spring XML file not handled well on CI server

* [SMX4-922] – Not all content of branding.properties is shown

* [SMX4-926] – should add org.ops4j.pax.web.config.file properties to etc/org.ops4j.pax.web.cfg

* [SMX4-932] – system.properties miss karaf.admin.role property

* [SMX4-940] – ServiceMix features depends on non-existent version of geronimo servlet spec.

* [SMX4-948] – Build failure when building with a clean maven repository (unable to determine JBI component)

* [SMX4-962] – servicemix xstream 1.4.1 bundle incorrectly refer xstream 1.4

* [SMX4-967] – remove saaj feature from add-features-to-repo

* [SMX4-968] – distribution kit miss org.apache.karaf.features.obr bundles which cause startup failed

* [SMX4-969] – features itests depends on old karaf management jar

* [SMX4-980] – rename etc/org.ops4j.pax.web.cfg to etc/org.ops4j.pax.web.cfg.empty.stub

* [SMX4-987] – simple/quartz.xml example output doesn’t comply with the README

* [SMX4-993] – The link to the FuseSource commercial documentation is broken

* [SMX4-996] – examples won’t build with clean Maven local repo

 

** Improvement

* [SMX4-219] – The help of the shell commands is wrong or not sufficient and needs improvement

* [SMX4-446] – Update Feature file of SMX4 to use HTTP feature of karaf and same version of jetty as camel feature file

* [SMX4-572] – Cleanup POMs and provide a better build

* [SMX4-597] – Use Camel feature

* [SMX4-654] – Improve features.xml to leverage OBR improvements in Karaf

* [SMX4-659] – Create bundle for jSch 0.1.44

* [SMX4-722] – Update POMs to Maven3

* [SMX4-727] – Consider dropping commons-logging for standard Java.util.logging

* [SMX4-744] – specify camel feature bundle start level less than 60

* [SMX4-772] – add configuration stub file for SSL pax-web suport for ease of users

* [SMX4-775] – Provide assembly in JAR packaging as well

* [SMX4-777] – Upgrade to Jetty 7.3.1.v20110307

* [SMX4-778] – Rework the smx4 build to have better dependency handling

* [SMX4-787] – Upgrade to ActiveMQ 5.5.1

* [SMX4-791] – Make allowCoreThreadTimeOut name consistent across mbeans and properties

* [SMX4-792] – Support run as subject for Camel NMR endpoint

* [SMX4-793] – Support run as subject for CXF NMR endpoint

* [SMX4-798] – Ensure OBR support is available before boot features are installed

* [SMX4-799] – use the latest xerces to replace the jaxp-ri-1.4.4 to resolve cocurrent issue

* [SMX4-801] – update a set of bundle version

* [SMX4-802] – use features.xml from cxf

* [SMX4-805] – Ignore the sun saaj package from the org.osgi.framework.bootdelegation

* [SMX4-808] – Ignore the sun jaxb package from the org.osgi.framework.bootdelegation

* [SMX4-809] – camel-cache ehcache cache repilication using ehcache-jmsreplication

* [SMX4-812] – Upgrade FreeMarker to 2.3.16

* [SMX4-815] – upgrade to cxf 2.4.0

* [SMX4-825] – Support timeout property on Camel NMR endpoints

* [SMX4-836] – Upgrade FreeMarker to 2.3.17

* [SMX4-837] – Upgrade FreeMarker to 2.3.18

* [SMX4-846] – Upgrade to Jetty 7.4.1.v20110513

* [SMX4-852] – Add ‘karaf-framework’ to boot features to avoid uninstalling core Karaf bundles

* [SMX4-854] – add avalon-framework-api bundle

* [SMX4-855] – create avalon-framework-impl bundle

* [SMX4-863] – upgrade to jetty 7.4.2.v20110526

* [SMX4-870] – “>>>> JavaDSL set body:” displayed but not noted in the Camel/OSGi example’s README.txt file

* [SMX4-871] – README.txt file incomplete for “simple” example in regards to the wsn.xml file.

* [SMX4-877] – create wrap bundle for axiom API and Impl 1.2.12

* [SMX4-882] – specify start-level as 50 for default installed jbi component features which ensure jbi component related bundle can get started before customer bundles when restart OSGi container

* [SMX4-883] – Alter packaging options to better reflect common use cases

* [SMX4-899] – xerces and xalan SPI factory package should be added in custom.properties org.osgi.framework.bootdelegation

* [SMX4-900] – add camel-blueprint as default installed feature

* [SMX4-910] – install activemq-web-console feature should work out of the box

* [SMX4-911] – use system properties to define activemq url

* [SMX4-923] – add activemq-spring feature to featuresBoot

* [SMX4-924] – should ship servlet api 2.5 but not servlet api 3.0

* [SMX4-931] – Sample project module elements are missing from top-level POM.

* [SMX4-938] – features.xml should reuse jetty feature from karaf

* [SMX4-939] – Refactor features build to be independent of NMR build

* [SMX4-943] – Camel NMR producer is not registered with its keyName but using the UUID

* [SMX4-956] – Monitor etc/activemq-broker.xml for changes

* [SMX4-957] – Add a name attribute to the features descriptors

* [SMX4-960] – extract servicemix-soap and servicemix-soap2 bundle into servicemix-shared feature

* [SMX4-966] – Connection refused to embedded broker when starting up

* [SMX4-978] – Upgrade to Camel 2.8.3

* [SMX4-979] – add specs feature to featuresBoot list ensure the specs bundle are available in time

* [SMX4-981] – Reorganize examples by technology

* [SMX4-988] – should add delay to camel timer of camel-nmr and camel-nmr-blueprint example so that the nmr endpoint get chance to create

* [SMX4-989] – create demo using Camel and local ActiveMQ broker

* [SMX4-998] – cleanup cxf related examples to remove unnecessary package/resource import and Required-Bundle

* [SMX4-999] – enhance cxf-ws-security-osgi example to leverage cxf JAASLoginInterceptor to authenticate against karaf default jaas configuration

* [SMX4-1002] – Use SLF4J instead of Java standard logging for CXF in SMX

* [SMX4-1008] – let cxf-ws-rm example use http osgi transport

 

** New Feature

* [SMX4-776] – Create OSGi bundle for Perf4j

* [SMX4-786] – Add a struts2-core and struts-xwork bundles for SMX project

* [SMX4-794] – Provide a convenience POM for users

 

** Task

* [SMX4-752] – Switch to use slf4j as logger (instead of commons-logging)

* [SMX4-770] – Update to Karaf 2.2.0

* [SMX4-781] – Upgrade to Camel 2.7

* [SMX4-785] – upgrade to cxf 2.3.3

* [SMX4-795] – Update to CXF 2.4.0

* [SMX4-816] – Create JBoss Netty 3.2.4 bundle

* [SMX4-820] – Create Bundle for cometd java server 2.1.1

* [SMX4-834] – upgrade karaf version to 2.2.1

* [SMX4-851] – Velocity bundle – Add dynamic imports so the #parse macro can load the resource

* [SMX4-856] – Upgrade to Java Mail 1.4.4

* [SMX4-858] – Quartz 2.0.1 bundle

* [SMX4-861] – upgrade to cxf 2.4.1

* [SMX4-876] – Upgrade to Karaf 2.2.2

* [SMX4-880] – Release Apache ServiceMix 4.4.0

* [SMX4-881] – Upgrade to Groovy 1.8.0

* [SMX4-887] – Upgrade to Quartz 1.8.5

* [SMX4-888] – Upgrade to Camel 2.8.0

* [SMX4-896] – upgrade to cxf 2.4.2

* [SMX4-902] – upgrade to cxf 2.4.2

* [SMX4-903] – upgrade to jetty 7.4.5.v20110725

* [SMX4-905] – Create a scala 2.9.1 bundle

* [SMX4-906] – upgrade xmlsec and opensaml bundle version

* [SMX4-908] – Upgrade to Camel 2.8.1

* [SMX4-912] – upgrade to spring-dm 1.2.1

* [SMX4-916] – upgrade to cxf 2.4.4

* [SMX4-942] – upgrade to spring 3.0.6

* [SMX4-952] – upgrade axiom version to 1.2.12

* [SMX4-961] – XStream 1.4.2 bundle

* [SMX4-995] – use same version of jsr311 as cxf 2.4.4

Fomos escolhidos entre as empresas mais inovadoras pela ITS e por isso iremos apresentar o Marvin9 na Futurecom 2011, segue um pequeno descritivo da solução.

 

 

Marvin9 auditor de publicidade web-based:

Marvin9 é uma plataforma de auditoria de propaganda na internet.
Relacionando empresas, produtos e serviços anunciados em grandes
sites, pequenos blogs e em mídias sociais.

Descubra quando, como, quanto e onde você e seus concorrentes estão
aparecendo na internet.

Usando tecnologias criadas pela VPIdata o Marvin9 usa base semântica
para identificar e categorizar informações anunciadas, com isso
consegue relacionar muito além do "texto" e sim "significado".
Marvin9 é um software oferecido via internet, só precisa criar uma
conta e começar a usar.

Vamos descobrir juntos se o ROI de suas propagandas na internet são efetivos ?

VPIdata tem a missão de inovar na área de tecnologia, por meio de
conhecimento especializado e atendimento singular. Com modelo de
negócio diferente oferecemos serviços por meio do nosso Ateliê de
Software focado no desenvolvimento e qualidade de soluções inovadoras
e sobre medida.

Visão e Parceria sempre na trilha da Inovação.

 

Marvin9. Monitoring yours and your competitors web advertising:

Helping customers seek additional revenue by monitoring yours and
competitors online advertising. No matter if this is a big portal,
small blog or social media.

Marvin9 use a semantic engine build using technologies made by VPIdata
searching not only “words” but “meaning”.

We offer Marvin9 using SAAS business model sign up and use.

Let Marvin9 get the real ROI of your web advertising.

VPIdata is a Brazilian startup specialized in semantic, data mining,
web mining, high availability system and web 2.0 platforms.

Virtual Path Identifier of Innovation based on Data.

Cartaz de chamada do evento:

Abranet está oferecendo 50% de desconto para Futurecom 2011.
http://www2.abranet.org.br/futurecom

Fomos selecionados pelo produto Marvin9 (Codejun é nome de registro da VPIdata).

Parabéns para toda equipe VPIdata.
Site da ITS

 

 

We think is problem was fix but when we access the issues page… Broken again!
After a long painful day we discovery via dreamhost support they updated rails version (3.0.3).
To put redmine working again we freeze the rails version and change a configure file.

Fixing

1. $ rake VERSION=2.3.5 rails:freeze:gems
2. $ cd vendor/rails/activesupport/lib/active_support/
3. $ vim vendor.rb
   Edit line 24 ( http://stackoverflow.com/questions/2975532/have-rails-2-3-x-ignore-the-i18n-gem )
gem 'i18n', '>= 0.1.3', '< 0.4.0'

4. $ cd -
5. $ rm -rf tmp/restart.txt
6. $  touch tmp/restart.txt

Dreamhost please buy me a beer :P

First #fail history:
We dealing with the following error:

Processing WelcomeController#index (for 186.207.8.199 at 2010-12-20 11:57:13) [GET]
Parameters: {“action”=>”index”, “controller”=>”welcome”}
Rendering template within layouts/base
Rendering welcome/index

ActionView::TemplateError (wrong number of arguments (2 for 0)) on line #23 of app/views/welcome/index.rhtml:
20:         <% for project in @projects %>
21:           <% @project = project %>
22:             <li>
23:             <%= link_to_project project %> (<%= format_time(project.created_on) %>)
24:             <%= textilizable project.short_description, :project => project %>
25:             </li>
26:         <% end %>

/usr/lib/ruby/gems/1.8/gems/i18n-0.4.2/lib/i18n/backend/base.rb:158:in `warn_syntax_deprecation!’
/usr/lib/ruby/gems/1.8/gems/i18n-0.4.2/lib/i18n/backend/base.rb:158:in `interpolate_without_deprecated_syntax’
/usr/lib/ruby/gems/1.8/gems/i18n-0.4.2/lib/i18n/backend/base.rb:153:in `gsub’
/usr/lib/ruby/gems/1.8/gems/i18n-0.4.2/lib/i18n/backend/base.rb:153:in `interpolate_without_deprecated_syntax’
/usr/lib/ruby/gems/1.8/gems/i18n-0.4.2/lib/i18n/backend/base.rb:46:in `translate’
/usr/lib/ruby/gems/1.8/gems/i18n-0.4.2/lib/i18n.rb:160:in `t’
/usr/lib/ruby/gems/1.8/gems/i18n-0.4.2/lib/i18n/backend/base.rb:60:in `localize’
/usr/lib/ruby/gems/1.8/gems/i18n-0.4.2/lib/i18n.rb:240:in `l’
lib/redmine/i18n.rb:48:in `format_time’
app/views/welcome/index.rhtml:23:in `_run_rhtml_app47views47welcome47index46rhtml’
app/views/welcome/index.rhtml:20:in `each’
app/views/welcome/index.rhtml:20:in `_run_rhtml_app47views47welcome47index46rhtml’
/dh/passenger/lib/phusion_passenger/rack/request_handler.rb:92:in `process_request’
/dh/passenger/lib/phusion_passenger/abstract_request_handler.rb:207:in `main_loop’
/dh/passenger/lib/phusion_passenger/railz/application_spawner.rb:400:in `start_request_handler’
/dh/passenger/lib/phusion_passenger/railz/application_spawner.rb:351:in `handle_spawn_application’
/dh/passenger/lib/phusion_passenger/utils.rb:184:in `safe_fork’
/dh/passenger/lib/phusion_passenger/railz/application_spawner.rb:349:in `handle_spawn_application’
/dh/passenger/lib/phusion_passenger/abstract_server.rb:352:in `__send__’
/dh/passenger/lib/phusion_passenger/abstract_server.rb:352:in `main_loop’
/dh/passenger/lib/phusion_passenger/abstract_server.rb:196:in `start_synchronously’
/dh/passenger/lib/phusion_passenger/abstract_server.rb:163:in `start’
/dh/passenger/lib/phusion_passenger/railz/application_spawner.rb:209:in `start’
/dh/passenger/lib/phusion_passenger/spawn_manager.rb:262:in `spawn_rails_application’
/dh/passenger/lib/phusion_passenger/abstract_server_collection.rb:126:in `lookup_or_add’
/dh/passenger/lib/phusion_passenger/spawn_manager.rb:256:in `spawn_rails_application’
/dh/passenger/lib/phusion_passenger/abstract_server_collection.rb:80:in `synchronize’
/dh/passenger/lib/phusion_passenger/abstract_server_collection.rb:79:in `synchronize’
/dh/passenger/lib/phusion_passenger/spawn_manager.rb:255:in `spawn_rails_application’
/dh/passenger/lib/phusion_passenger/spawn_manager.rb:154:in `spawn_application’
/dh/passenger/lib/phusion_passenger/spawn_manager.rb:287:in `handle_spawn_application’
/dh/passenger/lib/phusion_passenger/abstract_server.rb:352:in `__send__’
/dh/passenger/lib/phusion_passenger/abstract_server.rb:352:in `main_loop’
/dh/passenger/lib/phusion_passenger/abstract_server.rb:196:in `start_synchronously’

We found the bug on this issue:
http://www.redmine.org/issues/5608
In your app path, you need patch lib/redmine/i18n.rb file.
* Fix the line 40 or 48…
We download the correct code from:

http://www.redmine.org/projects/redmine/repository/raw/trunk/lib/redmine/i18n.rb

Quick fix

1. $ cp lib/redmine/i18n.rb lib/redmine/i18n.rb_BKP
2. $ wget lib/redmine/ “http://www.redmine.org/projects/redmine/repository/raw/trunk/lib/redmine/i18n.rb”
3. $ touch tmp/restart.txt (restart the context if you are running inside Phusion)

Fixed!
:P

Moshe Y. Vardi’s Editor’s Letter “Globalization and Offshoring of Software Revisited” and Dave Durkee’s “Why Cloud Computing Will Never Be Free” (both May 2010) failed to address security risks. Vardi’s headline promised an update on the questions raised by increased globalization of outsourced software development. Though I knew his main focus was on the economic impact of global outsourcing, I was still disappointed there was no mention of the security challenges posed by the global supply chain for software. Such challenges have prompted the U.S. Departments of Defense and Homeland Security, the SAFECode consortium, and numerous other organizations to commit significant effort to combating threats posed by software of unknown pedigree and provenance, including individual and state-sponsored “insider threats” (such as implanted malicious logic, backdoors, and exploitable vulnerabilities), particularly when developed offshore. See the Government Accountability Office’s Defense Acquisitions: Knowledge of Software Suppliers Needed to Manage Risks (http://www.gao.gov/new.items/d04678.pdf) and the Report of the Defense Science Board Task Force on Mission Impact of Foreign Influence on DOD Software (http://www.acq.osd.mil/dsb/reports/ADA486949.pdf). Though both focus on software used by DoD, the security issues apply to any organization that relies on outsourced software for critical business or mission functions.

Meanwhile, in an otherwise admirable assessment of the strengths and weaknesses of the cloud computing model of outsourced IT-as-a-service, Durkee likewise failed to mention potential consequences of cloud providers not protecting outsourced computing infrastructure against hackers and malicious code. For example, when discussing transparency, he overlooked the fact that no cloud provider allows its customers to implement intrusion detection or security monitoring extending into the management-services layer behind virtualized cloud instances. Moreover, these customers have learned not to expect their providers to deliver detailed security-incident, vulnerability, or malware reports.

The management-service layer provides a back channel through which the content of each cloud instance is accessible, not only by providers, but by any attacker able to hack into or implant a kernel-level rootkit. Once “in,” the attacker is positioned to exploit the back channel to manipulate or even make full copies of all cloud instances hosted on the compromised platform. Even if customers manage to get their providers to agree to service-level agreements (SLAs) sti pulating a high level of vigilance, reporting, and protection below the cloud-instance layer, the management-services layer remains an inherent weakness that should concern anyone looking to host “in the cloud” the kinds of critical applications Durkee explored.
Karen Mercedes Goertzel, Falls Church, VA

author’s Response:
I strongly agree with Goertzel’s sentiment and appreciate her raising this very important issue. The executive summary of the 2006 Globalization and offshoring report said: “Offshoring magnifies existing risks and creates new and often poorly understood or addressed threats to national security, business property and processes, and individuals’ privacy. While it is unlikely these risks will deter the growth of offshoring, businesses and nations should employ strategies to mitigate them.” The report’s Chapter 6, “Offshoring: Risks And Exposures,” covered the risks at length.
moshe Y. Vardi, editor-in-Chief

From: ACM