February 2008 - jboss-dev-forums - Jboss List Archives

[Design of EJB 3.0] - Re: Removing deployers from core

by ALRubinger

"anil.saldhana(a)jboss.com" wrote : Scott/ALR, what is the final goal here for EJB3? The external project contains ejb3 core and AS workspace contains the ejb3 integration code? Yes. The *final* goal in terms of AS Build is: Build AS Components Build External Components dependent on AS Components (ie. EJB3) Build AS Integration Modules Run AS Build (Assembly) to create distribution S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4133038#4133038 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4133038

16 years, 3 months

1
0
0 / 0

[Design of EJB 3.0] - Re: Removing deployers from core

by anil.saldhana＠jboss.com

Scott/ALR, what is the final goal here for EJB3? The external project contains ejb3 core and AS workspace contains the ejb3 integration code? I have disabled ejb3 jacc layer. I will not venture into ejb3 land for a week. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4133037#4133037 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4133037

16 years, 3 months

1
0
0 / 0

[Design of EJB 3.0] - Re: Removing deployers from core

by ALRubinger

Beat me to the list of dependencies. :) Looks like I can start to hack away at this once the dependency policy stuff is moved off to MC. Won't worry about the mock deployment for now, those tests may even be moved to ejb3 module in AS. Unless we create some notion of a deployment in EJB3 Core itself for use in embedded/standalone. S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4133035#4133035 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4133035

16 years, 3 months

1
0
0 / 0

[Design of EJB 3.0] - Re: Removing deployers from core

by scott.stark＠jboss.org

The JBoss5DependencyPolicy supply/demands are not useful and are even obsolete in the mc. The dependency should just be on a name, and if we need an abstraction, the mc alias mechanism used. I'm starting to work on the injection stuff, so we'll see how that can be cleaned up. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4133033#4133033 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4133033

16 years, 3 months

1
0
0 / 0

[Design of EJB 3.0] - Re: Removing deployers from core

by scott.stark＠jboss.org

Dependencies preventing this include: - MockEjb3Deployment used by tests - org.jboss.ejb3.Ejb3Deployment references Ejb3Deployer for CacheFactoryRegistry, RemoteProxyFactoryRegistry, PersistenceManagerFactoryRegistry - EJBContainer casts to a specific JBoss5DependencyPolicy for addSupply. The supply/demands needs to be redone anyway. - ClientENCInjectionContainer references JBoss5DependencyPolicy and JBoss5DeploymentUnit - injection classes cast to a JBoss5DependencyPolicy. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4133032#4133032 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4133032

16 years, 3 months

1
0
0 / 0

[Design of EJB 3.0] - Re: Removing deployers from core

by ALRubinger

There are dependencies on the deployers elsewhere in EJB3 Core. Because I cant have Core depend on the deployers in EJB3 Module of AS (would introduce cyclic dependency), need some guidance as to what may be removed, and how the errors might be resolved. S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4133031#4133031 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4133031

16 years, 3 months

1
0
0 / 0

[Design of JBossXB] - Re: How to force strict validation?

by rob.stryker＠jboss.com

Thanks for the replies: Just setting validation and schema validation to true did not accomplish what I needed it to do. I still was unable to access the parser to set the properties needed. I ended up cloning UnmarshallerImpl and making the getParser() method public (rather than package private) to do what I needed it to. | public class ParseTest extends TestCase { | private static final String SCHEMA = "/home/rob/apps/eclipse/workspaces/work/garbage/src/schema.xsd"; | private static final String DATA = "/home/rob/apps/eclipse/workspaces/work/garbage/data/test.xml"; | public void testABC() { | try { | File f = new File(SCHEMA); | InputStream stream = new FileInputStream(f); | SchemaBinding binding = XsdBinder.bind(stream, "UTF-8", (String)null); | stream.close(); | binding.setStrictSchema(true); | UnmarshallerImpl unmarshaller = new UnmarshallerImpl(); | String schemaLocation = new File("/home/rob/apps/eclipse/workspaces/work/garbage/src/schema.xsd").toURI().toURL().toExternalForm(); | unmarshaller.setValidation(true); | unmarshaller.getParser().setFeature("http://apache.org/xml/features/validation/schema", true); | unmarshaller.getParser().setProperty("http://apache.org/xml/properties/schema/external-noNamespaceSchemaLocation", | schemaLocation); | FileInputStream dataStream = new FileInputStream(new File(DATA)); | Object xmlObject = unmarshaller.unmarshal(dataStream, binding); | System.out.println("object is " + xmlObject); | } catch( Exception e ) { | // GOOD! I want XB to fail! | return; | } | fail("data file should not have validated!"); | } | } | Now I'm just looking via APIs to find a similar way to enforce strict validation when writing / marshalling the files as well ;) Again, thanks for the help. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4133030#4133030 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4133030

16 years, 3 months

1
0
0 / 0

[Design of POJO Server] - Re: Seeing incomplete deployment not failing again

by scott.stark＠jboss.org

Yes, that was the problem. This is a 2.1 ejb, so we can't be creating a dependency on the ejb3 container. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4133028#4133028 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4133028

16 years, 3 months

1
0
0 / 0

[Design of JBoss Portal] - Re: Event debugger

by julien＠jboss.com

Here is the EventPhaseSession interface: | public interface EventPhaseSession | { | | /** | * Queue an event for consumption. The queue is a FIFO queue. | * | * @param event an event | * @throws IllegalArgumentException if the event is null | * @throws IllegalStateException if an event cannot be published | */ | void queueEvent(Event event) throws IllegalArgumentException, IllegalStateException; | | /** | * Stop processing of all events and returns from the controller. | * | * @throws IllegalStateException if the session cannot be interrupted. | */ | void interrupt() throws IllegalStateException; | | } | It is usable really only during the routing phase and the event controller context can use it to queue events. the interrupt method is used by the controller context can be used to interrupt the event phase (for instance a portal logout event could do that). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4133025#4133025 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4133025

16 years, 3 months

1
0
0 / 0

[Design of JBoss Portal] - Re: Event debugger

by julien＠jboss.com

here are the relevant methods of the event controller context | /** | * Give control to the context when an event is produced. The session | * argument gives to the context the capability to queue events in response | * of the produced event or to interrupt the session. It has also access | * to the full history of distributed events in order to provide advanced | * implementation of event cycle detection. | * | * During the invocation of this method, any runtime exception thrown will signal | * a failure and the produced event will be discarded although the event | * distribution will continue. | * | * During the invocation of this method, any error thrown will be propagated | * to the portlet controller invoker. | * | * @param session the session | * @param sourceEvent the source event | * @param producedEvent the produced event | */ | void eventProduced(EventPhaseSession session, Event sourceEvent, Event producedEvent); | | /** | * Signal to the context when an event is consumed by a portlet. The session argument | * only provides querying capabilities and it is not possible to queue event | * or interrupt the session. | * | * During the invocation of this method, any runtime exception thrown will | * be ignored by the controller. | * | * During the invocation of this method, any error thrown will be propagated | * to the portlet controller invoker. | * | * @param session the session | * @param sourceEvent the source event | * @param consumedEvent the consumed event | */ | void eventConsumed(EventPhaseSession session, Event sourceEvent, Event consumedEvent); | the first method is used to route an produced event to create events in reaction. the second method is more an acknowledgement method that say that en event was consumed. I plan to add other callbacks for ignored events or failures. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4133024#4133024 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4133024

16 years, 3 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 February 2008