[Design of JBoss Labs] - Ear class loader question
by tbottger
I am deploying an ear that contains a couple WAR files and a lot of JAR files. One of the JAR files contained within the EAR is jaxb-rt-1.0-ea.jar. When I deploy and run the EAR, I am getting a java.lang.NoSuchFieldError: INITIAL_COLOR error. I am thinking I am conflicting with the Jboss-j2ee.jar located in the ${jbossHome}/server/test/lib. I don't understand why it is loading the class from this jar when the correct jar is in my EAR and gets deployed. I have the jaxb-rt-1.0-ea.jar in the MANIFEST.MF for my WAR and made sure that there is no reference to the Jboss-j2ee.jar. What is causing this jar in the ${jbossHome}/server/test/lib to be loaded instead of my jar?
I thought it my be a parent-first loading, but I have made sure my false in the jboss-service.xml in the deploy\jbossweb-tomcat55.sar directory. I am using 4.0.4. Any help would be appreciated.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968184#3968184
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3968184
20 years, 1 month
[Design of JBoss Labs] - Productization metrics for JEMS Matrix
by wrzep
Hello,
In the JEMS Maturity Matrix we would like to have measures describing software productization. I'm not entirely sure what should be listed here, but I've got some ideas and would appreciate your comments.
I like the following, short article about productization:
Effective productization in open source projects
anonymous wrote :
| Productization means turning the software into a "whole product" -- providing all the pieces that are necessary for mainstream users to get value from the software. This includes documentation, support and training. It also involves some type of branding (how people identify the product, like logos and company image).
|
Let's say we are measuring single project, mainly from user's point of view. We can consider:
- available documentation (manuals, wiki, FAQ, javadoc),
- professional support,
- training,
- if it is packaged for download,
- easy installation (web installer or installation manual),
- JEMS integration,
- user forums (?, as a kind of support),
- project version.
These are mainly booleans, but considered together they can give you some sense of how mature project is.
Metrics listed above could take necessary data from the project.xml files. Some info is already present (like JEMS integration), rest would be easy to include (like links to docs) and could be useful in the other contexts as well.
Also, project branding was mentioned above. It seems hard to measure how people recognize or appreciate the product. Idea that came to my mind was kind of google metric (for instance, how many web pages link to the product page), but it might be difficult to do it fairly.
Project popularity could be also measured with number of website visits. Or, maybe, we should introduce metrics based on polls?
I wonder what's your opinion.
Cheers,
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968162#3968162
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3968162
20 years, 1 month
[Design of JBoss jBPM] - Re: web services question
by alex.guizar＠jboss.com
I hadn't had a chance to follow this topic. Hopefully my input will still be useful before Ronald goes to Aruba :)
In general you should defer as much Java-XML binding to the web services stack as you can. Custom parsing should be avoided as it is hard to optimize. Something like:
<command name="[xsd:string]" [other attibutes optional]>
| [any mixed content]
| </command>
maps, per JAX-RPC rules, to
class Command {
| String name;
| SOAPElement _any;
| }
The SOAP stack parses the [any mixed content] to produce the SOAPElement. Then the application processes the SOAPElement to produce Java objects. Result: two separate binding steps!
Plus, every command is a separate contract and should have its own document. Something like Ronald's proposal:
<startProcess>
| <processDefinition .../>
| <variables ...>
| </startProcess>
is a lot better. What is unclear to me is how to introduce new commands. Is each of them a new operation in the WSDL port type?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968149#3968149
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3968149
20 years, 1 month