1460777829-18e8f3fe-d7b6-4c69-a080-8615ad75e42b

1. A heating unit, comprising:
a heat conductor internally provided with at least one duct for accommodating a PTC heating element, at least one first liquid passage channel, and at least one second liquid passage channel;
a first end cover fixedly coupled to one end of the heat conductor, the first end cover being internally provided with a first compartment, a second compartment, an end cover water inlet, and an end cover water outlet, the end cover water inlet being in fluid communication with the first compartment and the first liquid passage channel, and the end cover water outlet being in fluid communication with the second compartment and the second liquid passage channel;
a second end cover fixedly coupled to an opposite end of the heat conductor, the first liquid passage channel and the second liquid passage channel being in fluid communication with each other via an internal space within the second end cover so as to form a closed liquid circulation channel; and
at least one PTC heating element positioned within the duct of the heat conductor, the PTC heating element having a length longer than that of said heat conductor and having at least one end extending out of an end of the duct.
2. The heating unit of claim 1, wherein:
the first end cover includes at least one groove capable of accommodating the portion of the PTC heating element extending out of the, the groove extending through an interior of the first end cover and being in communication with an external space; andor
the second end cover is also provided with at least one opening capable of accommodating the end of the PTC heating element extending out of the duct.
3. The heating unit of claim 2, wherein:
a first sealing gasket is provided between an end face of the first end cover and an end face of the heat conductor, the first sealing gasket surrounding a mouth of the first liquid passage channel and of the second liquid passage channel; andor
a second sealing gasket is disposed between an end face of the second end cover and an end face of the heat conductor, the second sealing gasket surrounding a mouth formed at an end of the first liquid passage channel and the second liquid passage channel.
4. The heating unit of claim 3, wherein the portion of the PTC heating element that extends out of the duct is wrapped with an insulating and sealing layer.
5. The heating unit of claim 4, wherein the insulating and sealing layer comprises one of an epoxy filler, a rubber sheath, or a rubber sealing plug.
6. A heating unit, comprising:
a heat conductor, internally provided with at least one duct for accommodating a PTC heating element, and at least one liquid passage channel;
a first end cover fixedly coupled to one end of the heat conductor, the first end cover being provided with an end cover water inlet in fluid communication with one end of the liquid passage channel;
a second end cover fixedly coupled to the other end of the heat conductor, the second end cover being provided with an end cover water outlet in communication with the other end of the liquid passage channel; and
at least one PTC heating element provided in the duct of the heat conductor, the PTC heating element having a length longer than that of the heat conductor and having at least one end extending out of the duct.
7. The heating unit of claim 6, wherein:
the first end cover is provided with at least one first groove capable of accommodating the portion of the PTC heating element extending out of the duct, the first groove being in communication with an external space; andor
the second end cover comprises at least one second groove capable of accommodating the portion of the PTC heating element extending out of the duct, the second groove being also in communication with the external space.
8. The heating unit of claim 7, wherein:
a first sealing gasket is provided between an end face of the first end cover and an end face of the heat conductor, the first sealing gasket surrounding a mouth of the liquid passage channel; andor
a second sealing gasket is also provided between an end face of the second end cover and an end face of the heat conductor, the second sealing gasket surrounding a mouth of the liquid passage channel.
9. The heating unit of claim 8, wherein the portion of the PTC heating element that extends out of the duct is wrapped with an insulating and sealing layer.
10. The heating unit of claim 9, wherein the insulating and sealing layer comprises one of an epoxy filler, a rubber sheath, or a rubber plug.

The claims below are in addition to those above.
All refrences to claim(s) which appear below refer to the numbering after this setence.

