October 2006 - jboss-dev-forums - Jboss List Archives

[Design of JBoss Eclipse IDE (dev)] - Re: Failed to create new jboss debug configuration in Eclips

by ah6511

Thx. After I switched the jboss AS perspective, created a new server (jboss AS 4) and selecting it, but nothing shows up the view pane under server view pane, even though Modules, Event Log, etc are all enabled. Any idea? TIA. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3981130#3981130 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3981130

19 years, 5 months

1
0
0 / 0

[Design of POJO Server] - Re: EARStructure not deploying modules

by scott.stark＠jboss.org

"bill.burke(a)jboss.com" wrote : | What I meant was that a module within the EAR is not getting determineStructure called. I know this for a fact as I'm stepping through... | | Now where to put determineStructure? Within DefaultStructureBuilder? | | BTW, can you please explain what DefaultStructureBuilder is trying to accomplish? Specifically, what is going on with all the Classpath stuff? Specifically, I need to know if the Classpath will only contain the EJB jar and not other jars so that I can scan propertly for annotations. | | thanks Ok. Its up to a given structure deployer to call out to the input deployers (or use the AbstractStructureDeployer.addAllChildren) to recursively process contexts. Right now its a determined type of structure deployer that is only creating child ContextInfos for those modules explicitly listed. They can't have nested deployments. This will have to be changed because the EARStructure does not really know what each type of module is in terms of strucuture. We should be doing an allAllChildren starting with each declared module. The current EARStructure deployer creates a context for the ejb jar, and only includes the jars referenced by the module classpath manifest: | ContextInfoImpl moduleContext = new ContextInfoImpl(module.getPathName()); | metaData.addContext(moduleContext); | // Add the manifest locations | addClassPath(root, module, false, true, moduleContext); | to include the jar the call should be addClassPath(root, module, true, true, moduleContext). The ejb jar should be in its own classpath, while a war should not. DefaultStructureBuilder is a dumb mapping of what the structure deployers specified as the deployment in the StructureMetaData. It should not be doing anything else or else its overriding what the structure deployers indicated. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3981126#3981126 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3981126

19 years, 5 months

1
0
0 / 0

[Design of POJO Server] - Re: EARStructure not deploying modules

by bill.burke＠jboss.com

"scott.stark(a)jboss.org" wrote : That is possible. I would think any difference in vfs paths from those two paths indicates a vfs problem though, not a deployer issue as the paths should be consistent. Not a VFS problem...The VFS path ends up being "" empty string because you are building the VFS based on the URL of the ear because it is being deployed through MainDeployer.deploy(URL) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3981125#3981125 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3981125

19 years, 5 months

1
0
0 / 0

[Design of POJO Server] - Re: EARStructure not deploying modules

by scott.stark＠jboss.org

That is possible. I would think any difference in vfs paths from those two paths indicates a vfs problem though, not a deployer issue as the paths should be consistent. I'm working with the testsuite/output/lib/unpacked-ear1.ear to start with as it tries to deploy just about every type. It needs to be updated to include an ejb3 deployments as well now that the testsuite is java5 based. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3981123#3981123 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3981123

19 years, 5 months

1
0
0 / 0

[Design of POJO Server] - Re: EARStructure not deploying modules

by bill.burke＠jboss.com

