]
Pete Muir moved JBAS-5561 to JBSEAM-3050:
-----------------------------------------
Project: Seam (was: JBoss Application Server)
Key: JBSEAM-3050 (was: JBAS-5561)
Fix Version/s: 2.0.x
2.1.0.BETA1
(was: JBossAS-5.1.0.CR1)
Move Seam scanner code into AS
------------------------------
Key: JBSEAM-3050
URL:
http://jira.jboss.com/jira/browse/JBSEAM-3050
Project: Seam
Issue Type: Task
Components: Platform interoperability
Reporter: Stan Silvert
Assigned To: Pete Muir
Fix For: 2.0.x, 2.1.0.BETA1
We need to move the Seam scanner code that Ales wrote into AS5 so that you don't have
to deploy jboss-seam-jbas5.jar in your Seam project.
Discussion thus far:
ALES:
How are you planning on solving the classloading issue there?
e.g.
if the custom Seam/AS5 scanning code is in AS5, but still references some Seam code,
which is deployed as part of Seam app
PETE:
Hmm, we discussed splitting out the Scanner interface into an SPI, but I'm not sure
that is a great idea as it will result in a proliferation of jars and confusion.
ALES:
I'm always in favor of this.
More jars or not, having proper spi is always better then some tight integration.
But then this means that people have to either
- put this spi + plugins into some top level CL space
- include it with every Seam app
Which doesn't sound that bad - since all deployments should be automatic anyway (ant,
maven2, ...).
PETE:
Any other ideas? We could merge this into seam core and select the scanner as needed...
ALES:
OK, this simplifies things.
You do this via reflection - catching the first one that works.
It's the criteria of what we need that it's the problem.
At least I remember we had some issues determining weather we're running in AS5 or
Embedded.
But yeah, we can give it another shot.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: