- Symfony 教程
- Symfony - 主页
- Symfony - 简介
- Symfony - 安装
- Symfony - 架构
- Symfony - 组件
- Symfony - 服务容器
- Symfony - 事件和事件监听器
- Symfony - 表达
- Symfony - 捆绑包
- 创建一个简单的 Web 应用程序
- Symfony - 控制器
- Symfony - 路由
- Symfony - 视图引擎
- Symfony - Doctrine ORM
- Symfony - 表单
- Symfony - 验证
- Symfony - 文件上传
- Symfony - Ajax 控制
- Cookie 和会话管理
- Symfony - 国际化
- Symfony - 日志记录
- Symfony - 电子邮件管理
- Symfony - 单元测试
- Symfony - 高级概念
- Symfony - REST 版
- Symfony - CMF 版
- 完整的工作示例
- Symfony 有用资源
- Symfony - 快速指南
- Symfony - 有用的资源
- Symfony - 讨论
Symfony - 捆绑包
Symfony 包是按特定结构组织的文件和文件夹的集合。捆绑包的建模方式使其可以在多个应用程序中重用。主应用程序本身被打包为一个包,通常称为AppBundle。
捆绑包可以特定于应用程序打包,例如 AdminBundle(管理部分)、BlogBundle(站点的博客)等。此类捆绑包不能在应用程序之间共享。相反,我们可以将应用程序的某一部分(例如博客)建模为通用捆绑包,以便我们可以简单地将捆绑包从一个应用程序复制到另一个应用程序以重用博客功能。
捆绑包的结构
捆绑包的基本结构如下。
控制器- 所有控制器都需要放置在这里。
DependencyInjection - 所有依赖注入相关的代码和配置都需要放置在这里。
Resources/config - 与捆绑包相关的配置放置在此处。
资源/视图- 与捆绑包相关的视图模板放置在此处。
Resources/public - 捆绑相关的样式表、JavaScript、图像等放置在这里。
测试- 捆绑相关的单元测试文件放置在此处。
创建捆绑包
让我们在HelloWorld应用程序中创建一个简单的包,TutorialspointDemoBundle。
步骤 1 - 选择一个命名空间。捆绑包的命名空间应包括供应商名称和捆绑包名称。在我们的例子中,它是Tutorialspoint\DemoBundle。
步骤2 -通过扩展Bundle类创建一个空类TutorialspointDemoBundle并将其放置在src/Tutorialspoint/DemoBundle下。
namespace Tutorialspoint\DemoBundle; use Symfony\Component\HttpKernel\Bundle\Bundle; class TutorialspointDemoBundle extends Bundle { }
步骤 3 - 在AppKernel类中应用程序支持的包列表中注册该类。
public function registerBundles() { $bundles = array( // ... // register your bundle new Tutorialspoint\DemoBundle\TutorialspointDemoBundle(), ); return $bundles; }
这是创建空包所需的全部内容,所有其他概念与应用程序的概念相同。Symfony还提供了一个控制台命令generate:bundle来简化创建新bundle的过程,如下所示。
php bin/console generate:bundle --namespace = Tutorialspoint/DemoBundle
结果
Welcome to the Symfony bundle generator! Are you planning on sharing this bundle across multiple applications? [no]: no Your application code must be written in bundles. This command helps you generate them easily. Give your bundle a descriptive name, like BlogBundle. Bundle name [Tutorialspoint/DemoBundle]: In your code, a bundle is often referenced by its name. It can be the concatenation of all namespace parts but it's really up to you to come up with a unique name (a good practice is to start with the vendor name). Based on the namespace, we suggest TutorialspointDemoBundle. Bundle name [TutorialspointDemoBundle]: Bundles are usually generated into the src/ directory. Unless you're doing something custom, hit enter to keep this default! Target Directory [src/]: What format do you want to use for your generated configuration? Configuration format (annotation, yml, xml, php) [annotation]: Bundle generation > Generating a sample bundle skeleton into app/../src/Tutorialspoint/DemoBundle created ./app/../src/Tutorialspoint/DemoBundle/ created ./app/../src/Tutorialspoint/DemoBundle/TutorialspointDemoBundle.php created ./app/../src/Tutorialspoint/DemoBundle/Controller/ created ./app/../src/Tutorialspoint/DemoBundle/Controller/DefaultController.php created ./app/../tests/TutorialspointDemoBundle/Controller/ created ./app/../tests/TutorialspointDemoBundle/Controller/DefaultControllerTest.php created ./app/../src/Tutorialspoint/DemoBundle/Resources/views/Default/ created ./app/../src/Tutorialspoint/DemoBundle/Resources/views/Default/index.html.twig created ./app/../src/Tutorialspoint/DemoBundle/Resources/config/ created ./app/../src/Tutorialspoint/DemoBundle/Resources/config/services.yml > Checking that the bundle is autoloaded > Enabling the bundle inside app/AppKernel.php updated ./app/AppKernel.php > Importing the bundle's routes from the app/config/routing.yml file updated ./app/config/routing.yml > Importing the bundle's services.yml from the app/config/config.yml file updated ./app/config/config.yml Everything is OK! Now get to work :).