June 2009 - jboss-dev-forums - Jboss List Archives

[Design of JBoss jBPM] - please keep the docs up to date

by kukeltje

In the past, it happened to often that the docs were out of date in relation to the code. Lets prevent this from happening again. In chapter 5 of the devguide a ProcessFactory is mentioned, but that is not in the source anymore. Most likely the ProcessDefinitionBuilder is meant. In 5.5 the link to the api docs is not correct and a ProcessBuilder is also mentioned in one of the paragraphs. I know it takes some additional time of the devs, but if these things are not correct, (potential) users are probably deterred since it takes to much time and docs are not correct. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4235306#4235306 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4235306

14 years, 12 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: mc-script - and other stupid ideas

by adrian＠jboss.org

While doing this I came across a problem with re-using the MC metadata classes. Kabir appears to have found the same problem in the aop stuff and used the same hack that I have below. Some of the ValueAdapters are defined at the package/schema level rather than being associated with the type. So I have to redefine them in my schema otherwise I can't use the classes for xml parsing. This is incredibly brittle configuration. https://svn.jboss.org/repos/jbossas/projects/mc-script/trunk/src/main/jav... If somebody adds a new adapter, other users of the classes will break because they don't know about the new adapter. They probably won't use the new adapter but the construction of the SchemaBinding from the annotations will look at the class being adapted and complain. These adapters should be on their respective types. The only reason to define them on the schema is when you can't change the type. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4235288#4235288 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4235288

14 years, 12 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Problem deploying JBPM4.0.0.Beta2 on JBOSS 5.0.1.GA

by dabster2000

Woops sry - it was meant for the user forum just posted wrong. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4235287#4235287 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4235287

14 years, 12 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: mc-script - and other stupid ideas

by adrian＠jboss.org

"adrian(a)jboss.org" wrote : By way of a stupid example Its a stupid idea because metadata should really be declarative. No tool is going to be able to understand what the javascript means/does. ;-) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4235284#4235284 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4235284

14 years, 12 months

1
0
0 / 0

[Design the new POJO MicroContainer] - mc-script - and other stupid ideas

by adrian＠jboss.org

