[Design of JBoss jBPM] - Re: oryx and jbpm
by kukeltje
Eiki,
Best is to subscribe to the dev mailinglist to receive posts to this forum.
Yes we missed you a lot... no just kidding. It was kind of fruitful and I posted a new topic kind of related to this. But a short summary would be
Tom has two big reservations and one minor
- One is time (the july 1st deadline for 4.0.0.GA)
- Is it realy needed? Don't customers always use their own ui framework anyway?
- The minor one is backwards compatibility (shouldn't we support what is there now?)
The first is valid. If you want to do new things you should do them fairlly well (docs, how to embed in your own application, examples , an editor? etc)
The second one is kind of depending on what you provide I think. People using struts, velocity or whatever will not quickly als embed. jsf, certainly if what is provided out of the box is kind of limited. For an 'independent' technology like XForms that might be different, so I think that argument is not realy valid.
We did not realy talk about editors or the XForms engine, but I do admit to Toms argument that the Orbeon site is more mature. That does not say anything about the engine and/or editor though
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4215948#4215948
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4215948
15 years, 9 months
[Design of JBoss jBPM] - maven profile activation question
by tom.baeyens@jboss.com
i tried putting the following profile activation in our root pom:
<profiles>
| <profile>
| <id>database.config.overwrite</id>
| <activation>
| <property>
| <name>database</name>
| </property>
| <file>
| <exists>src/test/resources/jbpm.cfg.xml</exists>
| </file>
| </activation>
| <build>
| ...
|
i expected the profile to be activated only when both property database was set *and* the given resource file exists.
but if the file activation is present, then the property activation seems to be ignored.
if i put only one of the activations in there, in both cases it works correctly.
the idea was that only for modules that have this resource, the profile should be activated when the database property is set. the workaround that i applied was duplicating this profile declaration in examples and test-db.
but i am still curious to know if this is a bug or my misinterpretation
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4215925#4215925
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4215925
15 years, 9 months