How to resolve resources from modules dependecies?
by Magesh Kumar Bojan
Hi,
I am integrating Apache Camel for SwitchYard in AS7. We have defined a new Camel component in Switchyard and, per their requirement, the component class name is embedded inside a file in a dependent Switchyard module jar:
META-INF/services/org/apache/camel/component/switchyard
This at runtime is read via TCCL.getResourceAsStream by Camel. Now tracing through the Module implementation, I noticed that from a given dependent module only the META-INF, META-INF/services are added in the paths list. However, the path META-INF/services/org/apache/camel/component is not found. I tried adding export="true" with export for that path "META-INF/services/org/apache/camel/component" in that dependency but in vain. How to ensure any or all resource paths included in a dependent module is added to a given module's path list?
cheers,
Magesh
15 years
Fwd: web subsystem management use cases
by Heiko Braun
Begin forwarded message:
> From: Remy Maucherat <rmaucher(a)redhat.com>
> Date: May 11, 2011 1:06:35 PM GMT+02:00
> To: Heiko Braun <hbraun(a)redhat.com>
> Subject: Re: [jboss-as7-dev] web subsystem management use cases
>
> On Wed, 2011-05-11 at 12:52 +0200, Heiko Braun wrote:
>> On May 11, 2011, at 12:47 PM, Remy Maucherat wrote:
>>
>>> Ok, so that's the JSP configuration.
>>
>>
>> yes, in additionI would suggest these management categories:
>
> You can do JSP if you like, but I don't think it's a big priority
> compared to what you list below ;) The JSP defaults should be very good
> for production (so typical console consumers should not need any
> change).
>
>> - connectors
>
> Of course :) SSL is less a priority probably, it would require lots of
> setup.
>
>> - virtual hosts
>
> I think add/remove vhosts is the top priority.
>
>> - rewrite rules
>
> Ok, that's handy.
>
> And:
> - access log
>
>> I'll send out some UI mockups today, so you get an idea.
>
> --
> Remy Maucherat <rmaucher(a)redhat.com>
> Red Hat Inc
>
15 years
Re: [jboss-as7-dev] web subsystem management use cases
by Heiko Braun
Ok, let focus on the actual configuration, the connector and virtual-host element seem to be r/o anyway.
They will remain r/o within the console for now.
I did take quick glance, and would suggest we expose the ability to modify these attributes to begin with:
"configuration" => {
"type" => OBJECT,
"description" => "The common web container configuration.",
"required" => false,
"attributes" => {
"static-resources" => {
"type" => OBJECT,
"description" => "JSP container configuration.",
"required" => false,
"attributes" => {
"disabled" => {
"type" => STRING,
"description" => "Enable the JSP container. The default value is \"true\".",
"required" => false
},
"development" => {
"type" => STRING,
"description" => "Enable the development mode, which gives more information when an error occurs. The default value is \"false\".",
"required" => false
},
"keep-generated" => {
"type" => STRING,
"description" => "Keep the generated Servlets. The default value is \"true\".",
"required" => false
},
"check-interval" => {
"type" => STRING,
"description" => "Check interval for JSP updates using a background thread. The default value is \"0\" (disabled).",
"required" => false
},
"recompile-on-fail" => {
"type" => STRING,
"description" => "Retry failed JSP compilations on each request. The default value is \"false\".",
"required" => false
},
"scratch-dir" => {
"type" => STRING,
"description" => "Specify a different work directory.",
"required" => false
},
"x-powered-by" => {
"type" => STRING,
"description" => "Enable advertising the JSP engine in x-powered-by. The default value is \"true\".",
"required" => false
},
"display-source-fragment" => {
"type" => STRING,
"description" => "When a runtime error occurs, attempts to display corresponding JSP source fragment. The default value is \"true\".",
"required" => false
}
}
Does that sounds reasonable?
Any other development or performance relevant attribute people might miss in the console?
Ike
On May 11, 2011, at 11:22 AM, Remy Maucherat wrote:
> On Wed, 2011-05-11 at 11:05 +0200, Heiko Braun wrote:
>> What I mean is, that I don't recognize which parts are actually going to be modified,
>> i.e. what the use cases exist.
>>
>> - "configuration" : what's that?
>> - "connector": can there be others? which one? any examples?
>> - "connector/virtual-server": what does it mean? can it be changed?
>> - "connector/ssl": same story: can it be changed?
>> - "virtual-server": can there be others?
>
> I did put some descriptions for the subsystem (in the
> LocalDescriptions.properties), let me know if they should be improved.
>
> However, I don't see the tool displaying all them, so where are they
> actually used ?
>
> --
> Remy Maucherat <rmaucher(a)redhat.com>
> Red Hat Inc
>
15 years
Subsystem management status
by Heiko Braun
In addition to the mails I send out yesterday, each subsystem owner may want to comment on this page:
http://community.jboss.org/wiki/SubsystemManagementOperations
It reflects the current implementation status and availability of management operations within the console.
If you happen to fall into the blue category ("Subsystem Management API incomplete/missing") please take a minute
to let me know what if there are any management op's on the roadmap and when they will be provided upstream
Ike
15 years
Re: [jboss-as7-dev] web subsystem management use cases
by Heiko Braun
>
>
>> [domain@localhost:9999 /] /profile=default/subsystem=web:read-resource(recursive=true)
>> {
>> "outcome" => "success",
>> "result" => {
>> "configuration" => undefined,
>> "connector" => {"http" => {
>> "protocol" => "HTTP/1.1",
>> "socket-binding" => "http",
>> "scheme" => "http",
>> "virtual-server" => undefined,
>> "ssl" => undefined
>> }},
>> "virtual-server" => {"localhost" => {
>> "alias" => ["example.com"],
>> "access-log" => undefined,
>> "rewrite" => undefined
>> }}
>> },
>> "compensating-operation" => undefined
>> }
What I mean is, that I don't recognize which parts are actually going to be modified,
i.e. what the use cases exist.
- "configuration" : what's that?
- "connector": can there be others? which one? any examples?
- "connector/virtual-server": what does it mean? can it be changed?
- "connector/ssl": same story: can it be changed?
- "virtual-server": can there be others?
Ike
15 years
Re: [jboss-as7-dev] ejb3 and ee subsystems
by Jaikiran Pai
I ended up replying only to Ike instead of sending it to the list. So
forwarding this again.
-Jaikiran
-------- Original Message --------
Subject: Re: [jboss-as7-dev] ejb3 and ee subsystems
Date: Tue, 10 May 2011 20:36:31 +0530
From: Jaikiran Pai <jpai(a)redhat.com>
Reply-To: jpai(a)redhat.com
Organization: Red Hat
To: Heiko Braun <hbraun(a)redhat.com>
Currently EE (and EJB3) is undergoing a major refactoring in a separate
branch. Once we have that ready, we should be able to start looking at
the management part.
-Jaikiran
On Tuesday 10 May 2011 08:33 PM, Heiko Braun wrote:
> there is no reasonable functionality, I tend to exclude these two for 7.0.Final:
>
> [domain@localhost:9999 /] /profile=default/subsystem=ee:read-resource(recursive=true)
> {
> "outcome" => "success",
> "result" => {},
> "compensating-operation" => undefined
> }
> [domain@localhost:9999 /] /profile=default/subsystem=ejb3:read-resource(recursive=true)
> {
> "outcome" => "success",
> "result" => {},
> "compensating-operation" => undefined
> }
>
>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
15 years
webservice subsystem: metrics
by Heiko Braun
how can I get hold of the invocation metrics?
I can only see a "list-endpoints" operation, but nothing that relates to ${subject}
Ike
15 years
arquillian subsystem: management use cases
by Heiko Braun
Any notable management op's planned for arquillian in the near future?
I tend to exclude it from the 7.0.Final console as well.
[domain@localhost:9999 /] /profile=default/subsystem=arquillian:read-resource(recursive=true)
{
"outcome" => "success",
"result" => {},
"compensating-operation" => undefined
}
Ike
15 years
Naming management use cases
by Heiko Braun
If there is no reasonable functionality, I tend to exclude this one for 7.0.Final:
[domain@localhost:9999 /] /profile=default/subsystem=naming:read-resource(recursive=true)
{
"outcome" => "success",
"result" => {},
"compensating-operation" => undefined
}
Ike
15 years
