[Design of POJO Server] - Still have insufficient separation of metadata (Repost)
by scott.stark@jboss.org
(Reposted after cleaning up the confused thoughts)
Even after the attempt to cleanup the DeploymentUnit attachment transient vs trasient managed object attachments by putting non-serializable attachments into the transient bucket, while looking into JBMICROCONT-152 even serializable metadata is too aggregate to be able to make this distinction. For example, the ServiceMetaData contains ServiceInjectionValueMetaData which has a transient dependency that can be non-serializable (apparently, I cannot remember now why I marked it as transient):
| public class ServiceInjectionValueMetaData extends AbstractMetaDataVisitorNode
| implements ServiceValueMetaData, Serializable
| {
| private static final long serialVersionUID = 1;
|
| /** The dependency */
| private transient Object dependency;
|
| /** The property */
| private String property;
|
| /** The required state of the dependency */
| private ControllerState dependentState = ControllerState.INSTALLED;
|
This was not a valid transformation to a Serializable because the dependency cannot be restored, and its a neccessary attribute. A similar problem exists with ServiceConstructorMetaData as this generally contains arbitrary non-serializable/non-managed metadata needed to construct the underlying service instance.
So, the default attachment bucket is going to have to be the transient one. Only if a deployer knows its metadata can be used as a serializable transient managed object would it use the transient managed object bucket explicitly.
Generally it looks like the existing metadata is going to have to be refactored to allow for externalizable managed objects that can be persisted. We need to come back to this post the jboss5 beta2 release when the work done by Adrian has been integrated.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4024558#4024558
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4024558
19 years, 1 month
[Design of JBoss Build System] - Re: Build System Meeting Agenda Mar 01, 2007
by scott.stark@jboss.org
"pgier" wrote :
| Should we create some kind of automatic notification for releases? This could be done through a maven plugin that sends an email or generates an RSS feed.
|
Sounds good, but this should also be integrated into the jboss.org site. Perhasp the rss feed is sufficient for that.
"pgier" wrote :
| How should we handle thirdparty jars in our repository? One way is to set up a separate repository just for thirdparty artifacts. Another way is to allow developers to add thirdparty stuff to the snapshot repository, and then copy the required files to the release repository when a release is performed.
|
I still need the behavior of snapshot vs non-snapshot described better. We already have 'snapshot' releases in jboss and maven repositories. How does a snapshot repository come into the picture and help things. Layout the pros and cons.
"pgier" wrote :
| I started looking at some maven scripts for app server from about 1 year ago. They are out of date, but I will see what I can use from them and add them to app server 5.0.
|
Before doing that we need to get some of the existing mavenized projects fully working. The jbossxb project is in a essentially unknown branching state. The vfs project unit tests fail because the url handler system property settings are not getting passed to the test correctly.
"pgier" wrote :
| What needs to go into the distribution file for microcontainer? We talked about creating an assembly for microcontainer, but I'm not sure if there are any old releases similar to what we want now.
|
I'm going to create a separate thread on this in the mc forum.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4024718#4024718
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4024718
19 years, 1 month
[Deployers on JBoss (Deployers/JBoss)] - Howto to hot deploy only parts of exploded EAR file
by arubamalice
Apologies if this subject has been posted before but I have searched through the forums and not found an answer.
I am using JBoss 4.0.4. The project I am working on deploys an exploded EAR folder.
The name of the exploded EAR folder is MyTestApp.ear (example name).
This EAR file contains an exploded web app (MyWebApp.war) and an exploded JAR file (MyClasses.jar)
So the top level folder structure is
MyTestApp.ear
+--META-INF
+--MyWebApp.war
+--MyClasses.jar
The MyWebApp.war and MyClasses.jar components are correctly referenced in the META-INF/application.xml file as web and java modules
respectively.
Now every time I do a build and update the META-INF/application.xml, JBoss correctly auto deploys the whole ear file.
The problem is that my application uses Spring and various other components. Hence the build and deploy time can take up to
two minutes which is really frustrating when making minor changes to only the classes in the MyClasses.jar file.
Is there a way for me to onlyhot deploy the MyClasses.jar file and get JBoss to reload all the classes in this JAR, without deploying
the whole EAR file?
If anyone has any advice this would be appreciated.
Ayub M
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4024702#4024702
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4024702
19 years, 1 month