[Design of JBoss Portal] - Re: Setting content type for the whole portal : ContentTypeI
by thanvi
Hi
It's a very interting forum. I am tryign to set the content type to mulitpart/form-data.
I did the changes in the xml file as mentiond by Shaun.
But i got the following exception
15:53:41,991 ERROR [ObjectModelBuilder] Failed to invoke method public java.lang.Object org.jboss.portal.theme.deployment.jboss.LayoutStategyMetaDataFactory.newChild(java.util.ArrayList,org.jboss.xb.binding.UnmarshallingContext,java.lang.String,java.lang.String,org.xml.sax.Attributes) throws javax.activation.MimeTypeParseException, factory=org.jboss.portal.theme.deployment.jboss.LayoutStategyMetaDataFactory@4b0cbc
| javax.activation.MimeTypeParseException: Type [multipart/form-data] not supported
| at org.jboss.portal.common.MediaType.parseMimeType(MediaType.java:214)
| at org.jboss.portal.theme.deployment.jboss.LayoutStategyMetaDataFactory.newChild(LayoutStategyMetaDataFactory.java:63)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.xb.binding.ObjectModelBuilder.invokeFactory(ObjectModelBuilder.java:435)
| at org.jboss.xb.binding.DelegatingObjectModelFactory.newChild(DelegatingObjectModelFactory.java:93)
| at org.jboss.xb.binding.ObjectModelBuilder.startElement(ObjectModelBuilder.java:337)
| at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:299)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4003229#4003229
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4003229
19 years, 2 months
[Design of JBoss jBPM] - Re: Can't deploy processdefinition from GPD into jBPM 3.2 -
by tom.baeyens@jboss.com
>From the hibernate docs:
anonymous wrote : 3.8.3. Current Session context management with JTA
|
| The easiest way to handle Sessions and transactions is Hibernates automatic "current" Session management. See the discussion of Section 2.5, ?Contextual Sessions?. Using the "jta" session context, if there is no Hibernate Session associated with the current JTA transaction, one will be started and associated with that JTA transaction the first time you call sessionFactory.getCurrentSession(). The Sessions retrieved via getCurrentSession() in "jta" context will be set to automatically flush before the transaction completes, close after the transaction completes, and aggressively release JDBC connections after each statement. This allows the Sessions to be managed by the lifecycle of the JTA transaction to which it is associated, keeping user code clean of such management concerns. Your code can either use JTA programmatically through UserTransaction, or (recommended for portable code) use the Hibernate Transaction API to set transaction boundaries. If you run in an EJB container, declarative transaction demarcation with CMT is preferred.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4003170#4003170
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4003170
19 years, 2 months
[Design of JBoss jBPM] - Re: Can't deploy processdefinition from GPD into jBPM 3.2 -
by tom.baeyens@jboss.com
in the enterprise.ear, the configurations are packaged in a separate jar file called jbpm-configs.jar
these are the relevant properties in the hibernate.cfg.xml
<property name="hibernate.dialect">org.hibernate.dialect.HSQLDialect</property>
| <property name="hibernate.cache.provider_class">org.hibernate.cache.HashtableCacheProvider</property>
| <property name="hibernate.transaction.manager_lookup_class">org.hibernate.transaction.JBossTransactionManagerLookup</property>
| <property name="hibernate.connection.datasource">java:/JbpmDS</property>
| <property name="hibernate.transaction.factory_class">org.hibernate.transaction.CMTTransactionFactory</property>
| <property name="hibernate.transaction.manager_lookup_class">org.hibernate.transaction.JBossTransactionManagerLookup</property>
|
and this is the jbpm.cfg.xml part of the persistence/tx configs
<service name="persistence">
| <factory>
| <bean class="org.jbpm.persistence.db.DbPersistenceServiceFactory">
| <field name="isCurrentSessionEnabled">
| <true />
| </field>
| <field name="isTransactionEnabled">
| <false />
| </field>
| </bean>
| </factory>
| </service>
|
if you change to JTA, you might need to set the isTransactionEnabled property to true. i don't know these configs at all. i'll check the docs and get back if i find anything there.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4003167#4003167
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4003167
19 years, 2 months
[Design of JBoss jBPM] - Re: new build script updates committed
by tom.baeyens@jboss.com
updates:
* now you don't have to run the get dependencies separate any more. if your build needs the libraries, it will check if they are up to date. if not the build/build.xml is called with one of the targets get.libs.dependencies, get.jboss.dependencies or get.eclipse.dependencies.
* the version.properties files have been removed. instead, the build/build.properties contains the version properties.
* some targets were moved from the project.base.build.xml to the project specific build file. like package, jpdl, create.manifest and all those. the original mechanism was too complex and not realizing a lot of reuse. there seem to be always little differences between the same targets in different subprojects. the old targets in the project.base.build.xml are still on top of that file in comments in case you want to have a look.
next i'm going to try to easy release tasks such as uploading to sf.net, uploading the docs and publishing jbpm artifacts to the remote repository.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4003164#4003164
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4003164
19 years, 2 months