[Javassist Development] New message: "Building Web 2.0 UIs with JSF, Realtime Updates with JSF and Ajax Push Taught at GIDS"
by shaguf mohtisham
User development,
A new message was posted in the thread "Building Web 2.0 UIs with JSF, Realtime Updates with JSF and Ajax Push Taught at GIDS":
http://community.jboss.org/message/528693#528693
Author : shaguf mohtisham
Profile : http://community.jboss.org/people/shaguf5575
Message:
--------------------------------------------------------------
JavaServer Faces is a Java-based Web application framework intended developed to simplify development integration of Web-based user interfaces. It is often mentioned together with Ajax, a combination of technologies that makes it possible to create rich user interfaces. Since JSF supports multiple output formats, Ajax-enabled components can easily be added to enrich JSF-based user interfaces. Oracle's Frank Nimphius says that Service Oriented Architecture (SOA) has become a reality in modern software development but Web services don't have a user interface. This is fine if communication is between machines. But what about human interaction like in data entry and work flow? Users need an application display they feel comfortable working with. So what about building Web 2.0 user interfaces for service oriented architectures? Does it work, or does it hurt - and if so, how bad is it? Frank is coming this summer to India's biggest summit for the software developer ecosystem - Great Indian Developer Summit (http://www.developersummit.com/) to show how JavaServer Faces can be used to build compelling Ajax user interfaces for Web Services models giving end users a comfortable working environment that includes client side validation and user interface customization.
In his second session at GIDS 2010, Frank addresses the topic of implementing automatic UI refreshes. To web application users, it must appear as if the Web reinvents itself once a year with more interactive UIs, increasing performance through partial page refreshes, and desktop-like usability patterns that allow users to become as productive using web applications as they are using real desktop clients. One technical detail, though, hasn't changed in the past and is unlikely to change in the near future: HTTP. Hypertext Transfer Protocol is based on the request-response principle in which the client sends a query to the server and the server responds with the requested data. Between requests, no connection is maintained between the client and the server that would allow server-side logic to send more data unasked. Any changes in the underlying data layer used by an application are first detected within the next client request. Hopefully, it doesn't come to you by surprise when we say that in the modern days of Web 2.0 and Rich Enterprise Applications (REA), the Web still is disconnected and stateless. So, in these modern days of Web 2.0 and Rich Enterprise Applications (REA), is the Web still is disconnected and stateless? Not really, because you frequently use some applications on the Web that update their client UIs with server-side changes without your needing to do anything. The question, therefore, is how this was accomplished and whether you can do the same in JavaServer Faces. In his session, Frank will guide attendees through the options that are available in AJAX and other implementation technologies of Rich Internet Applications (RIA) to implement automatic UI refreshes.
Frank Nimphius is a principal product manager for application development tools at Oracle Corporation since 1999. He actively contributes to the development of Oracle JDeveloper and the Oracle Application Development Framework (ADF). He represents the Oracle J2EE development team at J2EE conferences world wide, including various Oracle user groups and the Oracle Open World conference. The talk 'Building Web 2.0 User Interfaces for Web Service Models using JSF' will be co-presented by Jobinesh Purushothaman. Jobinesh Purushothaman is an enterprise Java specialist with 10+ years of experience in the industry. He is involved in design and architectural decisions of various products using ADF and JavaEE technologies. He is interested in developing more simplified enterprise technologies where developers can focus on their business solutions rather on the technology complexities.
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/528693#528693
14 years, 11 months
[EJB 3.0] New message: "Re: Error on deploy persistence unit"
by Jose M. M. M.
User development,
A new message was posted in the thread "Error on deploy persistence unit":
http://community.jboss.org/message/528680#528680
Author : Jose M. M. M.
Profile : http://community.jboss.org/people/jotremar
Message:
--------------------------------------------------------------
09:48:18,446 INFO [DeployHandler] Failed to complete command: [start] for deployment: names=[vfszip:/E:/jboss/server/default/deploy/Practica_final-ejb.jar/], copyContent=true
org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
DEPLOYMENTS MISSING DEPENDENCIES:
Deployment "jboss.j2ee:jar=Practica_final-ejb.jar,name=TiendaBean,service=EJB3" is missing the following dependencies:
Dependency "<UNKNOWN jboss.j2ee:jar=Practica_final-ejb.jar,name=TiendaBean,service=EJB3>" (should be in state "Described", but is actually in state "** UNRESOLVED Demands 'persistence.unit:unitName=#ejbPU' **")
Deployment "jboss.j2ee:jar=Practica_final-ejb.jar,name=TiendaBean,service=EJB3_endpoint" is missing the following dependencies:
Dependency "jboss.j2ee:jar=Practica_final-ejb.jar,name=TiendaBean,service=EJB3" (should be in state "Configured", but is actually in state "PreInstall")
Deployment "persistence.unit:unitName=#ejbPU" is missing the following dependencies:
Dependency "jboss.jca:name=comercioBD,service=DataSourceBinding" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss.jca:name=comercioBD,service=DataSourceBinding' **")
DEPLOYMENTS IN ERROR:
Deployment "<UNKNOWN jboss.j2ee:jar=Practica_final-ejb.jar,name=TiendaBean,service=EJB3>" is in error due to the following reason(s): ** UNRESOLVED Demands 'persistence.unit:unitName=#ejbPU' **
Deployment "jboss.jca:name=comercioBD,service=DataSourceBinding" is in error due to the following reason(s): ** NOT FOUND Depends on 'jboss.jca:name=comercioBD,service=DataSourceBinding' **
at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:993)
at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:939)
at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:873)
at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.checkComplete(MainDeployerAdapter.java:128)
at org.jboss.profileservice.management.upload.remoting.AbstractDeployHandler.start(AbstractDeployHandler.java:265)
at org.jboss.profileservice.management.upload.remoting.AbstractDeployHandler.invoke(AbstractDeployHandler.java:177)
at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:891)
at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:106)
at org.jboss.remoting.Client.invoke(Client.java:1724)
at org.jboss.remoting.Client.invoke(Client.java:629)
at org.jboss.profileservice.management.upload.remoting.StreamingDeploymentTarget.invoke(StreamingDeploymentTarget.java:305)
at org.jboss.profileservice.management.upload.remoting.StreamingDeploymentTarget.start(StreamingDeploymentTarget.java:190)
at org.jboss.profileservice.management.upload.DeploymentProgressImpl.start(DeploymentProgressImpl.java:231)
at org.jboss.profileservice.management.upload.DeploymentProgressImpl.run(DeploymentProgressImpl.java:88)
at org.rhq.plugins.jbossas5.util.DeploymentUtils.run(DeploymentUtils.java:120)
at org.rhq.plugins.jbossas5.util.DeploymentUtils.deployArchive(DeploymentUtils.java:103)
at org.rhq.plugins.jbossas5.ApplicationServerComponent.createContentBasedResource(ApplicationServerComponent.java:400)
at org.rhq.plugins.jbossas5.ApplicationServerComponent.createResource(ApplicationServerComponent.java:211)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:482)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
09:48:18,840 ERROR [DeploymentUtils] Failed to start deployment [vfszip:/E:/jboss/server/default/deploy/Practica_final-ejb.jar/] during initial deployment of 'Practica_final-ejb.jar'. Backing out the deployment...
java.lang.RuntimeException: org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
DEPLOYMENTS MISSING DEPENDENCIES:
Deployment "jboss.j2ee:jar=Practica_final-ejb.jar,name=TiendaBean,service=EJB3" is missing the following dependencies:
Dependency "<UNKNOWN jboss.j2ee:jar=Practica_final-ejb.jar,name=TiendaBean,service=EJB3>" (should be in state "Described", but is actually in state "** UNRESOLVED Demands 'persistence.unit:unitName=#ejbPU' **")
Deployment "jboss.j2ee:jar=Practica_final-ejb.jar,name=TiendaBean,service=EJB3_endpoint" is missing the following dependencies:
Dependency "jboss.j2ee:jar=Practica_final-ejb.jar,name=TiendaBean,service=EJB3" (should be in state "Configured", but is actually in state "PreInstall")
Deployment "persistence.unit:unitName=#ejbPU" is missing the following dependencies:
Dependency "jboss.jca:name=comercioBD,service=DataSourceBinding" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss.jca:name=comercioBD,service=DataSourceBinding' **")
DEPLOYMENTS IN ERROR:
Deployment "<UNKNOWN jboss.j2ee:jar=Practica_final-ejb.jar,name=TiendaBean,service=EJB3>" is in error due to the following reason(s): ** UNRESOLVED Demands 'persistence.unit:unitName=#ejbPU' **
Deployment "jboss.jca:name=comercioBD,service=DataSourceBinding" is in error due to the following reason(s): ** NOT FOUND Depends on 'jboss.jca:name=comercioBD,service=DataSourceBinding' **
at org.jboss.profileservice.management.upload.remoting.StreamingDeploymentTarget.invoke(StreamingDeploymentTarget.java:313)
at org.jboss.profileservice.management.upload.remoting.StreamingDeploymentTarget.start(StreamingDeploymentTarget.java:190)
at org.jboss.profileservice.management.upload.DeploymentProgressImpl.start(DeploymentProgressImpl.java:231)
at org.jboss.profileservice.management.upload.DeploymentProgressImpl.run(DeploymentProgressImpl.java:88)
at org.rhq.plugins.jbossas5.util.DeploymentUtils.run(DeploymentUtils.java:120)
at org.rhq.plugins.jbossas5.util.DeploymentUtils.deployArchive(DeploymentUtils.java:103)
at org.rhq.plugins.jbossas5.ApplicationServerComponent.createContentBasedResource(ApplicationServerComponent.java:400)
at org.rhq.plugins.jbossas5.ApplicationServerComponent.createResource(ApplicationServerComponent.java:211)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:482)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
Caused by: org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
DEPLOYMENTS MISSING DEPENDENCIES:
Deployment "jboss.j2ee:jar=Practica_final-ejb.jar,name=TiendaBean,service=EJB3" is missing the following dependencies:
Dependency "<UNKNOWN jboss.j2ee:jar=Practica_final-ejb.jar,name=TiendaBean,service=EJB3>" (should be in state "Described", but is actually in state "** UNRESOLVED Demands 'persistence.unit:unitName=#ejbPU' **")
Deployment "jboss.j2ee:jar=Practica_final-ejb.jar,name=TiendaBean,service=EJB3_endpoint" is missing the following dependencies:
Dependency "jboss.j2ee:jar=Practica_final-ejb.jar,name=TiendaBean,service=EJB3" (should be in state "Configured", but is actually in state "PreInstall")
Deployment "persistence.unit:unitName=#ejbPU" is missing the following dependencies:
Dependency "jboss.jca:name=comercioBD,service=DataSourceBinding" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss.jca:name=comercioBD,service=DataSourceBinding' **")
DEPLOYMENTS IN ERROR:
Deployment "<UNKNOWN jboss.j2ee:jar=Practica_final-ejb.jar,name=TiendaBean,service=EJB3>" is in error due to the following reason(s): ** UNRESOLVED Demands 'persistence.unit:unitName=#ejbPU' **
Deployment "jboss.jca:name=comercioBD,service=DataSourceBinding" is in error due to the following reason(s): ** NOT FOUND Depends on 'jboss.jca:name=comercioBD,service=DataSourceBinding' **
at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:993)
at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:939)
at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:873)
at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.checkComplete(MainDeployerAdapter.java:128)
at org.jboss.profileservice.management.upload.remoting.AbstractDeployHandler.start(AbstractDeployHandler.java:265)
at org.jboss.profileservice.management.upload.remoting.AbstractDeployHandler.invoke(AbstractDeployHandler.java:177)
at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:891)
at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:106)
at org.jboss.remoting.Client.invoke(Client.java:1724)
at org.jboss.remoting.Client.invoke(Client.java:629)
at org.jboss.profileservice.management.upload.remoting.StreamingDeploymentTarget.invoke(StreamingDeploymentTarget.java:305)
... 17 more
09:48:18,844 INFO [DeployHandler] Remove, [vfszip:/E:/jboss/server/default/deploy/Practica_final-ejb.jar/]
09:48:18,853 WARN [CreateResourceRunner] Throwable was found in creation report for request [1]: java.lang.RuntimeException: org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
DEPLOYMENTS MISSING DEPENDENCIES:
Deployment "jboss.j2ee:jar=Practica_final-ejb.jar,name=TiendaBean,service=EJB3" is missing the following dependencies:
Dependency "<UNKNOWN jboss.j2ee:jar=Practica_final-ejb.jar,name=TiendaBean,service=EJB3>" (should be in state "Described", but is actually in state "** UNRESOLVED Demands 'persistence.unit:unitName=#ejbPU' **")
Deployment "jboss.j2ee:jar=Practica_final-ejb.jar,name=TiendaBean,service=EJB3_endpoint" is missing the following dependencies:
Dependency "jboss.j2ee:jar=Practica_final-ejb.jar,name=TiendaBean,service=EJB3" (should be in state "Configured", but is actually in state "PreInstall")
Deployment "persistence.unit:unitName=#ejbPU" is missing the following dependencies:
Dependency "jboss.jca:name=comercioBD,service=DataSourceBinding" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss.jca:name=comercioBD,service=DataSourceBinding' **")
DEPLOYMENTS IN ERROR:
Deployment "<UNKNOWN jboss.j2ee:jar=Practica_final-ejb.jar,name=TiendaBean,service=EJB3>" is in error due to the following reason(s): ** UNRESOLVED Demands 'persistence.unit:unitName=#ejbPU' **
Deployment "jboss.jca:name=comercioBD,service=DataSourceBinding" is in error due to the following reason(s): ** NOT FOUND Depends on 'jboss.jca:name=comercioBD,service=DataSourceBinding' **
- Enable DEBUG logging to see the stack trace.
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/528680#528680
14 years, 11 months
[EJB 3.0] New message: "Re: EJB 3.1 Singleton and Cluster"
by jaikiran pai
User development,
A new message was posted in the thread "EJB 3.1 Singleton and Cluster":
http://community.jboss.org/message/528662#528662
Author : jaikiran pai
Profile : http://community.jboss.org/people/jaikiran
Message:
--------------------------------------------------------------
Sorry, forgot to reply to this earlier.
> Jojopotatoe wrote:
>
>
>
> Do you plan to apply HA fonctionnality to @Singleton bean, i mean ability to restart the singleton bean on others server instance on a failure ?
>
>
Right now, the main priority is to get the EJB3.1 spec compliant singleton implementation available ASAP. Although, i haven't looked into the details about HA functionality for Singleton, i guess we could do/use the same infrastructure as what we have for providing HA for @Stateful beans. So yes, i think this should be possible. More on this, once we have the @Singleton implementation out. So stay tuned!
> Jojopotatoe wrote:
>
> I am very happy to see part of the EJB 3.1 in the current version, many thanks.
Good to know
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/528662#528662
14 years, 11 months
[EJB 3.0] New message: "Re: Entity Manager with BMT and Transaction Timeout"
by Alexander Hartner
User development,
A new message was posted in the thread "Entity Manager with BMT and Transaction Timeout":
http://community.jboss.org/message/528647#528647
Author : Alexander Hartner
Profile : http://community.jboss.org/people/ejb3workshop
Message:
--------------------------------------------------------------
I enabled the complete hibernate context at trace level and got the following.
> 2010-02-25 23:09:00,600 TRACE [org.hibernate.transaction.CacheSynchronization] transaction before completion callback
> 2010-02-25 23:09:00,600 TRACE [org.hibernate.jdbc.JDBCContext] before transaction completion
> 2010-02-25 23:09:00,601 TRACE [org.hibernate.impl.SessionImpl] before transaction completion
> 2010-02-25 23:09:00,601 TRACE [org.hibernate.ejb.AbstractEntityManagerImpl] automatically flushing session
> 2010-02-25 23:09:00,601 TRACE [org.hibernate.impl.SessionImpl] automatically flushing session
> 2010-02-25 23:09:00,601 TRACE [org.hibernate.event.def.AbstractFlushingEventListener] flushing session
> 2010-02-25 23:09:00,601 DEBUG [org.hibernate.event.def.AbstractFlushingEventListener] processing flush-time cascades
> 2010-02-25 23:09:00,601 TRACE [org.hibernate.engine.Cascade] processing cascade ACTION_PERSIST_ON_FLUSH for: com.abc.entities.Batch 2010-02-25 23:09:00,601 TRACE [org.hibernate.engine.Cascade] done processing cascade ACTION_PERSIST_ON_FLUSH for: com.abc.entities.Batch
> 2010-02-25 23:09:00,601 DEBUG [org.hibernate.event.def.AbstractFlushingEventListener] dirty checking collections
> 2010-02-25 23:09:00,601 TRACE [org.hibernate.event.def.AbstractFlushingEventListener] Flushing entities and processing referenced collections
> 2010-02-25 22:40:12,978 INFO [org.hibernate.ejb.Ejb3Configuration] found EJB3 Entity bean: com.abc.AuditTrailEntry ...skipping...
> 2010-02-25 23:09:00,601 ERROR [org.hibernate.LazyInitializationException] failed to lazily initialize a collection of role: com.abc.entities...
Not really sure what to look for.
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/528647#528647
14 years, 11 months
[JCA Development] New message: "Re: Standalone JCA: JNDI binding for multiple connection factories..."
by Jesper Pedersen
User development,
A new message was posted in the thread "Standalone JCA: JNDI binding for multiple connection factories...":
http://community.jboss.org/message/528646#528646
Author : Jesper Pedersen
Profile : http://community.jboss.org/people/jesper.pedersen
Message:
--------------------------------------------------------------
> The 1.6 Final Draft November 2009 argues with itself over this:
Nah, 6.5.1.3, 17.5.1.1, 20.6.2, 20.6.3 specifies the implementation requirements for a CF (javax.resource.Referenceable + java.io.Serializable).
The text in 20.6.1 gives a hint to the implementor, that if the +naming server+ doesn't support both mechanisms, one can be used. See the 3 bullets in the section.
> I'm not sure about the unique name part though.
Yes, this has to be designed.
> What is the alias? Do you mean generically or with something
> like a LinkRef (I've never used that before so not sure how it works
> yet).
Something like,
java:/eis/myresourceadapter --> java:/uniquenamegeneratedbythecontainer
LinkRef or other solutions is an implementation detail, we can worry about once we have the design for the unique names.
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/528646#528646
14 years, 11 months
