[Design of JBoss jBPM] - Re: build error
by msandoz
i download the files with cvs so that should be ok. i then ran the build under jbpm.3/designer/jpdl/org.jbpm.gd.jpdl.build as you mentioned and thats how i got the error. here are my personal build props:
| jboss.home=C:/jboss-4.0.5.GA
| eclipse.home=C:/software/eclipse
| eclipse.dir=C:/software/eclipse
| local.repository=c:/Users/msandoz/jbpm/repository
| remote.repository=http://repository.jboss.com
| docbook.support.dir=${local.repository}
| windows.browser=C:/Program Files/Internet Explorer/IEXPLORE.EXE
| macos.browser=/usr/bin/open
| linux.browser=firefox
|
also when i tried to run the project in eclipse the Jbpm3DevelopDesignerInEclipse wiki page directed me to check out the jbpm.3/designer/jpdl/org.jbpm.gd.jpdl.ui project which had of course lots of reference errors. should open a jira ticket for a change to the wiki page?
i have now opened the project you suggested and it is running smoothly. i think i'll take a break from the build for a bit while i play with the editor :)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4053960#4053960
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4053960
19 years
[QA of JBoss Portal] - Re: JSFUnit and Portlets
by julien＠jboss.com
JBoss Portal management apps get their services from the servlet context attributes. They are injected in the application via JSF wiring capabilities.
| <managed-bean>
| <managed-bean-name>portalobjectmgr</managed-bean-name>
| <managed-bean-class>org.jboss.portal.core.admin.ui.PortalObjectManagerBean</managed-bean-class>
| <managed-bean-scope>session</managed-bean-scope>
| <managed-property>
| <property-name>roleModule</property-name>
| <value>#{applicationScope.RoleModule}</value>
| </managed-property>
| <managed-property>
| <property-name>portalObjectContainer</property-name>
| <value>#{applicationScope.PortalObjectContainer}</value>
| </managed-property>
| <managed-property>
| <property-name>instanceContainer</property-name>
| <value>#{applicationScope.InstanceContainer}</value>
| </managed-property>
| <managed-property>
| <property-name>layoutService</property-name>
| <value>#{applicationScope.LayoutService}</value>
| </managed-property>
| <managed-property>
| <property-name>themeService</property-name>
| <value>#{applicationScope.ThemeService}</value>
| </managed-property>
| <managed-property>
| <property-name>domainConfigurator</property-name>
| <value>#{applicationScope.AuthorizationDomainRegistry.portalobject.configurator}</value>
| </managed-property>
| </managed-bean>
|
In that example we can see the the portalobjectmgr bean requires the injection of several services. Those services are injected by the portal at runtime.
So testing our apps requires those services to be present as well. Most of those services are POJOs which can be wired using microcontainer.
The microcontainer would be bootstrapped as a servlet context listener and it is possible to make the servlet context attributes being seen as a bean of the MC, providing thus injection capabilities in the servlet context attributes.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4053938#4053938
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4053938
19 years