[Design the new POJO MicroContainer] - Nulling properties on uninstall
by scott.stark@jboss.org
I just saw that on a failed installation, the mc is nulling out previously set properties as part of the uninstall process. I'm not expecting this so an NPE is resulting:
| 40250 TRACE [AbstractKernelController] Uninstalling VFSDeploymentScanner from Create
| 40250 TRACE [CreateDestroyLifecycleAction] No destroy method for AbstractKernelControllerContext@3727c5{ metadata=AbstractBeanMetaData@2f1e75{name=VFSDeploymentScanner bean=org.jboss.deployers.plugins.scanner.VFSDeploymentScannerImpl properties=[mainDeployer, URIList] constructor=null}name=VFSDeploymentScanner target=VFSDeploymentScannerImpl@18baf36{} state=Configured depends=AbstractDependencyInfo@19c4091{idependOn=[AbstractDependencyItem@19ed7e{name=VFSDeploymentScanner dependsOn=MainDeployer whenRequired=Configured dependentState=Installed resolved=true}] unresolved=[AbstractDependencyItem@19ed7e{name=VFSDeploymentScanner dependsOn=MainDeployer whenRequired=Configured dependentState=Installed resolved=true}]}}
| 40250 TRACE [AbstractKernelController] Uninstalling VFSDeploymentScanner from Configured
| 40250 TRACE [ConfigureAction] Ignored for org.jboss.joinpoint.plugins.BasicMethodJoinPoint@ecd92c
| java.lang.NullPointerException
| at org.jboss.deployers.plugins.scanner.VFSDeploymentScannerImpl.setMainDeployer(VFSDeploymentScannerImpl.java:109)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
| at java.lang.reflect.Method.invoke(Unknown Source)
|
I guess there needs to be a convention for the injection state of properties vs the bean kernel state. In this particular case I was just obtaining another property from the injected bean so I could actually delegate that to the kernel, but consider the case of deployers registering with the MainDeployer on injection. If there is no explicit start lifecycle, and injection of the MainDeployer was used as a proxy for this, there would be no way to unregister on uninstall. I guess that just means injection cannot be used as a proxy for lifecycle callbacks.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3958202#3958202
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3958202
19 years, 8 months
[Design of JBoss Web Services] - error in deploying a webservice
by sriv.abhishek
hi all,
I am trying to deploy a webservice that uses hibernate to map objects to a MySql database. I have a .ddl file that I use to create the schema. When I try to run ws tools on it it gives me this error.
generate-sources:
[wstools] log4j:WARN No appenders could be found for logger (org.jboss.ws.too
s.WSTools).
[wstools] log4j:WARN Please initialize the log4j system properly.
[wstools] java.lang.NullPointerException
[wstools] at org.jboss.ws.tools.schema.SchemaTypeCreator.introspectJavaPr
perties(SchemaTypeCreator.java:575)
[wstools] at org.jboss.ws.tools.schema.SchemaTypeCreator.generateNewType(
chemaTypeCreator.java:334)
[wstools] at org.jboss.ws.tools.schema.SchemaTypeCreator.getType(SchemaTy
eCreator.java:272)
[wstools] at org.jboss.ws.tools.schema.SchemaTypeCreator.generateType(Sch
maTypeCreator.java:133)
[wstools] at org.jboss.ws.tools.JavaToXSD.generateForSingleType(JavaToXSD
java:109)
[wstools] at org.jboss.ws.tools.helpers.JavaToWSDLHelper.generateType(Jav
ToWSDLHelper.java:555)
[wstools] at org.jboss.ws.tools.helpers.JavaToWSDLHelper.generateTypesFor
SD(JavaToWSDLHelper.java:141)
[wstools] at org.jboss.ws.tools.JavaToWSDL11.handleJavaToWSDLGeneration(J
vaToWSDL11.java:236)
[wstools] at org.jboss.ws.tools.JavaToWSDL11.generate(JavaToWSDL11.java:1
8)
[wstools] at org.jboss.ws.tools.JavaToWSDL.generate(JavaToWSDL.java:318)
[wstools] at org.jboss.ws.tools.helpers.ToolsHelper.handleJavaToWSDLGener
tion(ToolsHelper.java:122)
[wstools] at org.jboss.ws.tools.WSTools.process(WSTools.java:129)
[wstools] at org.jboss.ws.tools.WSTools.generate(WSTools.java:119)
[wstools] at org.jboss.ws.tools.ant.wstools.execute(wstools.java:103)
[wstools] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.j
va:275)
[wstools] at org.apache.tools.ant.Task.perform(Task.java:364)
[wstools] at org.apache.tools.ant.Target.execute(Target.java:341)
[wstools] at org.apache.tools.ant.Target.performTasks(Target.java:369)
[wstools] at org.apache.tools.ant.Project.executeSortedTargets(Project.ja
a:1216)
[wstools] at org.apache.tools.ant.Project.executeTarget(Project.java:1185
[wstools] at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(D
faultExecutor.java:40)
[wstools] at org.apache.tools.ant.Project.executeTargets(Project.java:106
)
[wstools] at org.apache.tools.ant.Main.runBuild(Main.java:668)
[wstools] at org.apache.tools.ant.Main.startAnt(Main.java:187)
[wstools] at org.apache.tools.ant.launch.Launcher.run(Launcher.java:246)
[wstools] at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67)
any pointers or suggestion would be appreciated.
Thankyou,
Abhishek Srivastava.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3958188#3958188
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3958188
19 years, 8 months
[Design of JBoss Eclipse IDE (dev)] - Re: JBossSeam IDE proposal
by cdelashmutt
Targeting UI tools for an initial release is probably a bit overzealous, but I have some ideas I would like to discuss. You all are probably thinking about these features anyway, but I'd like to discuss them a bit.
I think that linking in knowledge of Seam components in your build path is a critical feature to add. Creation of projects/components/etc is very important, but I think that it is also very important to give some tools that help with major of work that needs to be done in a given application.
What I mean by this is, first, content assist that can help you complete references to seam components and properties or methods (depending on the context). I think also, a browser of some sort that shows you all of the known Seam components, plus the built in ones would be good as well. Of course, drag and drop from the browser to code would be a nice feature as well.
I think the pinnacle in my mind right now is a JSF visual editor (possibly WTP's effort?) that is Seam aware. Basically couple the component browser with the JSF editor to allow a drag of a component property or method and drop on a property of a JSF component to "bind" it to that component. This sort of thing might even be something that we can release as JSF preview of a page, and then move to more editing in the future.
I'd love to do this sort of thing, but I'm only one person, and I'm already on the hook for a SPNEGO JAAS authentication module for JBoss SX. :) That being said, I'd like to discuss this functionality further to try and break it down into chunks that might be small enough for me to do.
What do you guys think? Stupid idea? Already done? Something better?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3958165#3958165
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3958165
19 years, 8 months