Ravi Reddy

Usage Of Enterprise Mule Version : I'm posting this post what are the problems i faced during integration of Mule Enterprise Version(2.2.4) in service development in SOA.

Issue :

org.mule.api.lifecycle.LifecycleException: Failed to invoke lifecycle phase "start" on object: SedaService{TestService}

at org.mule.lifecycle.DefaultLifecyclePhase.applyLifecycle(DefaultLifecyclePhase.java:276)

Caused by: org.mule.api.lifecycle.InitialisationException: Initialisation Failure: Could not find portType named {http://aaa.bbb.ccc/services}TestServices at org.mule.transport.cxf.CxfMessageReceiver.doInitialise(CxfMessageReceiver.java:305)

Solution:

The solution for the issue which we are facing by using Enterprise Mule version.The Enterprise Mule which uses particular version CXF (2.1.5) which predefining the wsdl port name should end with "Port" in the *.wsdl files.

Below code changes which we made during fixing this issue without changing any "classpath:*" protocol for associating a wsdlLocation with a service in the mule config.

Please see the code changes in brown color text.

Before Fix (Standalone Mule):
wsdl:service name="TestServices"
wsdl:port binding="mc:TestService" name="TestService"
soap:address location="http://localhost:8080/services/v1/TestServices"
wsdl:port
wsdl:service

After Fix (Enterprise Mule):
wsdl:service name="TestServices"
wsdl:port binding="mc:TestService" name="TestServicesPort"
soap:address location="http://localhost:8080/services/v1/TestServices"
wsdl:port
wsdl:service

Please use the opening and closing tags in above code.

Sunday, February 7, 2010

Flex Proto Type

Check out this SlideShare Presentation:

Flex Proto Type

View more presentations from ravireddy76.

Monday, July 6, 2009

Richfaces Proto Type

Check out this SlideShare Presentation:

Richfaces Proto Type

View more documents from ravireddy76.

Friday, March 27, 2009

Icefaces ProtoType For Java & J2EE Technologies

Proof Of Concept Product

View more presentations from ravireddy76.

Friday, February 6, 2009

Presentation(UI or Client) framework evaluation and options

Objective:

It is always difficult and challenging task in order to evaluate the which is best frame work for presentation or client layer in java. Here I'm trying to evaluate the some of the presentation frameworks in java based on the different software analyst and architects perspective views and put them side-by-side to compare their convenience for developers, in terms of performance, scalability, maintainability, learning effort and rapid development etc. in the future.

Struts
FrameWork Type : Request-based framework
Learning Effort : Fast and Easy
Maintenance : Easy
Performance/
Scalability : Very Good
Others : Widely demand and highly used

JSF
FrameWork Type : Component-based framework
Learning Effort: Fast and Easy
Maintenance : Easy
Performance/
Scalability : Very Good
Others : Suggested by many people in java world (present day).Framework is not matured.

Tapestry
FrameWork Type : Component-based framework
Learning Effort : Time Consuming
Maintenance : Moderate
Performance/
Scalability : Very Good
Others : Only few organizations uses and few tech’s available to work in this framework (less documentation and FAQ’s available).

Web Works
FrameWork Type : Request-based framework
Learning Effort : Easy
Maintenance : Easy
Performance/
Scalability : Very Good
Others : Only few organizations use the framework (Now it’s merged with struts)

Spring MVC
FrameWork Type : Request-based framework
Learning Effort : Moderate
Maintenance : Easy
Performance/
Scalability : Very Good
Others : Lots of configuration file setups (.xml),No Ajax support.

Wicket
FrameWork Type : Component-based framework
Learning Effort : More
Maintenance : Moderate
Performance/
Scalability : Very Good
Others : Only few organizations uses and few tech’s available to work in this framework (less documentation and FAQ’s available).

Swing
FrameWork Type : Component-based framework
Learning Effort : Moderate
Maintenance : Moderate
Performance/
Scalability : Moderate
Others : It requires sufficient skill sets and application architecture than web applications.

Other Web Frameworks:

GWT (Google Web Tool Kit), Ice faces,Rich faces,Seam, Beehive, Stripes, Flex etc

Performance Overview:

Below performance analysis are done for some of the frameworks based on CRUD + S ([C]reate-[R]ead-[U]pdate-[D]elete+[S]earch) approach and The Grinder 3 testing framework.

Below performance numbers and charts are retrieved from http://www.sourcelabs.com

1) JSF

2) Struts + Tiles (Tiles is a template system and decoration framework. It can be used to create a common look and feel for a web application. Tiles can also be used to create reusable view components.)

3) Struts + Site Mesh (Site Mesh is a web-page layout and decoration framework to maintain consistent look/feel, navigation and layout scheme. Which allows look and feel to be abstracted from the content/functionality of a web-application?)

4) Tapestry

References:

http://raibledesigns.com/rd/entry/comparing_web_frameworks_time_for,

http://sandbox.sourcelabs.com/kosta/web_ui_compare/readme/,

http://java.sys-con.com/,

http://www.oracle.com/technology/pub/articles,

http://forum.java.sun.com/index.jspa,

http://java.net/,

http://www.javaworld.com/ ,

http://www.theserverside.com/discussions/