sepatel/inigma-shared

This project is no longer maintained. Common Libraries used for Web Applications

License

Copyright 2011 Sejal Patel

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

inigma-shared

Common Libraries used for Web Applications. They are designed specially for Java applications built around the Spring Framework that are pure REST services for doing web 2.0 style applications. It is possible to take advantage of many features for non-web services based applications but the primary focus and design of everything is around enabling the quick, clean, and consistent development of restful web services with a consistent downstream experience for the actual UI implementers as well as SOA architecture systems integrating with these services.

inigma-shared's Issues

JdbcTemplate Wrapper

A wrapper which allows doing a queryForObject and return null if it is an empty result set if it is an empty result set rather then throwing an exception to be handled downstream.

It is pretty intuitive to know that a sql could possibly come up with no results and things happen accordingly in many cases. Exceptions add unnecessary bulk to the code.

Improved REST invokers

Better handling of server to server REST calls that have the ability to "log" the request/response to datastores or logs as well as handle error responses with a processed or alternative bean response or even perhaps a standardized Response type. Should DRY out the overhead of making server to server rest calls via spring.

Standardize Rest Responses

They should likely have transient status codes and definitely have list of errors and better validation support/rejections and such.

All Request and Response should be supported in a generic fashion and errors should be allowed to pass back some specific data that helps clarify/relate to the errors as well.

DynamicDatasource Damaged Connections

It does not appear that bonecp is actually executing the sql statement on checkout to ensure that the connection is valid before handing it out. There seems to be a discrepency between how it worked under c3p0 and bonecp but a damaged sql statement never seems to recover.

Auth Filter not of ProviderManager Implementation?

org.springframework.beans.factory.BeanNotOfRequiredTypeException: Bean named 'authFilter' must be of type [org.springframework.security.authentication.ProviderManager], but was actually of type [com.stratix.svision.auth.SvisionAuthFilter]

Timer Thread dies if mongo closes during reload

Stack trace of relevance.

Exception in thread "Timer-1" java.lang.IllegalStateException: this Mongo has been closed
org.inigma.shared.config.MongoConfiguration.reload(MongoConfiguration.java:123)
org.inigma.shared.config.MongoConfiguration.access$000(MongoConfiguration.java:31)
org.inigma.shared.config.MongoConfiguration$1.run(MongoConfiguration.java:59)

Asynchronous monitor cannot be terminated

I don't want to have the asynchronous monitor in place as I am using a custom one. Because initialize is run internally there is no way to get a handle on the asynchronous monitor in order to terminate it. Allow a way to not have that built-in monitor to run.

Standardized Version Indicator

Similar to the monitor service, there should be version service which can help distinguish easily what version of which application is deployed/used.