[Design of JBoss Web Services] - JBWS-1464 Clarification of the MTOM related specifications.
by darran.lofthouse@jboss.com
I have been looking at the following specification to try and get a better understanding of how the mime type for binary content is specified in the schema and in the actual document transmitted: -
http://www.w3.org/TR/xml-media-types/
My interpretation is that the 'expectedContentTypes' attribute is an annotation which is added to the XML schema to list the mime types that can be represented by the binary content.
My interpretation of the 'contentType' is that this is used on the document instance itself (not the schema) to specify what is the actual mime type of the binary data being transmitted.
So in the schema 'expectedContentTypes' can be used to list a set of mime types and then in the document 'contentType' is used to specify what is being transmitted in this document instance.
However in the user guide and in some test cases we seem to be using 'contentType' in the place of 'expectedContentTypes' or in addition to 'expectedContentTypes' in the schema.
This seems incorrect to me, should it really be possible to use 'contentType' in the schema?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4004005#4004005
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4004005
19 years, 2 months
[Design of JBoss Profiler] - unable to use jboss Profiler
by graj
I wrote a simple method (in a seperate public class) that prints the number 1 to 20 to the console with a delay of 5 sec. This method was called from a Servlet.
Steps to recreate my scenario:
1. start JBoss App Server
2. Activate the profiler using the MBean
3. invoke my Servlet and wait for the 20 numbers to be printed on the console
4. stop the profiler by stoping it using the MBean. At this point I see the .gz files getting updated with data.
5. Now open the Profiler's Web Application and enter the directory where the log entrries are made.
My Problem:
I see the method I wrote listed in the memory section of the process view and not in the 'methods' section of the Process View in the resulting analysis data.
Since my method is not listed in the 'methods section' of the process view, I am unable to analyze the response time for invoking the method. Can you please help me.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4004004#4004004
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4004004
19 years, 2 months
[Design of JBoss jBPM] - Re: new simplified menu structure
by david.lloyd@jboss.com
"tom.baeyens(a)jboss.com" wrote : +1. So we should give some thought on how the user can specify button names and link them to transition names. By default, the transition names are chosen, but the user should be able to override these. If no transition name is specified and no button name is given, we can't do anything else except come up with a silly generic name.
I can add an attribute to the transitionButton component for an optional caption. If the caption is not present, use the transition name. If the transition is unnamed, then I guess just "Transition ID 1234" is the best we can do...
"tom.baeyens(a)jboss.com" wrote : "falazar" wrote : And the "Cancel" does not actually cancel the task or the process, so it is very ambigously named, we changed it to "Go back to inbox" and added a Cancel Request transition button.
|
| good point. that button got me fooled too. since there is a task.cancel method, i thougt it was cancelling the task. "Back to Inbox" is indeed better
Hmmm, upon reflection I think that a cancel task button is a lot more useful than the current cancel button is - what if I change this button to "Cancel Task" which calls the .cancel() method on the task instance, and just drop the idea of the original cancel button? Especially in light of the new navigation structure.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4003997#4003997
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4003997
19 years, 2 months
[Design of JBoss Serialization] - Re: resolveClass and annotateClass
by Glooper
I had a few hours today to have a look at this so was examining your code to see how I would solve my problem. Please correct me if I'm wrong!
I can't see how you could ever call annotateClass as class information is persisted on the stream seperately to the objects. You are using the ClassMetaData class to describe a class, and you persisting that information using the StreamingClass class.
I'm guessing that to change jboss serialization such that different class loaders can be used for different serialized objects, I would have to include the relevant information within the ClassMetaData... and change StreamingClass such that it can store the classloader information in saveStream and read the class loader information at the beginning of the readStream method. Does this make sense?
Ben
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4003991#4003991
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4003991
19 years, 2 months