[Deployers on JBoss (Deployers/JBoss)] - Re: Ordering of .ear subdeployments
by vickyk
anonymous wrote :
| The ordering solution needs to be complete, so the jboss-appl.xml needs to have an explicit ordering section that allows a unified ordering of both the application.xml and jboss-app.xml deployments.
|
So we need to have the additional section in the jboss-app.xml file where in we will define the unified ordering. Additionally the EARDeployer needs to prepare the J2eeApplicationMetaData associated with the DeploymentInfo from this unified listing in the jboss-app.xml . What we need is
1) To have <unified-order> tag in the jboss-aap.xml file , this will list the deployments in order .
2) The EARDeployer should be able to prepare the J2eeApplicationMetaData from the <unified-order> when it is present in the jboss-app.xml file .
3) Based on the presence of <unified-order> the DeploymentInfo.sortedSubDeployments flag should be made true . This will be doing the job of the comparator what we were planning .
Scott , is this what you had been expecting ?
anonymous wrote :
| In the point release we should also be able to disable the change in ordering behavior to avoid breaking existing deployments like the test-cif.ear.
|
Ok I will undo the changes in Branch_4_0 (SVN) , we can put it back once the complete ordering is incorporated .
Vicky
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3964900#3964900
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3964900
19 years, 7 months
[Design of JBoss jBPM] - process element beans
by tom.baeyens@jboss.com
i'm playing with the following idea to include in jbpm 4. i just present this idea here to get early feedback.
in various locations in jbpm, the dependency injection pattern was used. basic bean wiring is used in delegations (for including instantiation and configuration), for the overall jbpm configurations, for the services that separate jbpm from it's environment, ...
i want to bring all of these together in jbpm 4 and create one wiring mechanism for all of these.
if you look at the jbpm.cfg.xml, that is basically all wiring information on a jbpm-instance level. i think it makes sense to have similar configuration capabilities on process-definition, node and task level. probably all process elements would be able to benefit if you can just configure a hashmap of beans in that element.
this could be considered as a kind of metadata for the process, in the sense that it would be information that jbpm doesn't know about, but which makes sense to the jbpm user in that context.
once we're able to store this bean wiring information relative to all the process elements, that could very well be used for node configurations. so that we can add new node types without changing the db schema.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3964898#3964898
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3964898
19 years, 7 months
[Design of JBoss jBPM] - Re: process deployment from WAR file
by tom.baeyens@jboss.com
i'll rephrase to see if i get you correctly:
You want to make a process archive a part of the deployment structure (=available to the classloader or in a deployment directory). Then, you want to discover all the deployed process archives on the deployment directory and deploy them to the jbpm db. The hashing of process archives is the solution you propose for making the distinction between processes that are already deployed and processes that need to be (re)deployed. This to overcome the difference in lifecycle of a deployed process versus the java/webapp deployment lifecycle.
right ?
in the recent drools discussions, i realized that there are many ways to go from sources to deployments and developers are used to the different java deployment strategies. In more general terms: I'm still looking at how we can create a unified deployment model that would provide a similar picture to java, servlet, process, rules and other deployments.
It seems that we're now trying to embed our deployment model in the known existing deployment models, rather then to try and unify all of them.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3964896#3964896
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3964896
19 years, 7 months
[Design of JBoss Portal] - CMS Admin/Automated changes to HTML
by Agathon
I considered posting this in the user forums, but after considering the matter carefully, I really think this is a design issue. The problem is this: the CMS Admin portlet automatically changes HTML, stripping class attributes, and changing links.
Simply put, this is not good at all! If I specify a class attribute in a tag, its because I want it to be in there. I think it should be up to the user to decide what changes to the underlying HTML they want to make. If you really want to include automated routines to assist in this task, then please make them optional, not mandatory.
At the moment, I'm forced to live with a sub-optimal HTML that is really painful to maintain. Please fix this soon!
Thanks,
James McLean
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3964865#3964865
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3964865
19 years, 7 months
InstanceAlreadyExistsException after undeploy and repeated deploy in JBoss AS 5.0.0 Beta
by Jaroslaw Kijanowski
Hello,
I've got the following issue with JBoss AS 5.0.0 Beta:
After I run a test I see on the server console that the corresponding jar is undeploying and the home interfaces are unbinding. But when I run the test again, I get InstanceAlreadyExistsException:
11:43:12,406 INFO [Server] JBoss (MX MicroKernel) [5.0.0.Beta (build: CVSTag=HE
AD date=200608071122)] Started in 1m:3s:563ms
11:43:53,046 INFO [EjbModule] Deploying Customer
11:43:53,234 INFO [EjbModule] Deploying Account
11:43:53,250 INFO [EjbModule] Deploying Teller
11:43:53,281 INFO [EjbModule] Deploying Bank
11:43:54,687 INFO [ProxyFactory] Bound EJB Home 'Customer' to jndi 'bank/Custom
er'
11:43:54,703 INFO [ProxyFactory] Bound EJB Home 'Account' to jndi 'bank/Account
'
11:43:54,718 INFO [ProxyFactory] Bound EJB Home 'Teller' to jndi 'bank/Teller'
11:43:54,734 INFO [ProxyFactory] Bound EJB Home 'Bank' to jndi 'bank/Bank'
11:43:54,734 INFO [EJBDeployer] Deployed: file:/D:/jboss-svn4/jboss-head/testsu
ite/output/lib/bank.jar
11:44:02,093 INFO [EJBDeployer] Undeploying: file:/D:/jboss-svn4/jboss-head/tes
tsuite/output/lib/bank.jar
11:44:02,125 INFO [ProxyFactory] Unbind EJB Home 'Bank' from jndi 'bank/Bank'
11:44:02,125 INFO [EjbModule] Undeployed Bank
11:44:02,125 INFO [ProxyFactory] Unbind EJB Home 'Teller' from jndi 'bank/Telle
r'
11:44:02,125 INFO [EjbModule] Undeployed Teller
11:44:02,125 INFO [ProxyFactory] Unbind EJB Home 'Account' from jndi 'bank/Acco
unt'
11:44:02,140 INFO [EjbModule] Undeployed Account
11:44:02,140 INFO [ProxyFactory] Unbind EJB Home 'Customer' from jndi 'bank/Cus
tomer'
11:44:02,140 INFO [EjbModule] Undeployed Customer
*************
An now I run the test again:
*************
11:44:17,390 INFO [EjbModule] Deploying Customer
11:44:17,421 INFO [EjbModule] Deploying Account
11:44:17,421 INFO [EjbModule] Deploying Teller
11:44:17,437 INFO [EjbModule] Deploying Bank
11:44:17,453 INFO [EntityContainer] Registration is not done -> stop
11:44:17,453 ERROR [AbstractKernelController] Error installing to Create: name=j
boss.j2ee:module=bank.jar,service=EjbModule,uid=29596937 state=Configured mode=M
anual requiredState=Create
javax.management.InstanceAlreadyExistsException: jboss.j2ee:jndiName=bank/Custom
er,service=EJB already registered.
at org.jboss.mx.server.registry.BasicMBeanRegistry.add(BasicMBeanRegistr
y.java:765)
at org.jboss.mx.server.registry.BasicMBeanRegistry.registerMBean(BasicMB
eanRegistry.java:234)
.
.
.
11:44:17,531 INFO [EJBDeployer] Deployed: file:/D:/jboss-svn4/jboss-head/testsu
ite/output/lib/bank.jar
11:44:17,968 INFO [EJBDeployer] Undeploying: file:/D:/jboss-svn4/jboss-head/tes
tsuite/output/lib/bank.jar
******************
I saw similar issues for previous versions of the AS (all resolved) but I think this is the first for the Beta 5.0 version.
19 years, 7 months