git usage
by Boleslaw Dawidowicz
Hi
We were recently brainstorming a bit with Julien around Git usage for GateIn and here is a draft of the doc:
https://docs.google.com/document/pub?id=1dp3QODiZDG3KbolnBsCkjZWwYtIvCaQv...
I would like all of you to read it and comment.
The main concern is around having two spaces in github. Let me clarify reasoning about this part a bit. If you look at how Infinispan uses git:
https://docs.jboss.org/author/display/ISPN/Contributing+to+Infinispan#Con...
you will notice that in the end there are few people acting as "Project Admin" and everything goes via them as a pull request. This means that all development is being performed in private clones and forks and only code in clean state hits the repo. It also means that few people have a lot on their shoulders to handle pull requests.
Julien proposed to have common more open space at "https://github.com/gatein". We would be able to collaborate more on common branches. It would be also more easy to track all development work that is going on in the project in one place. We would be able to also give push/pull access to guys from QA and Support.
Separately we would have something aka "blessed" repo (https://github.com/gateinportal). Only few people have access there, and everytime we tag, release we push clean code with clean history there. Community doesn't really need to be aware of it and we don't need to advertise it too much. It is more also for safety reasons as git allows destructive operations so when more people can push things into "gatein" space we can end up with losing some important history there.
Personally I still have a bit mixed feelings around this two places idea and thats partly why I'm asking for feedback. I assume that we would like to commit directly into "gatein" space repos for feature requests, bugs and etc. We would still use private forks for prototyping, experimenting or dirty commits but it would be advised to push things to gatein space on regular bases for other work.
The goal is to prepare some kind of public doc like infinispan wiki.
Bolek
14 years, 11 months
Access to the service stack from the API
by Christophe Laprun
Folks,
Ideally, we would support calling to the API from extensions. However, this is currently a tricky proposition due to weak service ordering and dependency management of the kernel. Calling to the API from portlets is a non-issue because all the services are made available by the portal context by the time portlets are ready to execute code.
While we might decide to eschew support of calling to the API from extensions, we need to address the REST use case and solve the issue of making sure that all the proper services are started and available when the REST component of the API is made available to users (which will probably not call to the API from a portal context). We therefore need to come up with a solution to this issue.
Ideas? :)
Cordialement / Best,
Chris
==
Principal Software Engineer / JBoss Enterprise Middleware Red Hat, Inc.
Follow GateIn: http://blog.gatein.org / http://twitter.com/gatein
Follow me: http://metacosm.info/metacosm / http://twitter.com/metacosm
14 years, 12 months
GateIn Api Discussion
by Matt Wringe
There have been some discussion on creating an api package to create a
simple way for people to interact and manipulate a gatein portal.
Example situations would be things like creating a gadget, adding an
application to a category, creating a page and adding it to a node,
adding applications to a page, managing users, etc...
Two different solutions have been created, both are a bit different in
approach. These are preliminary and are not meant to be complete, it is
more meant to start of a discussion:
https://github.com/metacosm/gatein-api
https://github.com/mwringe/gatein-api
Lets start a discussion on the above apis and what you would expect to
come from an api like this.
15 years
PC component StAX parsing
by Marko Strukelj
Julien, I found a little issue with CDATA and new StAX parsing. Values
wrapped with CDATA are all null.
The fix is to turn on coalesce mode on XMLInputFactory:
Index:
portlet/src/main/java/org/gatein/pc/portlet/impl/deployment/staxnav/PortletApplicationMetaDataBuilder.java
===================================================================
---
portlet/src/main/java/org/gatein/pc/portlet/impl/deployment/staxnav/PortletApplicationMetaDataBuilder.java
(revision 6769)
+++
portlet/src/main/java/org/gatein/pc/portlet/impl/deployment/staxnav/PortletApplicationMetaDataBuilder.java
(working copy)
@@ -187,6 +187,7 @@
PortletApplication20MetaData md = new PortletApplication20MetaData();
XMLInputFactory factory = XMLInputFactory.newInstance();
+ factory.setProperty("javax.xml.stream.isCoalescing", true);
XMLStreamReader stream = factory.createXMLStreamReader(is);
StaxNavigator<Element> nav = new StaxNavigatorImpl<Element>(new
Naming.Enumerated.Simple<Element>(Element.class, null), stream);
- marko
15 years