I got a bit bored yesterday so I decided to write an example that shows how easy it is to extend the microctonainer's value system. (Actually the example really shows off JBossXB's xml any handling). By way of a stupid example, I decided to write a new ValueMetaData that determines its values using the Java6 script engine stuff. (As usual change svn to anonsvn if you don't have a jboss.org account). https://svn.jboss.org/repos/jbossas/projects/mc-script/trunk/src/main/jav... You should be able to work out how to use it from the xsd https://svn.jboss.org/repos/jbossas/projects/mc-script/trunk/src/main/res... or the tests https://svn.jboss.org/repos/jbossas/projects/mc-script/trunk/src/test/res... Here I'll explain how it works. The extension point is that a property (or parameter or collection element) configuration takes any ValueMetadata because it is defined in the xml to be an xsd:any element. Using the JBossXB annotations to define an xml group (you don't actually need the group, a plain type with a getter/setter marked @XmlAnyElement will also work if it is not of type DOM element) | @JBossXmlGroup | ({ | @JBossXmlChild(name="array", type=AbstractArrayMetaData.class), | @JBossXmlChild(name="collection", type=AbstractCollectionMetaData.class), | @JBossXmlChild(name="inject", type=AbstractInjectionValueMetaData.class), | @JBossXmlChild(name="list", type=AbstractListMetaData.class), | @JBossXmlChild(name="map", type=AbstractMapMetaData.class), | @JBossXmlChild(name="null", type=AbstractValueMetaData.class), | @JBossXmlChild(name="set", type=AbstractSetMetaData.class), | @JBossXmlChild(name="this", type=ThisValueMetaData.class), | @JBossXmlChild(name="value", type=StringValueMetaData.class), | @JBossXmlChild(name="value-factory", type= AbstractValueFactoryMetaData.class) | }) | @JBossXmlGroupText(wrapper= StringValueMetaData.class, property="value") | | // HERE! | | @JBossXmlGroupWildcard(wrapper= AbstractValueMetaData.class, property="value") public interface ValueMetaData extends JBossInterface, MetaDataVisitorNode | and in the xsd | | | <xsd:group name="valueGroup"> | | | <snipped/> | | | <xsd:any namespace="##other" processContents="strict"> | | <xsd:annotation> | | <xsd:documentation>An extension value</xsd:documentation> | | </xsd:annotation> | | </xsd:any> | | </xsd:choice> | | </xsd:group> | This means I can create a new subclass of ValueMetaData in its own xml namespace and use it anywhere a "ValueGroup" is defined in the xml (or equivalently a property is of type ValueMetaData - or a collection of them). This is what I've done with the ScriptValueMetaData that invokes a script to determine the value. | @JBossXmlSchema(namespace="urn:jboss:bean-deployer:script:2.0", elementFormDefault=XmlNsForm.QUALIFIED) | @XmlRootElement(name="script") | @XmlType(name="scriptType", propOrder="parameters") | public class ScriptValueMetaData extends AbstractValueMetaData | The example is slightly more complicated than it needs to be since I added an extra feature so you can pass parameters (including injections from other beans) which means it has to handle visiting the children of the metadata (the parameters) and a few other bits and pieces like making the "controllerContext" available as a variable to the script. Without those complications, you can see that all the work is just in getValue(TypeInfo, ClassLoader). There are a number of other places within the microcontainer and deployment or classloader metadata that can be extended in this way, e.g. the classloader requirement/capabilities. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4235282#4235282 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4235282

14 years, 12 months

1
0
0 / 0

[Design of JBoss Web] - Writing the ThreadName in AccessLogValue

by vijayamaladoss

Hi, I am using Jboss EAP 4.2 GA and I want to write the thread name in the access log using "%I" pattern. But seems that this is not yet supported in Jbossweb. I decompiled the code of Jbossweb.jar and I didnt find the AccessLogValve.ThreadNameElement defined there. I am able to do the same on a Standalone tomcat container (version 6.0) Should I need a different version of Jbossweb to use this ? Thanks, VJ View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4235270#4235270 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4235270

14 years, 12 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Problem deploying JBPM4.0.0.Beta2 on JBOSS 5.0.1.GA

by kukeltje

wrong forum, use the userforum for this View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4235267#4235267 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4235267

14 years, 12 months

1
0
0 / 0

[Design of JBoss jBPM] - Problem deploying JBPM4.0.0.Beta2 on JBOSS 5.0.1.GA

by dabster2000

I trying to deploy a jbpm example on a clean and newly downloaded JBoss 5.0.1.GA but are having classloader problems. My goal is to create an enterprise project which can be deployed on servers other than JBoss - which is why I'm not interested in installing JBPM on the JBoss server and why I'm not interested in deploying jbpm-archives. I've made an EAR file containing a WAR which again are referencing an utility jar. My JBPM flows are located in the utility jar. My utility jar includes the following jar libraries: jbpm.jar livetribe-jsr223.jar jaxb-impl.jar stax.jar When I invoke my workflow using the following: System.out.println("Starting process engine!"); ProcessEngine processEngine = new Configuration().buildProcessEngine(); RepositoryService repositoryService = processEngine.getRepositoryService(); repositoryService.createDeployment().addResourceFromClasspath("mytestflow.jpdl.xml").deploy(); ExecutionService executionService = processEngine.getExecutionService(); executionService.startProcessInstanceByKey("myInstance1"); return "Service ended!"; I get the following error and I have no clue as to what is going on and any help will be highly appreciated :) 12:08:54,339 INFO [STDOUT] Starting process engine! 12:08:54,734 INFO [Environment] Hibernate 3.3.1.GA 12:08:54,744 INFO [Environment] hibernate.properties not found 12:08:54,747 INFO [Environment] Bytecode provider name : javassist 12:08:54,753 INFO [Environment] using JDK 1.4 java.sql.Timestamp handling 12:08:55,600 INFO [Configuration] configuring from resource: jbpm.hibernate.cfg.xml 12:08:55,600 INFO [Configuration] Configuration resource: jbpm.hibernate.cfg.xml 12:08:55,611 INFO [Configuration] Reading mappings from resource : jbpm.repository.hbm.xml 12:08:55,710 INFO [HbmBinder] Mapping class: org.jbpm.pvm.internal.repository.DeploymentImpl -> JBPM_DEPLOYMENT 12:08:55,754 INFO [HbmBinder] Mapping class: org.jbpm.pvm.internal.repository.DeploymentProperty -> JBPM_DEPLOYPROP 12:08:55,791 INFO [Configuration] Reading mappings from resource : jbpm.execution.hbm.xml 12:08:55,863 INFO [HbmBinder] Mapping class: org.jbpm.pvm.internal.model.ExecutionImpl -> JBPM_EXECUTION 12:08:55,905 INFO [HbmBinder] Mapping class: org.jbpm.pvm.internal.model.CommentImpl -> JBPM_COMMENT 12:08:55,906 INFO [HbmBinder] Mapping class: org.jbpm.pvm.internal.type.Variable -> JBPM_VARIABLE 12:08:55,961 INFO [HbmBinder] Mapping subclass: org.jbpm.pvm.internal.type.variable.DateVariable -> JBPM_VARIABLE 12:08:55,961 INFO [HbmBinder] Mapping subclass: org.jbpm.pvm.internal.type.variable.DoubleVariable -> JBPM_VARIABLE 12:08:55,962 INFO [HbmBinder] Mapping subclass: org.jbpm.pvm.internal.type.variable.HibernateLongVariable -> JBPM_VARIABLE 12:08:55,962 INFO [HbmBinder] Mapping subclass: org.jbpm.pvm.internal.type.variable.LongVariable -> JBPM_VARIABLE 12:08:55,962 INFO [HbmBinder] Mapping subclass: org.jbpm.pvm.internal.type.variable.HibernateStringVariable -> JBPM_VARIABLE 12:08:55,962 INFO [HbmBinder] Mapping subclass: org.jbpm.pvm.internal.type.variable.StringVariable -> JBPM_VARIABLE 12:08:55,963 INFO [HbmBinder] Mapping subclass: org.jbpm.pvm.internal.type.variable.NullVariable -> JBPM_VARIABLE 12:08:55,963 INFO [HbmBinder] Mapping subclass: org.jbpm.pvm.internal.type.variable.BlobVariable -> JBPM_VARIABLE 12:08:55,963 INFO [HbmBinder] Mapping subclass: org.jbpm.pvm.internal.type.variable.ClobVariable -> JBPM_VARIABLE 12:08:55,964 INFO [HbmBinder] Mapping class: org.jbpm.pvm.internal.lob.Lob -> JBPM_LOB 12:08:55,972 INFO [HbmBinder] Mapping class: org.jbpm.pvm.internal.job.JobImpl -> JBPM_JOB 12:08:55,975 INFO [HbmBinder] Mapping subclass: org.jbpm.pvm.internal.job.MessageImpl -> JBPM_JOB 12:08:55,975 INFO [HbmBinder] Mapping subclass: org.jbpm.pvm.internal.model.op.ExecuteActivityMessage -> JBPM_JOB 12:08:55,976 INFO [HbmBinder] Mapping subclass: org.jbpm.pvm.internal.model.op.SignalMessage -> JBPM_JOB 12:08:55,978 INFO [HbmBinder] Mapping subclass: org.jbpm.pvm.internal.model.op.TakeTransitionMessage -> JBPM_JOB 12:08:55,978 INFO [HbmBinder] Mapping subclass: org.jbpm.pvm.internal.model.op.ProceedToDestinationMessage -> JBPM_JOB 12:08:55,978 INFO [HbmBinder] Mapping subclass: org.jbpm.pvm.internal.job.CommandMessage -> JBPM_JOB 12:08:55,978 INFO [HbmBinder] Mapping subclass: org.jbpm.pvm.internal.job.TimerImpl -> JBPM_JOB 12:08:55,981 INFO [Configuration] Reading mappings from resource : jbpm.history.hbm.xml 12:08:56,006 INFO [HbmBinder] Mapping class: org.jbpm.pvm.internal.history.model.HistoryProcessInstanceImpl -> JBPM_HIST_PROCINST 12:08:56,013 INFO [HbmBinder] Mapping class: org.jbpm.pvm.internal.history.model.HistoryActivityInstanceImpl -> JBPM_HIST_ACTINST 12:08:56,016 INFO [HbmBinder] Mapping subclass: org.jbpm.pvm.internal.history.model.HistoryAutomaticInstanceImpl -> JBPM_HIST_ACTINST 12:08:56,016 INFO [HbmBinder] Mapping subclass: org.jbpm.pvm.internal.history.model.HistoryDecisionInstanceImpl -> JBPM_HIST_ACTINST 12:08:56,017 INFO [HbmBinder] Mapping subclass: org.jbpm.pvm.internal.history.model.HistoryTaskInstanceImpl -> JBPM_HIST_ACTINST 12:08:56,018 INFO [Configuration] Reading mappings from resource : jbpm.task.hbm.xml 12:08:56,044 INFO [HbmBinder] Mapping class: org.jbpm.pvm.internal.task.TaskImpl -> JBPM_TASK 12:08:56,058 INFO [HbmBinder] Mapping class: org.jbpm.pvm.internal.task.ParticipationImpl -> JBPM_PARTICIPATION 12:08:56,059 INFO [HbmBinder] Mapping class: org.jbpm.pvm.internal.task.SwimlaneImpl -> JBPM_SWIMLANE 12:08:56,061 INFO [Configuration] Reading mappings from resource : jbpm.jpdl.hbm.xml 12:08:56,089 INFO [HbmBinder] Mapping subclass: org.jbpm.jpdl.internal.model.JpdlExecution -> JBPM_EXECUTION 12:08:56,089 INFO [Configuration] Reading mappings from resource : jbpm.identity.hbm.xml 12:08:56,123 INFO [HbmBinder] Mapping class: org.jbpm.pvm.internal.identity.impl.UserImpl -> JBPM_ID_USER 12:08:56,127 INFO [HbmBinder] Mapping class: org.jbpm.pvm.internal.identity.impl.MembershipImpl -> JBPM_ID_MEMBERSHIP 12:08:56,134 INFO [HbmBinder] Mapping class: org.jbpm.pvm.internal.identity.impl.GroupImpl -> JBPM_ID_GROUP 12:08:56,136 INFO [Configuration] Configured SessionFactory: null 12:08:56,138 INFO [HbmBinder] Mapping collection: org.jbpm.pvm.internal.repository.DeploymentImpl.resources -> JBPM_LOB 12:08:56,139 INFO [HbmBinder] Mapping collection: org.jbpm.pvm.internal.repository.DeploymentImpl.objectProperties -> JBPM_DEPLOYPROP 12:08:56,141 INFO [HbmBinder] Mapping collection: org.jbpm.pvm.internal.model.ExecutionImpl.variables -> JBPM_VARIABLE 12:08:56,141 INFO [HbmBinder] Mapping collection: org.jbpm.pvm.internal.model.ExecutionImpl.timers -> JBPM_JOB 12:08:56,141 INFO [HbmBinder] Mapping collection: org.jbpm.pvm.internal.model.ExecutionImpl.executions -> JBPM_EXECUTION 12:08:56,141 INFO [HbmBinder] Mapping collection: org.jbpm.pvm.internal.model.CommentImpl.comments -> JBPM_COMMENT 12:08:56,142 INFO [HbmBinder] Mapping collection: org.jbpm.pvm.internal.history.model.HistoryProcessInstanceImpl.historyActivityInstances -> JBPM_HIST_ACTINST 12:08:56,142 INFO [HbmBinder] Mapping collection: org.jbpm.pvm.internal.task.TaskImpl.participations -> JBPM_PARTICIPATION 12:08:56,142 INFO [HbmBinder] Mapping collection: org.jbpm.pvm.internal.task.TaskImpl.comments -> JBPM_COMMENT 12:08:56,143 INFO [HbmBinder] Mapping collection: org.jbpm.pvm.internal.task.TaskImpl.subTasks -> JBPM_TASK 12:08:56,143 INFO [HbmBinder] Mapping collection: org.jbpm.pvm.internal.task.SwimlaneImpl.participations -> JBPM_PARTICIPATION 12:08:56,143 INFO [HbmBinder] Mapping collection: org.jbpm.jpdl.internal.model.JpdlExecution.swimlanes -> JBPM_SWIMLANE 12:08:56,201 INFO [DriverManagerConnectionProvider] Using Hibernate built-in connection pool (not for production use!) 12:08:56,201 INFO [DriverManagerConnectionProvider] Hibernate connection pool size: 20 12:08:56,201 INFO [DriverManagerConnectionProvider] autocommit mode: false 12:08:56,201 INFO [DriverManagerConnectionProvider] using driver: org.hsqldb.jdbcDriver at URL: jdbc:hsqldb:mem:. 12:08:56,202 INFO [DriverManagerConnectionProvider] connection properties: {user=sa, password=} 12:08:56,246 INFO [SettingsFactory] RDBMS: HSQL Database Engine, version: 1.8.0 12:08:56,246 INFO [SettingsFactory] JDBC driver: HSQL Database Engine Driver, version: 1.8.0 12:08:56,286 INFO [Dialect] Using dialect: org.hibernate.dialect.HSQLDialect 12:08:56,316 INFO [TransactionFactoryFactory] Using default transaction strategy (direct JDBC transactions) 12:08:56,321 INFO [TransactionManagerLookupFactory] No TransactionManagerLookup configured (in JTA environment, use of read-write or transactional second-level cache is not recommended) 12:08:56,321 INFO [SettingsFactory] Automatic flush during beforeCompletion(): disabled 12:08:56,321 INFO [SettingsFactory] Automatic session close at end of transaction: disabled 12:08:56,322 INFO [SettingsFactory] JDBC batch size: 15 12:08:56,322 INFO [SettingsFactory] JDBC batch updates for versioned data: disabled 12:08:56,325 INFO [SettingsFactory] Scrollable result sets: enabled 12:08:56,326 INFO [SettingsFactory] JDBC3 getGeneratedKeys(): disabled 12:08:56,326 INFO [SettingsFactory] Connection release mode: auto 12:08:56,344 INFO [SettingsFactory] Default batch fetch size: 1 12:08:56,344 INFO [SettingsFactory] Generate SQL with comments: disabled 12:08:56,345 INFO [SettingsFactory] Order SQL updates by primary key: disabled 12:08:56,345 INFO [SettingsFactory] Order SQL inserts for batching: disabled 12:08:56,345 INFO [SettingsFactory] Query translator: org.hibernate.hql.ast.ASTQueryTranslatorFactory 12:08:56,350 INFO [ASTQueryTranslatorFactory] Using ASTQueryTranslatorFactory 12:08:56,350 INFO [SettingsFactory] Query language substitutions: {} 12:08:56,350 INFO [SettingsFactory] JPA-QL strict compliance: disabled 12:08:56,350 INFO [SettingsFactory] Second-level cache: enabled 12:08:56,350 INFO [SettingsFactory] Query cache: disabled 12:08:56,350 INFO [SettingsFactory] Cache region factory : org.hibernate.cache.impl.NoCachingRegionFactory 12:08:56,351 INFO [SettingsFactory] Optimize cache for minimal puts: disabled 12:08:56,351 INFO [SettingsFactory] Structured second-level cache entries: disabled 12:08:56,360 INFO [SettingsFactory] Statistics: disabled 12:08:56,360 INFO [SettingsFactory] Deleted entity synthetic identifier rollback: disabled 12:08:56,361 INFO [SettingsFactory] Default entity-mode: pojo 12:08:56,361 INFO [SettingsFactory] Named query checking : enabled 12:08:56,449 INFO [SessionFactoryImpl] building session factory 12:08:57,562 INFO [SessionFactoryObjectFactory] Not binding factory to JNDI, no JNDI name configured 12:08:57,607 INFO [SchemaExport] Running hbm2ddl schema export 12:08:57,631 INFO [SchemaExport] exporting generated schema to database 12:08:57,663 INFO [SchemaExport] schema export complete 12:08:59,468 ERROR [[spring-ws]] Servlet.service() for servlet spring-ws threw exception java.lang.ClassCastException: org.jbpm.jpdl.internal.activity.ExclusiveBinding at org.jbpm.jpdl.internal.xml.BindingsParser.instantiateBinding(BindingsParser.java:62) at org.jbpm.jpdl.internal.xml.BindingsParser.parseDocumentElement(BindingsParser.java:47) at org.jbpm.pvm.internal.xml.Parser.parseDocument(Parser.java:475) at org.jbpm.pvm.internal.xml.Parser.execute(Parser.java:394) at org.jbpm.pvm.internal.xml.Parse.execute(Parse.java:157) at org.jbpm.jpdl.internal.xml.JpdlParser.parseBindings(JpdlParser.java:110) at org.jbpm.jpdl.internal.xml.JpdlParser.(JpdlParser.java:93) at org.jbpm.jpdl.internal.repository.JpdlDeployer.(JpdlDeployer.java:51) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:494) at org.jbpm.pvm.internal.wire.descriptor.ObjectDescriptor.construct(ObjectDescriptor.java:151) at org.jbpm.pvm.internal.wire.WireContext.construct(WireContext.java:473) at org.jbpm.pvm.internal.wire.WireContext.create(WireContext.java:452) at org.jbpm.pvm.internal.wire.descriptor.CollectionDescriptor.initialize(CollectionDescriptor.java:72) at org.jbpm.pvm.internal.wire.WireContext.performInitialization(WireContext.java:537) at org.jbpm.pvm.internal.wire.WireContext.processPendingInitializations(WireContext.java:568) at org.jbpm.pvm.internal.wire.WireContext.create(WireContext.java:454) at org.jbpm.pvm.internal.wire.operation.FieldOperation.apply(FieldOperation.java:43) at org.jbpm.pvm.internal.wire.descriptor.ObjectDescriptor.initialize(ObjectDescriptor.java:220) at org.jbpm.pvm.internal.wire.WireContext.performInitialization(WireContext.java:537) at org.jbpm.pvm.internal.wire.WireContext.initialize(WireContext.java:499) at org.jbpm.pvm.internal.wire.WireContext.create(WireContext.java:453) at org.jbpm.pvm.internal.wire.WireContext.create(WireContext.java:441) at org.jbpm.pvm.internal.wire.WireContext.get(WireContext.java:421) at org.jbpm.pvm.internal.wire.WireContext.get(WireContext.java:331) at org.jbpm.pvm.internal.wire.WireContext.get(WireContext.java:707) at org.jbpm.pvm.internal.env.BasicEnvironment.get(BasicEnvironment.java:148) at org.jbpm.pvm.internal.env.BasicEnvironment.get(BasicEnvironment.java:139) at org.jbpm.pvm.internal.wire.descriptor.ObjectDescriptor.autoWire(ObjectDescriptor.java:294) at org.jbpm.pvm.internal.wire.descriptor.ObjectDescriptor.initialize(ObjectDescriptor.java:216) at org.jbpm.pvm.internal.wire.WireContext.performInitialization(WireContext.java:537) at org.jbpm.pvm.internal.wire.WireContext.initialize(WireContext.java:499) at org.jbpm.pvm.internal.wire.WireContext.create(WireContext.java:453) at org.jbpm.pvm.internal.wire.WireContext.create(WireContext.java:441) at org.jbpm.pvm.internal.wire.WireContext.get(WireContext.java:421) at org.jbpm.pvm.internal.wire.WireContext.get(WireContext.java:331) at org.jbpm.pvm.internal.wire.WireContext.get(WireContext.java:707) at org.jbpm.pvm.internal.env.BasicEnvironment.get(BasicEnvironment.java:148) at org.jbpm.pvm.internal.env.BasicEnvironment.get(BasicEnvironment.java:139) at org.jbpm.pvm.internal.cmd.DeployCmd.execute(DeployCmd.java:46) at org.jbpm.pvm.internal.cmd.DeployCmd.execute(DeployCmd.java:33) at org.jbpm.pvm.internal.svc.DefaultCommandService.execute(DefaultCommandService.java:42) at org.jbpm.pvm.internal.tx.StandardTransactionInterceptor.execute(StandardTransactionInterceptor.java:54) at org.jbpm.pvm.internal.svc.EnvironmentInterceptor.execute(EnvironmentInterceptor.java:54) at org.jbpm.pvm.internal.svc.RetryInterceptor.execute(RetryInterceptor.java:55) at org.jbpm.pvm.internal.repository.DeploymentImpl.deploy(DeploymentImpl.java:81) at com.testapp.MyService.invokeWorkflow(MyService.java:14) at dk.testapp.MyWebService.invokeInternal(MyWebService.java:14) at org.springframework.ws.server.endpoint.AbstractJDomPayloadEndpoint.invoke(AbstractJDomPayloadEndpoint.java:59) at org.springframework.ws.server.endpoint.adapter.PayloadEndpointAdapter.invoke(PayloadEndpointAdapter.java:48) at org.springframework.ws.server.MessageDispatcher.dispatch(MessageDispatcher.java:221) at org.springframework.ws.server.MessageDispatcher.receive(MessageDispatcher.java:168) at org.springframework.ws.transport.support.WebServiceMessageReceiverObjectSupport.handleConnection(WebServiceMessageReceiverObjectSupport.java:88) at org.springframework.ws.transport.http.WebServiceMessageReceiverHandlerAdapter.handle(WebServiceMessageReceiverHandlerAdapter.java:57) at org.springframework.ws.transport.http.MessageDispatcherServlet.doService(MessageDispatcherServlet.java:230) at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:571) at org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:511) at javax.servlet.http.HttpServlet.service(HttpServlet.java:637) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92) at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126) at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:601) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:613) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4235254#4235254 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4235254

14 years, 12 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: I submit to our Maven overlords

by ataylor

I actually don't mind maven when it comes to thirdparty dependencies. You have finer grained control over what you want. i.e., with buildmagic if someone wants to use JBM all the jars are downloaded when maybe they only want the client jars. Also its download only once for every project which i like. Also theres nothing to stop us using ant to build and call maven just for the dependencies, thats what the AS build does. +1 with jbm 2 only. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4235222#4235222 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4235222

14 years, 12 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: I submit to our Maven overlords

by timfox

"gaohoward" wrote : | Probably I know maven not so much so my opinion is not fair for maven. But unless maven becomes mandate in the projects I'm working on, I'll stick to ant as long as possible. | | +1 I think for the JBM 1.x work we should stick with ant, but just move to Maven for the new 2.0 stuff. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4235210#4235210 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4235210

14 years, 12 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums June 2009