[Design of POJO Server] - Re: tomcat deployer porting
by scott.stark@jboss.org
Data like this:
| protected EncMap encInjectors = new EncMap();
| protected Map<String, Map<AccessibleObject, Injector>> encInjections = new HashMap<String, Map<AccessibleObject, Injector>>();
| protected Map<String, Map<AccessibleObject, Injector>> resolvedClassInjections = new HashMap<String, Map<AccessibleObject, Injector>>();
|
|
| protected List<PersistenceUnitDeployment> persistenceUnitDeployments = new ArrayList<PersistenceUnitDeployment>();
| protected LinkedHashMap ejbContainers = new LinkedHashMap(); // will always be empty.
| protected DeploymentPersistenceUnitResolver persistenceUnitResolver;
| protected WarEjbResolver ejbResolver;
| protected DependencyPolicy dependencyPolicy = new JmxDependencyPolicy();
| protected Collection<InjectionHandler> handlers;
| protected DeploymentInfo di;
| protected ClassLoader webLoader;
| protected AbstractWebContainer.WebDescriptorParser parser;
| protected WebApplication appInfo;
|
should be in the DeploymentUnit attachments for use by other deployers, and some probably set by other deployers:
| protected WebMetaData parse(DeploymentUnit unit, VirtualFile file)
| throws Exception
| {
| Collection<InjectionHandler> handlers = unit.getAttachment("handlers");
| WarEjbResolver ejbResolver = unit.getAttachment(WarEjbResolver.class);
| ...
|
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3975025#3975025
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3975025
18 years, 3 months
[Design of JBoss jBPM] - Re: 3.2 alpha 1 release status
by tom.baeyens@jboss.com
"david.lloyd(a)jboss.com" wrote : "falazar" wrote : It seems like a couple of these tables may not be normalized very well either.
| I'm with you there, but from talking to Tom I don't think we can expect this to change in the 3.x series, since we're going to avoid any sweeping database changes, especially those that would introduce compatibility problems... Tom, correct me if I'm wrong.
3.1, 3.2, 3.3, ... can have changing database schemas. it's for micro release numbers that jbpm db schema should be stable (e.g. between 3.1.2 and 3.1.3).
but id didn't yet get completely the problem that falazar is experiencing. falazar, can you try explaining again what you did, what jbpm behaviour was and what behaviour you expected.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3974990#3974990
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3974990
18 years, 3 months