[Design of JBoss Web Services] - Re: [Productivity] Level 1 - Start from scratch
by alessio.soldano＠jboss.com
What are we going to do?
Regarding the IDE setup, we might provide a basic Eclipse project configuration that users might use as a starting point for each of their ws-enabled projects. Otherwise we could create a simple presentation / movie showing users how to setup the environment the right way.
We might also ask the Red Hat Developer Studio team to support the latest jbossws features (at least the wsprovide and wsconsume tools).
Then we should link the documentation and the samples more tightly. This means that most of the samples and tests will be enriched with a brief description (a scenario) in the documentation. Then wherever the documentation covers a particular feature backed up by a sample or test case, there will be a link to the test-suite. Finally we could make the test-suite run easier providing an Eclipse project configuration with the tests only and a simplified Ant script to run each of them.
What do you think about these ideas? Do you think something else might be useful?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4095208#4095208
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4095208
18 years, 5 months
[Design of JBoss Build System] - Maven build broken again - Microcontainer
by adrian＠jboss.org
Why is Maven trying to download snapshots for artifacts in the same project?
| [INFO] ----------------------------------------------------------------------------
| [INFO] Building JBoss Deployers Impl
| [INFO] task-segment: [install]
| [INFO] ----------------------------------------------------------------------------
| [INFO] [resources:resources]
| [INFO] Using default encoding to copy filtered resources.
| [INFO] snapshot org.jboss.microcontainer:jboss-container:2.0.0-SNAPSHOT: checking for updates from snapshots.jboss.org
| [INFO] snapshot org.jboss.microcontainer:jboss-container:2.0.0-SNAPSHOT: checking for updates from jboss-snapshots
| Downloading: http://snapshots.jboss.org/maven2//org/jboss/microcontainer/jboss-contain...
| 324K downloaded
| [INFO] snapshot org.jboss.microcontainer:jboss-dependency:2.0.0-SNAPSHOT: checking for updates from snapshots.jboss.org
| [INFO] snapshot org.jboss.microcontainer:jboss-dependency:2.0.0-SNAPSHOT: checking for updates from jboss-snapshots
| Downloading: http://snapshots.jboss.org/maven2//org/jboss/microcontainer/jboss-depende...
| 56K downloaded
| [INFO] [compiler:compile]
| [INFO] Compiling 1 source file to /home/ejort/microcontainer/deployers-impl/target/classes
| [WARNING] /home/ejort/microcontainer/deployers-impl/src/main/org/jboss/deployers/plugins/main/MainDeployerImpl.java:[161,28] [deprecation] getDeploymentContext(java.lang.String,boolean) in org.jboss.deployers.structure.spi.main.MainDeployerStructure has been deprecated
|
| [WARNING] /home/ejort/microcontainer/deployers-impl/src/main/org/jboss/deployers/plugins/main/MainDeployerImpl.java:[154,28] [deprecation] getDeploymentContext(java.lang.String) in org.jboss.deployers.structure.spi.main.MainDeployerStructure has been deprecated
|
| [INFO] [resources:testResources]
| [INFO] Using default encoding to copy filtered resources.
| [INFO] [compiler:testCompile]
| [INFO] Compiling 1 source file to /home/ejort/microcontainer/deployers-impl/target/tests-classes
| [INFO] ------------------------------------------------------------------------
| [ERROR] BUILD FAILURE
| [INFO] ------------------------------------------------------------------------
| [INFO] Compilation failure
|
| /home/ejort/microcontainer/deployers-impl/src/tests/org/jboss/test/deployers/deployer/support/TestServiceMetaDataICF.java:[39,67] type org.jboss.managed.spi.factory.InstanceClassFactory does not take parameters
|
| /home/ejort/microcontainer/deployers-impl/src/tests/org/jboss/test/deployers/deployer/support/TestServiceMetaDataICF.java:[88,41] cannot find symbol
| symbol : method unwrap(org.jboss.metatype.api.values.MetaValue,java.lang.Class)
| location: class org.jboss.metatype.api.values.MetaValueFactory
|
The class does exist in the Microcontainer's managed project, but it obviously
doesn't exist in the snapshot.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4095181#4095181
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4095181
18 years, 5 months
[Design of JBoss Serialization] - Multithreading
by FredrikJ
Hi.
We are currently using jboss serialization for a multithreaded server solution. I just ran some performance tests and saw that all my worker-threads were busy and when generating a stacktrace they all are in the same jboss serialization method.
The stacktraces look like:
| "Table-GameEventDaemon-gam1-23" prio=1 tid=0x8a331500 nid=0x2ac0 runnable [0x8662e000..0x8662efa0]
| at org.jboss.serial.classmetamodel.ClassMetamodelFactory$CacheLoaderReference.setCurrentClassLoader(ClassMetamodelFactory.java:92)
| at org.jboss.serial.classmetamodel.ClassMetamodelFactory.getLoaderMap(ClassMetamodelFactory.java:248)
| at org.jboss.serial.classmetamodel.ClassMetamodelFactory.getClassMetaData(ClassMetamodelFactory.java:346)
| at org.jboss.serial.objectmetamodel.ObjectDescriptorFactory.describeObject(ObjectDescriptorFactory.java:172)
| at org.jboss.serial.objectmetamodel.DataContainer$DataContainerDirectOutput.writeObject(DataContainer.java:206)
| at org.jboss.serial.persister.ObjectOutputStreamProxy.writeObjectOverride(ObjectOutputStreamProxy.java:60)
| at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:298)
| at java.util.TreeMap.writeObject(TreeMap.java:1475)
| at sun.reflect.GeneratedMethodAccessor8.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.serial.persister.RegularObjectPersister.writeSlotWithMethod(RegularObjectPersister.java:120)
| at org.jboss.serial.persister.RegularObjectPersister.defaultWrite(RegularObjectPersister.java:86)
| at org.jboss.serial.persister.RegularObjectPersister.writeData(RegularObjectPersister.java:62)
| at org.jboss.serial.objectmetamodel.ObjectDescriptorFactory.describeObject(ObjectDescriptorFactory.java:276)
| at org.jboss.serial.objectmetamodel.DataContainer$DataContainerDirectOutput.writeObject(DataContainer.java:206)
| at org.jboss.serial.io.JBossObjectOutputStream.writeObjectOverride(JBossObjectOutputStream.java:181)
| at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:298)
| at com.game.util.Serializer.serialize(Serializer.java:29)
The code used to serialize the objects is written like:
public final static byte[] serialize(Object o) throws IOException {
| ByteArrayOutputStream ba = new ByteArrayOutputStream();
| BufferedOutputStream bo = new BufferedOutputStream(ba);
| JBossObjectOutputStream out = new JBossObjectOutputStream(bo);
| out.writeObject(o);
| out.flush();
| return ba.toByteArray();
| }
So, why are all threads choking at setCurrentClassloader? Is that an expensive operation?
Also, is there any way we can improve the throughput here, either by rewriting the serialize(...) method or by pooling some resources?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4095131#4095131
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4095131
18 years, 5 months
[Design of JBoss Web Services] - Re: [Productivity] Level 0 - WS Culture
by alessio.soldano＠jboss.com
What are we going to do?
Level 0 issues may be solved enhancing the current documentation. As I previously said, all productivity efforts will start from a reorganization of our documentation. It's supposed to leverage some of the Wiki features, like categories, to link related pages. Our aim will be to provide each user with its own "red-path" for reading the documentation, according to her knowledge and needs.
In particular, speaking of level 0, beginners will be driven to pages concerning the WS culture, that means:
- basic webservice knowledge
- webservices main goals (interoperability, etc)
- terminology and related technologies (WSDL, SOAP, etc)
These pages will not go into details, they'll delegate to official third-party docs when needed. They'll only provide the readers with the high level view of a WS system, explaining them what they really have to know. This is going to be something like the glue that keeps the *right* detailed, documentation together.
The action we think to carry out for this level are quite straightforward; however if somebody has something to add or any suggestion, as always, feel free to comment.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4095124#4095124
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4095124
18 years, 5 months
[Design of JBoss Web Services] - [Productivity] Level 0 - WS Culture
by alessio.soldano＠jboss.com
This thread is about the first level of productivity efforts we're thinking about for jbossws. Please refer to this http://www.jboss.com/index.html?module=bb&op=viewtopic&t=121127 for a topic introduction.
Every technology has its own learning curve. Understanding webservices might be not so easy at first because of the number and complexity of all the specification involved. Moreover, the world wide web contains lots of tutorials, guides, walk-through concerning webservice development, but most of them are either hard to understand, obsolete or out-of-date, referring proprietary/non-standard technologies, etc. This is most likely going to mislead and confuse the readers.
A clear guide providing the right directions for a correct learning path may help customers acquire the knowledge they really need without waisting a lot of time. This:
- increases the user satisfaction
- gives us customers that really know what webservices are about and use them according to the aims they are meant to be used for
- finally allows customers to easily proceed one step ahead and leverage our advanced features (related to the following levels) for their business, instead of struggling with beginners' issues because of their poor knowledge.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4095120#4095120
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4095120
18 years, 5 months