Fabric3

Webapp runtime requires a web component

Details

  • Type: Improvement Improvement
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Won't Fix
  • Affects Version/s: 0.4
  • Fix Version/s: 1.6
  • Component/s: WebApp Runtime
  • Labels:
    None
  • Number of attachments :
    0

Description

The webapp runtime requires that a web component is defined. The user can specify the name of this component as a context parameter but if they don't it is defaulted to "webapp." If there is no component with that name then a fatal error is raised.

This makes life easy for UI applications consuming local services, but requires that an empty "web" component is configured for applications that may never use it (for example, ones that just expose web services). It should be possible to have a default configuration that does not require a web component.

Activity

Hide
Jeremy Boynes added a comment -

One option would be to remove the requirement for a named component.

The runtime would examine the webapp composite and locate the single web component it contained. If found, that would become the bound web component. If the user had specified a name, then it would be an error if it was not the name of the bound component.

Show
Jeremy Boynes added a comment - One option would be to remove the requirement for a named component. The runtime would examine the webapp composite and locate the single web component it contained. If found, that would become the bound web component. If the user had specified a name, then it would be an error if it was not the name of the bound component.
Hide
Jim Marino added a comment -

The webapp runtime will be retired in an upcoming release.

Show
Jim Marino added a comment - The webapp runtime will be retired in an upcoming release.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: