[JBoss JIRA] Moved: (JBJCA-12) Programmatic Connection Definition Deployment
by Jesper Pedersen (JIRA)
[ https://jira.jboss.org/jira/browse/JBJCA-12?page=com.atlassian.jira.plugi... ]
Jesper Pedersen moved JBAS-1425 to JBJCA-12:
--------------------------------------------
Project: JBoss JCA (was: JBoss Application Server)
Key: JBJCA-12 (was: JBAS-1425)
Component/s: Core
(was: JCA service)
Security: (was: Public)
> Programmatic Connection Definition Deployment
> ---------------------------------------------
>
> Key: JBJCA-12
> URL: https://jira.jboss.org/jira/browse/JBJCA-12
> Project: JBoss JCA
> Issue Type: Task
> Components: Core
> Reporter: Adrian Brock
> Assignee: Jesper Pedersen
> Priority: Minor
>
> Forums Discussion Thread: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=48673
> Provide a mechanism where ConnectionFactorys/DataSources (Connection Definitions)
> can be deployed/undeployed programmatically.
> The basic design is as follows:
> 1) Provide a mechanism to instantiate MetaData for a connection factory.
> This information is the same as the -ds.xml deployment format.
> The MetaData can be logically divided into at least the following categories:
> * RAR/ConnectionDefinition identification
> * ManagedConnectionFactory
> * Pool
> * Security
> * ConnectionManager
> * Proxy/JNDI binding
> 2) Write an optimized version of the MetaData for the DataSource deployments
> which are really a simplified version of the ConnectionFactory deployments with some
> hardwiring.
> 3) Write a service that deploys the ConnectionFactory (creates MBeans)
> from the MetaData and undeploys them based on their id (jndi binding).
> 4) Convert the ConnectionFactory deployer to construct the MetaData from the -ds.xml
> files and invoke the service new service.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 7 months
[JBoss JIRA] Created: (JBAS-5864) Redeploy shows
by Arjen Smedes (JIRA)
Redeploy shows
--------------
Key: JBAS-5864
URL: https://jira.jboss.org/jira/browse/JBAS-5864
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Deployers, JSF
Affects Versions: JBossAS-4.2.3.GA
Environment: Kubuntu, JDK 1.6
Reporter: Arjen Smedes
Assignee: Ales Justin
Hi, running jdk1.6.0_02, Maven2 (2.0.7) and jboss maven plugin (1.3.1) to deploy JSF-1.2 webapp into JBOSS-4.2.3.GA. Redeploy generates the following stacktrace:
21:56:38,684 INFO [TomcatDeployer] undeploy, ctxPath=/upstream2, warUrl=.../tmp/deploy/tmp33776upstream2-exp.war/
21:56:38,693 ERROR [[/upstream2]] Exception sending context destroyed event to listener instance of class org.jboss.web.jsf.integration.config.JBossJSFConfigureListener
java.lang.NullPointerException
at com.sun.faces.config.ConfigureListener.contextDestroyed(ConfigureListener.java:234)
at org.apache.catalina.core.StandardContext.listenerStop(StandardContext.java:3895)
at org.apache.catalina.core.StandardContext.stop(StandardContext.java:4527)
at org.apache.catalina.core.ContainerBase.destroy(ContainerBase.java:1163)
at org.apache.catalina.core.StandardContext.destroy(StandardContext.java:4617)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
After that, the application runs normally (as it seems, it's a HelloWorld for JSF, so not much functionality built in as yet).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 7 months