1. A business mashup method, comprising:
generating business application logic syntax corresponding to a business according to requirements of the business, where the business application logic syntax comprises both of a description of Web services and a description of Widgets;
mashing up the Widgets described in the business application logic syntax to create a Widget mashup application;
establishing an adaptation relationship between the Web services and the Widgets in the Widget mashup application;
generating an executable business process for the business based on the business application logic syntax and the adaptation relationship; and
generating an executable mashup Widget application based on the Widget mashup application and the adaptation relationship.
2. The method of claim 1, where generating the business application logic syntax corresponding to the business according to the requirements of the business comprises:
acquiring Web service metadata and Widget metadata related to the business; and
composing the business application logic syntax using the acquired Web service metadata and the Widget metadata, where the Web service metadata forms the description of the Web services in the business application logic syntax and the Widget metadata forms the description of the Widgets in the business application logic syntax.
3. The method of claim 2, where acquiring the Web service metadata and the Widget metadata related to the business comprises:
populating the Web service metadata related to the business from a service metadata registry that stores the Web service metadata;
assembling the Web service metadata; and
populating the Widget metadata from a Widget registry that stores the Widgets.
4. The method of claim 1, where mashing up the Widgets described in the business application logic syntax to create the Widget mashup application comprises:
discovering the Widgets using the description of the Widgets in the business application logic syntax; and
assembling the Widgets based on events to generate the Widget mashup application, where the events comprise a published event and a handled event.
5. The method of claim 1, where establishing the adaptation relationship between the Web services and the Widgets in the Widget mashup application comprises:
establishing a transformation relationship on information format between the Web services and the Widgets; and
establishing a transformation relationship on transport protocol between the Web services and the Widgets.
6. The method of claim 1, where generating the executable business process for the business based on the business application logic syntax and the adaptation relationship comprises:
composing a Business Process Execution Language (BPEL) based application with the Web services based on the business application logic syntax and the adaptation relationship; and
transforming the BPEL based application into the executable business process according to a runtime environment.
7. The method of claim 1, further comprising:
deploying runtime environments comprising a business process runtime environment and a Widget runtime environment;
publishing the executable business process into the business process runtime environment;
publishing the executable mashup Widget application into the Widget runtime environment;
executing the executable business process in the business process runtime environment; and
executing the executable mashup Widget application in the Widget runtime environment;
where the executable business process and the executable mashup Widget application exchange information with each other based on the adaptation relationship during runtime.
8. A business mashup system, comprising:
a memory; and
at least one processor programmed to:
generate business application logic syntax corresponding to a business according to requirements of the business, where the business application logic syntax comprises both of a description of Web services and a description of Widgets;
mash up the Widgets described in the business application logic syntax to create a Widget mashup application;
establish an adaptation relationship between the Web services and the Widgets in the Widget mashup application;
generate an executable business process for the business based on the business application logic syntax and the adaptation relationship; and
generate an executable mashup Widget application based on the Widget mashup application and the adaptation relationship.
9. The system of claim 8, where, in being programmed to generate the business application logic syntax corresponding to the business according to the requirements of the business, the at least one processor is programmed to:
acquire Web service metadata and Widget metadata related to the business; and
compose the business application logic syntax using the acquired Web service metadata and the Widget metadata, where the Web service metadata forms the description of the Web services in the business application logic syntax and the Widget metadata forms the description of the Widgets in the business application logic syntax.
10. The system of claim 9, where, in being programmed to acquire the Web service metadata and the Widget metadata related to the business, the at least one processor is programmed to:
populate the Web service metadata related to the business from a service metadata registry that stores the Web service metadata;
assemble the Web service metadata; and
populate the Widget metadata from a Widget registry that stores the Widgets.
11. The system of claim 8, where, in being programmed to mash up the Widgets described in the business application logic syntax to create the Widget mashup application, the at least one processor is programmed to:
discover the Widgets using the description of the Widgets in the business application logic syntax; and
assemble the Widgets based on events to generate the Widget mashup application, where the events comprise a published event and a handled event.
12. The system of claim 8, where, in being programmed to establish the adaptation relationship between the Web services and the Widgets in the Widget mashup application, the at least one processor is programmed to:
establish a transformation relationship on information format between the Web services and the Widgets; and
establish a transformation relationship on transport protocol between the Web services and the Widgets.
13. The system of claim 8, where, in being programmed to generate the executable business process for the business based on the business application logic syntax and the adaptation relationship, the at least one processor is programmed to:
compose a Business Process Execution Language (BPEL) based application with the Web services based on the business application logic syntax and the adaptation relationship; and
transform the BPEL based application into the executable business process according to a runtime environment.
14. The system of claim 8, where the at least one processor is further programmed to:
deploy runtime environments comprising a business process runtime environment and a Widget runtime environment;
publish the executable business process into the business process runtime environment; and
publish the executable mashup Widget application into the Widget runtime environment;
execute the executable business process in the business process runtime environment; and
execute the executable mashup Widget application in the Widget runtime environment;
where the executable business process and the executable mashup Widget application exchange information with each other through the adaptation relationship during runtime.
15. A computer program product comprising a non-transitory computer readable storage medium including computer readable program code, where the computer readable program code when executed on a computer causes the computer to:
generate business application logic syntax corresponding to a business according to requirements of the business, where the business application logic syntax comprises both of a description of Web services and a description of Widgets;
mash up the Widgets described in the business application logic syntax to create a Widget mashup application;
establish an adaptation relationship between the Web services and the Widgets in the Widget mashup application;
generate an executable business process for the business based on the business application logic syntax and the adaptation relationship; and
generate an executable mashup Widget application based on the Widget mashup application and the adaptation relationship.
16. The computer program product of claim 15, where in causing the computer to generate the business application logic syntax corresponding to the business according to the requirements of the business, the computer readable program code when executed on the computer causes the computer to:
acquire Web service metadata and Widget metadata related to the business; and
compose the business application logic syntax using the acquired Web service metadata and the Widget metadata, where the Web service metadata forms the description of the Web services in the business application logic syntax and the Widget metadata forms the description of the Widgets in the business application logic syntax.
17. The computer program product of claim 16, where in causing the computer to acquire the Web service metadata and the Widget metadata related to the business, the computer readable program code when executed on the computer causes the computer to:
populate the Web service metadata related to the business from a service metadata registry that stores the Web service metadata;
assemble the Web service metadata; and
populate the Widget metadata from a Widget registry that stores the Widgets.
18. The computer program product of claim 15, where in causing the computer to mash up the Widgets described in the business application logic syntax to create the Widget mashup application, the computer readable program code when executed on the computer causes the computer to:
discover the Widgets using the description of the Widgets in the business application logic syntax; and
assemble the Widgets based on events to generate the Widget mashup application, where the events comprise a published event and a handled event.
19. The computer program product of claim 15, where in causing the computer to establish the adaptation relationship between the Web services and the Widgets in the Widget mashup application, the computer readable program code when executed on the computer causes the computer to:
establish a transformation relationship on information format between the Web services and the Widgets; and
establish a transformation relationship on transport protocol between the Web services and the Widgets.
20. The computer program product of claim 15, where in causing the computer to generate the executable business process for the business based on the business application logic syntax and the adaptation relationship, the computer readable program code when executed on the computer causes the computer to:
compose a Business Process Execution Language (BPEL) based application with the Web services based on the business application logic syntax and the adaptation relationship; and
transform the BPEL based application into the executable business process according to a runtime environment.
21. The computer program product of claim 15, where the computer readable program code when executed on the computer further causes the computer to:
deploy runtime environments comprising a business process runtime environment and a Widget runtime environment;
publish the executable business process into the business process runtime environment;
publish the executable mashup Widget application into the Widget runtime environment;
execute the executable business process in the business process runtime environment; and
execute the executable mashup Widget application in the Widget runtime environment;
where the executable business process and the executable mashup Widget application exchange information with each other based on the adaptation relationship during runtime.