I figured out the error. The namespace wasn't declared in component.xml since
it moved from 'core' to 'jbpm'
But still the database contains no tables.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4057253#4057253
Reply to the post :
Gavin, I have followed the approach and I can see the hibernate mappings on the
console, however the tables are not being created and I'm sure that the
datasource configuration is correct pointing to the right database.
On the other end when commenting out the bpm configuration from the
Got it sorted out. All I needed was to create the jBPMContext again.
Thanks
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4057267#4057267
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4057267
Now this approach does not work out anymore since I upgraded from CVS to
version 1.3.0.BETA1
@Interceptor(NEVER) is no longer there because of a change in API. I have
created my modification as follows and still the jbpm database is not being
deployed automatically without having any process
@BypassInterceptors is the replacement.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4057214#4057214
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4057214
___
jboss-user mailing
Thanks Gavin but still that didn't work. Is there any parameter for the
BypassInterceptors ?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4057218#4057218
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4057218
I just added a new protected method, so you can do:
@Scope(ScopeType.APPLICATION)
| @BypassInterceptors
| @Startup
| @Name(org.jboss.seam.bpm.jbpm)
| public class MyJbpm
| {
| protected boolean isProcessDeploymentEnabled()
| {
| return true;
| }
| }
View
Great, I'll checkout again from CVS and give it a try.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4057223#4057223
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4057223
___
Ok I got the concept but now how to make this class initialize itself on
startup? Would I need to invoke it from a servlet?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4035248#4035248
Reply to the post :
Let's see the class you want to start up
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4035255#4035255
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4035255
___
jboss-user mailing
I guess I need to override the startup method. This is what I have done so far
| import static org.jboss.seam.InterceptionType.NEVER;
| import static org.jboss.seam.annotations.Install.BUILT_IN;
|
| import org.jboss.seam.ScopeType;
| import org.jboss.seam.annotations.Create;
|
You just need
@Name(org.jboss.seam.core.jbpm.init)
| @Install(true)
| public class JbpmInitializer extends Jbpm {
to get it to start.
I'm not sure which lines actually start jbpm, but I guess you know ;)
I would do a super.startup() as well, to make sure that all the standard seam
init
thanks for the feedback. I gave it a try at a simple level and I don't think
it's working out. How can I check if the component has been initialized?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4035268#4035268
Reply to the post :
It will appear in the startup log and on the debug page in application scope as
xxx.component
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4035270#4035270
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4035270
I guess it's working, checked the logs and found the following
| 2007-04-06 14:04:30,031 INFO [org.jboss.seam.Component] Component:
org.jboss.seam.core.jbpm.init, scope: APPLICATION, type: JAVA_BEAN, class:
org.jbpm.console.core.JbpmInitializer
|
View the original post :
upon installation the executed code is done in the startup method right?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4035273#4035273
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4035273
Yes, thats working. As the base component is annotated @Startup and in the
application startup, then the component will be created during application
startup, and hence, the method annotated @create will be run
View the original post :
This one works well for me
@Intercept(NEVER)
| @Name(org.jboss.seam.core.jbpm.init)
| @Startup(depends={org.jboss.seam.core.jbpm})
| @Install(dependencies=org.jboss.seam.core.jbpm)
| public class JbpmInitializer extends Jbpm {
|
| private static final LogProvider log =
Thanks a lot, got it working. I had commented out the jbpm configuration in
components.xml
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4035330#4035330
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4035330
I got your point, will give it a try. Thanks for the suggestion
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4034736#4034736
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4034736
Thanks for the suggestion. I'll give it a try
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4034738#4034738
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4034738
___
jboss-user
I'm confused about what you want. I think you might just want to start up JBPM
when Seam starts, and then deploy your process definitions some other way? If
so, look at the way org.jboss.seam.core.Jbpm.startup works, and extend the
class, and overriding the startup method so it starts up
Any update on this? the schema fails to be created.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4033658#4033658
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4033658
___
Do you have the necessary lines in components.xml?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4031768#4031768
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4031768
___
Yes gavin the configuration is there in components.xml
now the thing is that i don't have any processes deployed the configuration
looks as follows:
| core:jbpm
| core:process-definitions/core:process-definitions
| core:pageflow-definitions/core:pageflow-definitions
|
Wellthen, of course no process definitions will be created!
What did you expect?
You'll have to find some other means to deploy the processes, if you don't want
to list them in components.xml.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4031778#4031778
I have other alternatives but would I still benefit from using the full
features related to JBPM?
One quick approach is to deploy a dummy process. But wouldn't it be appropriate
to deploy the jBPM just when it's configuration is present?
View the original post :
Hold on, what is it that you want to be created? The schema, or the data in the
schema?
If all you want to do is create the schema, you only have to enable schema
export in hibernate.cfg.xml. Just like in the examples.
View the original post :
exactly i just want to enable the schema export, nothing else is required and
this is already specified in the hibernate.cfg.xml
| property name=hbm2ddl.autocreate/property
|
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4031797#4031797
Reply to the
Gavin, the hibernate.xml is not being parsed from within the jar. I modified it
to be non deployable and still no exceptions has been thrown at deployment
time.
I verified the file exists in the archive
View the original post :
30 matches
Mail list logo
