[JBoss Tools Development] New message: "Re: Content Assist in attributes which should be filled with id's"
by Denis Golovin
JBoss development,
A new message was posted in the thread "Content Assist in attributes which should be filled with id's":
http://community.jboss.org/message/530242#530242
Author : Denis Golovin
Profile : http://community.jboss.org/people/dgolovin
Message:
--------------------------------------------------------------
I'm just brainstorming what would it be:
1. Enabling/disabling facelets on Dynamic Web Project which would modify required resources and add required libraries;
2. New wizards to create templates with selection from predefined layouts like: header/body, header/body/footer, header/left/body/footer and etc...
3. Template/component extraction (this one I heard from Alexander Smirnov) - select region/node in current jsp and then convert it into facelet component/template. Vice versa case also could be useful but it is not a priority.
4. Search for facelets elements references
5. Refactoring (is based on 4):
- renaming/moving template files
- renaming facelet elements like ui:insert@name value
6. Content assist improvements (see Maxim example)
7. Content assist Templates (see XML templates for XML editor or ant build.xml editor)
8. .... list is still open you name it
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/530242#530242
16 years, 1 month
[JBoss Microcontainer Development] New message: "Re: Circular Dependencies and Semi-Resolve"
by Adrian Brock
JBoss development,
A new message was posted in the thread "Circular Dependencies and Semi-Resolve":
http://community.jboss.org/message/530211#530211
Author : Adrian Brock
Profile : http://community.jboss.org/people/adrian@jboss.org
Message:
--------------------------------------------------------------
> alesj wrote:
>
> Does this work out-of-the-box for multiple circular depending deployments (aka OSGi bundles, which is what we're aiming for)?
>
> How are service's invalid configs reported -- A on B in ctor, and vice-versa?
> I guess they just don't ever get resolved -- failing at check complete?
Look at the tests, e.g. testTransientComplicatedCircular(), or write a new one if you think its not handled. ;-)
I don't think I've got full coverage on the tests since there's a lot of edge-cases with the
backwards compability handling, but I've got all of the basics.
Circular dependencies will only work if the DependencyItem explicitly invokes semiResolve()
(or it has some other way of handling it). So it doesn't change anything for existing implementations.
The checkComplete() should work fine. If the circular dependency can be resolved, its DependencyItem will
be in the RESOLVED state, so it won't appear in the IncompleteDeploymentException (IDE).
If its only in the SEMI_RESOLVED state, i.e. something is missing, it will appear in the IDE.
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/530211#530211
16 years, 1 month
[JBoss ESB Development] New message: "Re: Camel integration input requested"
by Edgar Silva
JBoss development,
A new message was posted in the thread "Camel integration input requested":
http://community.jboss.org/message/530204#530204
Author : Edgar Silva
Email : edgarsilva(a)gmail.com
Profile : http://community.jboss.org/people/edgar.silva
Message:
--------------------------------------------------------------
Yes, you are right, this gateway is inside the services section:
<services>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <service category="Custom" name="Listener" description="" invmScope="GLOBAL"> <listeners> <listener name="ApacheCamel" busidref="ApacheCamel" is-gateway="true"> <property name="gatewayClass" value="org.jboss.soa.esb.listeners.gateway.camel.ApacheCamelListener"></property> <property name="protocol-uri" value="irc:breakingwoods@irc.freenode.net/#esbtest"></property> <property name="destination-category" value="sample-apachecamelESBService"></property> <property name="destination-name" value="sample-apachecamelESBServiceListener"></property> </listener> </listeners> <actions mep="OneWay"> <action name="dump" class="org.jboss.soa.esb.actions.SystemPrintln">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<property name="printfull" value="false"></property>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</action> </actions> </service>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<service category="sample-apachecamelESBService" name="sample-apachecamelESBServiceListener" description="Service responsible for interact with Actions based in Project sample-apachecamel">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<listeners>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<jms-listener name="JMS-Gateway" busidref="sample-apachecamelGwChannel" maxThreads="1" is-gateway="true"></jms-listener>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<jms-listener name="JMS-ESBListener" busidref="sample-apachecamelEsbChannel" maxThreads="1"></jms-listener>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</listeners>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<actions mep="OneWay">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<action name="dump" class="org.jboss.soa.esb.actions.SystemPrintln">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<property name="printfull" value="true"></property>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</action>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</actions>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</service>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</services>
Based on your tips, I will improve this gateway source at breakingwoods SVN now
Thanks
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/530204#530204
16 years, 1 month
[JBoss Microcontainer Development] New message: "Circular Dependencies and Semi-Resolve"
by Adrian Brock
JBoss development,
A new message was posted in the thread "Circular Dependencies and Semi-Resolve":
http://community.jboss.org/message/530202#530202
Author : Adrian Brock
Profile : http://community.jboss.org/people/adrian@jboss.org
Message:
--------------------------------------------------------------
https://jira.jboss.org/jira/browse/JBKERNEL-109
I've committed a prototype for circular dependencies.
This involved three main changes:
1) The ability to "semiResolve" a dependency which means that you know what you want to depend on,
but it is not in the correct state yet. However, if the only thing that is stopping it moving to the correct
state is a circular dependency (i.e. other things in the semi-resolved state) then it will upgraded to fully resolved.
2) Change AbstractDependencyItem to use an enum for the three different types of resolved states,
resolved, semi-resolved and unresolved and track the different types in AbstractDependencyInfo for optimized processing of the
different types.
3) A change in AbstractController to introduce an "uninstalling" set like the "installing" set, to avoid recursive
when uninstalling contexts that have circular dependencies.
Caveats:
* I haven't looked at adding ON_DEMAND processing, although it should be simple to add?
* The semi-resolved handling only looks at contexts in the previous state to what you require.
If they are in any earlier state then they are unresovled until they progress to the previous state.
This avoids having to do a complicated determination on whether there is a path to break the circular dependency,
rather than just advancing all the related semi-resolved contexts to the next state.
Its usage should be trivial:
public MyDependencyItem extends AbstractDependencyItem
{
public boolean resolve(Controller)
{
// Determine the context we want to be semi-resolved on
ControllerContext ctx = ...;
if (ctx == null)
return false;
// Pass the handling to AbstractDependencyItem
return semiResolve(ctx);
}
}
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/530202#530202
16 years, 1 month