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

[Deployers on JBoss (Deployers/JBoss)] - Re: Is META-INF in the classpath?

by adrian＠jboss.org

"adrian(a)jboss.org" wrote : This looks like a problem with the new SARDeployer. | Well actually the problem is in the JAXPDeployer that it uses. Ironically, it is setting up an InputSource with the URI but then not using it :-) | | InputStream is = openStreamAndValidate(file); | try | { | DocumentBuilder parser = getDocumentBuilderFactory().newDocumentBuilder(); | InputSource source = new InputSource(is); | source.setSystemId(file.toURI().toString()); | parser.setEntityResolver(new JBossEntityResolver()); | | // HERE it passes the stream instead of the source :-) | return parser.parse(is); | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4154430#4154430 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4154430

16 years, 8 months

1
0
0 / 0

[Deployers on JBoss (Deployers/JBoss)] - Re: Is META-INF in the classpath?

by adrian＠jboss.org

"adrian(a)jboss.org" wrote : This looks like a problem with the new SARDeployer. | Well actually the problem is in the JAXPDeployer that it uses. Ironically, it is setting up an InputSource with the URI but then not using it :-) | | InputStream is = openStreamAndValidate(file); | try | { | DocumentBuilder parser = getDocumentBuilderFactory().newDocumentBuilder(); | InputSource source = new InputSource(is); | source.setSystemId(file.toURI().toString()); | parser.setEntityResolver(new JBossEntityResolver()); | | // HERE it passes the stream instead of the source :-) | return parser.parse(is); | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4154429#4154429 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4154429

16 years, 8 months

1
0
0 / 0

[Design of EJB 3.0] - Re: Maven Version Resolution Differences 2.0.8 / 2.0.9

by pgier

"ALRubinger" wrote : "pgier" wrote : Are you using the import scope in ejb3? I'm not sure how maven 2.0.8 would handle import scope, either an error or unpredictable behaviour I would guess. | | Yeah, we're not using "import" scope in EJB3. | | So I'm still at a loss as to what's up with this issue. | | I suppose in the meantime we should introduce a fail-fast by requiring Maven 2.0.9 in the Enforcer Configuration for EJB3 Core. | | S, | ALR Does the tree work ok without the "includes" parameter? That's really weird behaviour and looks like a bug. Something in the dependency resolution must have changed in 2.0.9 that messed up the dependency plugin. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4154428#4154428 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4154428

16 years, 8 months

1
0
0 / 0

[Design of JBoss ESB] - Re: A problem about soapAction and wsdl in JBossESB

by Kevin.Conner＠jboss.com

Can you send me your WSDL file? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4154427#4154427 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4154427

16 years, 8 months

1
0
0 / 0

[Deployers on JBoss (Deployers/JBoss)] - Re: Is META-INF in the classpath?

by adrian＠jboss.org

"scott.stark(a)jboss.org" wrote : No, not generally. If its needed you would have to use a META-INF/jboss-structure.xml to instruct the structure deployers to add it. You then have to specify the complete classpath though. Don't know if the latest classloading deployers have a simpler syntax for this. | This doesn't use classloading. It is xml parsing. ;-) We need to tell the parser what the system uri is so it can do relative uri handling. I guess there will be a similar problem for the more modern XInclude handling? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4154426#4154426 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4154426

16 years, 8 months

1
0
0 / 0

[Deployers on JBoss (Deployers/JBoss)] - Re: Is META-INF in the classpath?

by adrian＠jboss.org

This looks like a problem with the new SARDeployer. | protected ServiceDeployment parse(VFSDeploymentUnit unit, VirtualFile file, Document document) throws Exception | { | ServiceDeploymentParser parser = new ServiceDeploymentParser(document); | ServiceDeployment parsed = parser.parse(); | The location of the xml document (file.toURL()) is not being passed to the JAXP parser used by ServiceDeploymentParser, so it wil resolve it relative to the current directory (which is the bin folder normally with JBoss). But I think this will be true of a lot of the other parsing deployers that now use JBossXB. In general we are passing streams instead of URLs, e.g. JBossXBDeployerHelper | InputStream is = openStreamAndValidate(file); | Object parsed = null; | try | { | // HERE Doesn't know the file url | parsed = unmarshaller.unmarshal(is, resolver); | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4154425#4154425 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4154425

16 years, 8 months

1
0
0 / 0

[Design of EJB 3.0] - Re: Maven Version Resolution Differences 2.0.8 / 2.0.9

by ALRubinger

"pgier" wrote : Are you using the import scope in ejb3? I'm not sure how maven 2.0.8 would handle import scope, either an error or unpredictable behaviour I would guess. Yeah, we're not using "import" scope in EJB3. So I'm still at a loss as to what's up with this issue. I suppose in the meantime we should introduce a fail-fast by requiring Maven 2.0.9 in the Enforcer Configuration for EJB3 Core. S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4154422#4154422 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4154422

16 years, 8 months

1
0
0 / 0

[Design of POJO Server] - Re: Integrating aop-mc-int bean metadata with AS5

by adrian＠jboss.org

"kabir.khan(a)jboss.com" wrote : Because the beans that push the things into the aspectmanager are not deployed until the BeanMetaDataDeployer picks them up in the REAL stage. | | Are you suggesting that as part of my POST_CLASSLOADER deployer rip out the aop beanmetadatafactories from the deployment, and deploy them myself there? That could work, they are easily identifiable, but I didn't want to mess around with the deployment too much. You at least need to push the point-cut definitions into the AspectManager during POST_CLASSLOADER so you know which classes need weaving and where. The aspects themselves won't become usable until the dependencies are satisifed (i.e. dependencies get injected onto them during the REAL stage) but then nobody should be trying to use the objects until this is done (they should just be analysing the classes). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4154420#4154420 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4154420

16 years, 8 months

1
0
0 / 0

[Deployers on JBoss (Deployers/JBoss)] - Re: Is META-INF in the classpath?

by scott.stark＠jboss.org

16 years, 8 months

1
0
0 / 0

[Design of POJO Server] - Re: profile service, farming

by scott.stark＠jboss.org

It sounds correct to make the cluster aware feature be an implementation detail that requires injection of the clustering function into the profile impl/profile repository impl. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4154415#4154415 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4154415

16 years, 8 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums May 2008