[Design of JBoss Web Services] - Re: [Productivity] Level 1 - Start from scratch
by timeagentess
1. I think it would be helpful to specify at each step exactly what is being done and what files the user should expect to have after completing it.
i.e. "First step is to create the remote interface and the service class, with annotations so-and-so, which control aspects xyz. After doing so, you should have these files, structured as follows:..."
2. Also, clear indication of which files are generated automatically, at which step and with which tools would be a great help for beginners.
(The JBossWS documentation as it is now offers good building bricks, so to say, but it doesn't always make it clear what to start with or where to use them to get a desired effect)
3. I also agree with maeste above about the advantages of using standard ant build.xml files. I think it is daunting experience for a user who is both a newbie with WS and not using the IDE described in the tutorial to have to try and adapt the solution to their own config. There are many enough concepts and tools one must get familiar with in order to be comfortable using WS, and having to understand an IDE on top of that does not help ;)
(Plus, I have the feeling working through an IDE puts details crucial for understanding WS in a "black box", which is good when everything is working perfectly, but it's not very helpful when, more often than not, things go wrong)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4096893#4096893
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4096893
18 years, 5 months
[Design of JBoss jBPM] - Re: Extension of the Designer
by magro1202
Hi Koen
thank you for your answer
the action should be configurable in every case you can use an action node, e.g. in Nodes, transitions, states, events, ...
so i do not want to create a seperate action, or a special node, i would like to extend the existing Action node to give a user the opportunity to load a definition of all specific elements he needs for his special issue to the designer to show up controls with which he can configure these elements, whatever the elements are.
So for a concrete example:
i could imagine, in a standard action configuration page there is a new tab, as you mentioned, where you can choose a definition in XML Format for example.
in this XML File all custom elements are specified.
The XML File is to be parsed by the designer and then the designer offers
configuration possibilities for his elements.
Then the made configurations are transfered to the given action node in the process definition.
the elements need not necessarily be dependant to the ActionHandler, it could be that the specified class is not available within the designed Project
my intension is to make an action node freely configurable to every user with custum issues he wants to do within the action without manually adjust the process definition file.
May be there are a lot other possibilities to get that straight,
this is gonna be one main point of my thesis to figure them out.
this is getting interesting i think.
If you have any recommendations dont't hesitate to tell me, i'm open for all opinions
regards
Matthias
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4096873#4096873
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4096873
18 years, 5 months
[Design of JBoss jBPM] - Re: splitting access= on variables into multiple attributes
by tom.baeyens＠jboss.com
in 4.0, for jPDL i hope to pursue the following:
1) jPDL in bacwards compatibility mode. old jPDL processes will be deployable in jPDL 4, but the databases will probably be incompatible.
2) jPDL 2. There are a lot of improvements that can be made to jPDL. More direct support for other concurrecy models, hierarchical sub-tasks instead of the flat list we have now, process annotations, static variables, variable declarations, etc
3) expand jPDL 2 with many functional node types. E.g. like the mail node we have now or with web service invocation nodes. also we might think of modelling external triggers. E.g. transactions might be external triggers or internal events. When those triggers are explicitely modelled with input parameters, it's possible to generate java beans or web services from that (like BPEL does).
This last focus would allow us to cover a big part of the BPEL functionality with free graph modelling, easier integration between services and java and other node types,...
But with out limited resources, we'll have to take it step by step and see where we end up...
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4096858#4096858
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4096858
18 years, 5 months
[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Integration on JBoss5: NullPointerException deploying jm
by scott.stark＠jboss.org
With the latest metadata update all but the security tests are passing. I still see a lookup error from the TopicAdapter, but this is because of a race condition between shutting down the container on undeploy and some outstanding msgs.
| tests-jbossmessaging-unit:
| [junit] Running org.jboss.test.jbossmessaging.perf.JMSPerfStressTestCase
| [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 6.065 sec
| [junit] Running org.jboss.test.jbossmessaging.perf.JMSReconnectStressTestCase
| [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 2.305 sec
| [junit] Running org.jboss.test.jbossmessaging.perf.ReceiveNackClientStressTestCase
| [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 1.819 sec
| [junit] Running org.jboss.test.jbossmessaging.perf.SendReplyPerfStressTestCase
| [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 2.124 sec
| [junit] Running org.jboss.test.jbossmessaging.ra.RaJMSSessionUnitTestCase
| [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 7.67 sec
| [junit] Running org.jboss.test.jbossmessaging.ra.RaQueueUnitTestCase
| [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 5.76 sec
| [junit] Running org.jboss.test.jbossmessaging.ra.RaSyncRecUnitTestCase
| [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 2.671 sec
| [junit] Running org.jboss.test.jbossmessaging.ra.RaTopicUnitTestCase
| [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 5.624 sec
| [junit] Running org.jboss.test.jbossmessaging.test.ConcurrentDeliveryUnitTestCase
| [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 21.609 sec
| [junit] Running org.jboss.test.jbossmessaging.test.ConnectionConsumerUnitTestCase
| [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 1.985 sec
| [junit] Running org.jboss.test.jbossmessaging.test.JBossMessagingJoramUnitTestCase
| [junit] Tests run: 198, Failures: 0, Errors: 0, Time elapsed: 21.313 sec
| [junit] Running org.jboss.test.jbossmessaging.test.JBossSessionRecoverUnitTestCase
| [junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 13.526 sec
| [junit] Running org.jboss.test.jbossmessaging.test.MessageBodyUnitTestCase
| [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 10.214 sec
| [junit] Running org.jboss.test.jbossmessaging.test.MessageTypesUnitTestCase [junit] Tests run: 6, Failures: 0, Errors: 0, Time elapsed: 1.96 sec
| [junit] Running org.jboss.test.jbossmessaging.test.RollBackUnitTestCase
| [junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 5.205 sec
| [junit] Running org.jboss.test.jbossmessaging.test.SecurityUnitTestCase
| [junit] Tests run: 30, Failures: 9, Errors: 0, Time elapsed: 17.217 sec
| [junit] Test org.jboss.test.jbossmessaging.test.SecurityUnitTestCase FAILED [junit] Running org.jboss.test.jbossmessaging.test.TemporarySessionConnectionUnitTestCase
| [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 1.608 sec
| [junit] Running org.jboss.test.jbossmessaging.test.UnackedUnitTestCase
| [junit] Tests run: 6, Failures: 0, Errors: 0, Time elapsed: 29.137 sec
| [junit] Running org.jboss.test.jbossmessaging.test.XAResourceUnitTestCase
| [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 1.674 sec
| [junit] Running org.jboss.test.jbossmessaging.test.XAResourceWrapperSmokeUnitTestCase
| [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.338 sec
|
| BUILD SUCCESSFUL
| Total time: 3 minutes 5 seconds
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4096808#4096808
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4096808
18 years, 5 months