"scott.stark(a)jboss.org" wrote : I'm sitting in it now for an ear deployment: | | | | Thread [main] (Suspended (breakpoint at line 102 in EARStructure)) | | EARStructure.determineStructure(VirtualFile, StructureMetaData, StructuredDeployers) line: 102 | | BasicStructuredDeployers.determineStructure(VirtualFile, StructureMetaData) line: 76 | | MainDeployerImpl.determineStructure(DeploymentContext) line: 528 | | MainDeployerImpl.addDeploymentContext(DeploymentContext) line: 271 | | ProfileServiceBootstrap.loadProfile(String) line: 365 | | ProfileServiceBootstrap.bootstrap() line: 246 | | ProfileServiceBootstrap(AbstractBootstrap).run() line: 89 | | ServerImpl.doStart() line: 401 | | ServerImpl.start() line: 340 | | Main.boot(String[]) line: 210 | | Main$1.run() line: 508 | | Thread.run() line: not available | | | What I meant was that a module within the EAR is not getting determineStructure called. I know this for a fact as I'm stepping through... Now where to put determineStructure? Within DefaultStructureBuilder? BTW, can you please explain what DefaultStructureBuilder is trying to accomplish? Specifically, what is going on with all the Classpath stuff? Specifically, I need to know if the Classpath will only contain the EJB jar and not other jars so that I can scan propertly for annotations. thanks View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3981122#3981122 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3981122

19 years, 5 months

1
0
0 / 0

[Design of POJO Server] - Re: EARStructure not deploying modules

by bill.burke＠jboss.com

"scott.stark(a)jboss.org" wrote : I'm also not seeing the parent/child problem you mention. When the ear child module from the application.xml is added to the ear ContextInfo, the parent is matched up. This is for an unpacked ear. | Maybe because you are not deploying via a JBossTestCase and MainDeployer.deploy(URL)??? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3981121#3981121 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3981121

19 years, 5 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: JBMICROCONT-23, support for lifecycle annotations

by alesj

>> Just wing it Wing it? I added annotation lifecycle support. But I have problems since my annotations don't get picked up by container module. | Set<MethodInfo> methods = beanInfo.getMethods(); | if (methods != null) | { | for (MethodInfo mi : methods) | { | if (mi.isAnnotationPresent(getUninstallAnnotation())) | { | return mi.getName(); | } | } | } | Results in no lifecycle annotation found. How is with actual lifecycle annotation class usage in annotation lookup - or should I use a straight String? | public String getInstallAnnotation() | { | return CreateLifecycle.class.getName(); | } | Lifecycle annotations have C in cycle in lower case - as all other lifecycle classes - not as in JIRA issue. And what's the status of JBossXB, since I get a lot of ClassCastExc while testing - saying my metadata is of illegal class. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3981116#3981116 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3981116

19 years, 5 months

1
0
0 / 0

[Design of POJO Server] - Re: EARStructure not deploying modules

by scott.stark＠jboss.org

I'm also not seeing the parent/child problem you mention. When the ear child module from the application.xml is added to the ear ContextInfo, the parent is matched up. This is for an unpacked ear. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3981115#3981115 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3981115

19 years, 5 months

1
0
0 / 0

[Design of POJO Server] - Re: EARStructure not deploying modules

by scott.stark＠jboss.org

I'm sitting in it now for an ear deployment: | Thread [main] (Suspended (breakpoint at line 102 in EARStructure)) | EARStructure.determineStructure(VirtualFile, StructureMetaData, StructuredDeployers) line: 102 | BasicStructuredDeployers.determineStructure(VirtualFile, StructureMetaData) line: 76 | MainDeployerImpl.determineStructure(DeploymentContext) line: 528 | MainDeployerImpl.addDeploymentContext(DeploymentContext) line: 271 | ProfileServiceBootstrap.loadProfile(String) line: 365 | ProfileServiceBootstrap.bootstrap() line: 246 | ProfileServiceBootstrap(AbstractBootstrap).run() line: 89 | ServerImpl.doStart() line: 401 | ServerImpl.start() line: 340 | Main.boot(String[]) line: 210 | Main$1.run() line: 508 | Thread.run() line: not available | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3981114#3981114 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3981114

19 years, 5 months

1
0
0 / 0

[Design of POJO Server] - Re: EARStructure not deploying modules

by bill.burke＠jboss.com

I'm pretty sure determineStructure is not called on the EAR module as its classpath is null. Looking into this too. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3981113#3981113 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3981113

19 years, 5 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums October 2006